binarycloud-dev

[binarycloud-dev] make errors with xml2php

[Alex B. <en...@tu...>]

hi Andris,

I'm getting this:

alex@core htdocs> make
/bin/sh: /home/alex/r2/binarycloud/build/en/htdocs: is a directory
make: *** [xml_page_def] Error 126
alex@core htdocs> 

I had a look at the makefiles, and I can't quite see what's wrong yet.

I've included them here, have a look.

best,

_alex

[binarycloud-dev] make errors with xml2php

[Andris S. <an...@do...>]

> I'm getting this:
> /bin/sh: /home/alex/r2/binarycloud/build/en/htdocs: is a > directory
> make: *** [xml_page_def] Error 126
> alex@core htdocs>

Just checked in all binarycloud tree and tried to document the changes
needed
for xml2php to work.
I got the same error before I remembered I changed /binarycloud/makefile.in
as well...
Part of it looks like this:
    GETPKG=$(TOOLS_DIR)/pk2dir.pl
    INSTALLCODE=$(TOOLS_DIR)/installcode.sh
    PROCESSPREPEND = $(TOOLS_DIR)/processprepend.php
But it should contain one more line which defines the location of xml2php,
so:
    GETPKG=$(TOOLS_DIR)/pk2dir.pl
    INSTALLCODE=$(TOOLS_DIR)/installcode.sh
    PROCESSPREPEND = $(TOOLS_DIR)/processprepend.php
    XML2PHP= $(TOOLS_DIR)/xml2php.php

Also, it might be an good idea to add XMLUtils.php to the list of copied
files at /binarycloud/base/lib/makefile

Let me know if anyone can build the thing now, because I'm not going to
update the CVS with the new version of xml2php & friends & makefiles unless
I hear at
least one success story (:>)

Bellow the history of changes needed with the latest bc version from CVS:
    /binarycloud/makefile - changed the order of the build process
    /binarycloud/makefile.in - added XML2PHP= $(TOOLS_DIR)/xml2php.php
    /binarycloud/base/utils/processprepend.php - added #!c:/php/php.exe -q
at the beginning of the file
    /binarycloud/user/makefile - added xml2php calling functions
    /binarycloud/base/lib/makefile - added XMLUtils.php to the list of files
copied


Andris Spruds

RE: [binarycloud-dev] make errors with xml2php

[Andreas A. <a.a...@th...>]

Hi Andris,

> Let me know if anyone can build the thing now, because I'm not going to
> update the CVS with the new version of xml2php & friends & 
> makefiles unless
> I hear at least one success story (:>)

I applied your zip and the changes in the Makefie.in, but now I get this :(

...
in user/htdocs
Error in argument 1, char 3: option not found
Error in argument 1, char 3: option not found
Usage: php [-q] [-h] [-s] [-v] [-i] [-f <file>] | {<file> [args...]}
<<<the php help screen >>>
Error in argument 1, char 3: option not found
Error in argument 1, char 3: option not found
Usage: php [-q] [-h] [-s] [-v] [-i] [-f <file>] | {<file> [args...]}
<<<the php help screen >>>
make[1]: *** [xml_page_def] Error 1
make: *** [langs] Error 2
[andi@hal r2]$


Andi

[binarycloud-dev] make errors with xml2php

[Andris S. <li...@ap...>]

> I applied your zip and the changes in the Makefie.in, but now I get this
:(
> in user/htdocs
> Error in argument 1, char 3: option not found

At least we have some progress... Another error message (:>)...
Could you please check
1) whether it now gets to the xml2php file (i.e. try to echo something at
the beginning of the file, see if something comes out).
2) whether you have enabled register_argc_argv and register_globals in your
php.ini file.
3) if you're Unix user, there should be #!/usr/local/php4/bin/php -q, but
not #!c:/php/php.exe -q at the beginning of xml2php.php

Andris Spruds

RE: [binarycloud-dev] make errors with xml2php

[Andreas A. <a.a...@th...>]

Hi Andris.

> 2) whether you have enabled register_argc_argv and
> register_globals in your php.ini file.
OK. That was the problem.

Fantastic. It works!!

Some notes:

1) to get arount the register_global/arg stuff you can put this into the
xml2php
ini_set('register_globals', on);
$argv = $HTTP_SERVER_VARS["argv"];


2) The output for datasources is not quite correct. (see. Lang)

global $QueryManager;
$QueryManager->datasources = array(...)

Uuups. I think i have to change init/qm as well to support the same format
as in Lang.

datasources(
	array(data),
	array(data)
);


currently:
datasources(
	'hook' => array(data),
	'hook2' => array(data)
);

