Julien wrote:
> Here is the full build log:
Hi,
Thank you for trying. You did extract the piece that showed that there
was a problem.
The additional context won't help any. The problem is that the server
shell (/bin/sh)
died unexpectedly while processing the code fragment displayed in your
initial
extraction. The syntax of that fragment is Bourne (and hence POSIX)
compliant.
The question is, ``Why did the shell die?'' If there is a core file
left around, it could
be debugged. Another option is to modify the autogen package so that
in the file autogen*/agen5/opts.def the line:
version = `
is changed to read:
version = ` set -x
if the "set -x" does not fire, then your "dash" thingey has trouble
behaving as
a server shell (stdin/stdout redirected to a pair of pipes to another
process).
If it does fire, you'll see the shell trace in stderr and it should be
obvious
what is going awry. The code in agen5/agShell.c has the code for managing
a server shell. FYI:
$ (export SHELL=$dash top_builddir=.. top_srcdir=.. PATH=`cd
../columns;pwd`:$PATH ; export top_builddir top_srcdir PATH ;
/home/bkorb/ag/ag/agen5/autogen -L../autoopts --definition=./xmlopts.def)
Changing server shell from /home/bkorb/tools/dash/dash-0.5.3/_i/bin/dash
to /bin/sh
$ ls -l /bin/sh
lrwxrwxrwx 1 root bin 45 Jun 17 10:29 /bin/sh ->
/home/bkorb/tools/dash/dash-0.5.3/_i/bin/dash
It is not dash. I have to go now. Thanks for your help. Regards, Bruce
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