3) We should find a way to have a the interpreter line in the php files more
flexible through the different platforms. Perl has a trick to do so
eval 'exec perl -S $0 "$@"'
Maybe we find a way to handle that better.

Andi

Re: [binarycloud-dev] make errors with xml2php

[Alex B. <en...@tu...>]

> Hi Andris.
> 
>> 2) whether you have enabled register_argc_argv and
>> register_globals in your php.ini file.
> OK. That was the problem.
> 
> Fantastic. It works!!
> 

andreas: can you commit it?

or andris?

if it works, I want it :) gimme gimme! heh


> 1) to get arount the register_global/arg stuff you can put this into the
> xml2php
> ini_set('register_globals', on);
> $argv = $HTTP_SERVER_VARS["argv"];

yes, we should set that in all of the command line scripts.
then again, we _could_ integrate that into Init::_ini_set with some sort of
constant flag like

define("HEY_IM_ON_THE_COMMAND_LINE_HERE", true); :)

> 2) The output for datasources is not quite correct. (see. Lang)
> 
> global $QueryManager;
> $QueryManager->datasources = array(...)
> 
> Uuups. I think i have to change init/qm as well to support the same format
> as in Lang.

cool.


> datasources(
> array(data),
> array(data)
> );
> 
> 
> currently:
> datasources(
> 'hook' => array(data),
> 'hook2' => array(data)
> );
> 
> 3) We should find a way to have a the interpreter line in the php files more
> flexible through the different platforms. Perl has a trick to do so
> eval 'exec perl -S $0 "$@"'
> Maybe we find a way to handle that better.

agreed, I was going to suggest a simple ./configure.sh which would do a grep
for a php command line key.

any other ideas?

_a

RE: [binarycloud-dev] make errors with xml2php

[Andreas A. <a.a...@th...>]

Hi Alex,

That's how I would do it:

1:
We use a unix standard location for the shell interpreter
i.e. #!/usr/bin/php (creating a symlink isn't that hard, but only needed for
debugging purposes, see below)

2:
For the make process we introduce an new variable in
Makefile.in that is determined by a configure script i.e:

PHPCMD= "{by configure determined location}"

(after configure e.g. PHPCMD="/usr/local/bin/php -q")

in Makefiles that use command line php we just use
this syntax:

 @$(PHPCMD) $(XML2PHP) ... options etcpp

pros:
- the php command is in a single place
- configure don't has to modify all php shell scripts
- Actually we could leave out the #! line and with some mods
  the scripts could be "incldable" and used through the web
  (maybe we need this later => builing triggerd via an
  admin interface or whatever might be useful in the future).


Andi


>> 3) We should find a way to have a the interpreter
>> line in the php files more flexible through the
>> different platforms. Perl has a trick to do so
>> eval 'exec perl -S $0 "$@"'
>
> agreed, I was going to suggest a simple ./configure.sh which
> would do a grep for a php command line key.
>
> any other ideas?

Re: [binarycloud-dev] make errors with xml2php

[alex b. <en...@tu...>]

actually it's called PHPRC and it's in my ENV. I'll change all the code and
instructions.

good point.

----- Original Message -----
From: "Andreas Aderhold" <a.a...@th...>
To: <bin...@li...>
Sent: Sunday, August 26, 2001 5:09 AM
Subject: RE: [binarycloud-dev] make errors with xml2php


> Hi Alex,
>
> That's how I would do it:
>
> 1:
> We use a unix standard location for the shell interpreter
> i.e. #!/usr/bin/php (creating a symlink isn't that hard, but only needed
for
> debugging purposes, see below)
>
> 2:
> For the make process we introduce an new variable in
> Makefile.in that is determined by a configure script i.e:
>
> PHPCMD= "{by configure determined location}"
>
> (after configure e.g. PHPCMD="/usr/local/bin/php -q")
>
> in Makefiles that use command line php we just use
> this syntax:
>
>  @$(PHPCMD) $(XML2PHP) ... options etcpp
>
> pros:
> - the php command is in a single place
> - configure don't has to modify all php shell scripts
> - Actually we could leave out the #! line and with some mods
>   the scripts could be "incldable" and used through the web
>   (maybe we need this later => builing triggerd via an
>   admin interface or whatever might be useful in the future).
>
>
> Andi
>
>
> >> 3) We should find a way to have a the interpreter
> >> line in the php files more flexible through the
> >> different platforms. Perl has a trick to do so
> >> eval 'exec perl -S $0 "$@"'
> >
> > agreed, I was going to suggest a simple ./configure.sh which
> > would do a grep for a php command line key.
> >
> > any other ideas?
>
>
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> http://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>