You might want to make sure that 'sh' really is 'bash'. The admins on
your host might have linked 'sh' to something else, like 'ksh', which is
'near enough like bash' for most stuff to work. Having said that, I
just ran:

    ksh configure

with no problems, so this might be a complete red herring. Your milage
may vary, content may have settled during transit, etc...

Ralph Mitchell

John Almberg wrote:

> Hey, we are making progress. Running configure with sh worked after I
> explicitly told it the ssl libs were in /usr/local/ssl. Ran it like
> so:
>
>
> $ sh ./configure --prefix=/home/mydir/curl --with-ssl=/usr/local/ssl
>
> And got this:
>
> <OTHER STUFF BEFORE THIS, BUT SEEMS OKAY . . .>
> checking for setvbuf... yes
> checking for sigaction... yes
> checking for signal... yes
> checking for getpass_r... no
> checking for strlcat... no
> checking for getpwuid... yes
> checking for geteuid... yes
> checking for dlopen... yes
> checking for utime... yes
> checking for sigsetjmp... no
> checking for poll... no
> checking for sigsetjmp defined as macro... yes
> checking for perl... /usr/bin/perl
> checking for gnroff... /usr/bin/gnroff
> checking CA cert bundle install path...
> /home/mydir/curl/share/curl/curl-ca-bundle.crt
> checking for bison... bison -y
> checking whether to enable debug options... no
> configure: error: conditional "CONTENT_ENCODING" was never defined.
> Usually this means the macro was only invoked conditionally.
> plum:~/curl$
>
> -- John
>
>
> Daniel Stenberg wrote:
>
>> On Sat, 30 Nov 2002, John Almberg wrote:
>>
>>
>> > There was a core file generated. Ran the following gdb cmd:
>> >
>> > plum:~/curl$ gdb -c core
>> > GDB is free software and you are welcome to distribute copies of it
>> > under certain conditions; type "show copying" to see the
>> > conditions.
>> > There is absolutely no warranty for GDB; type "show warranty" for
>> > details.
>> > GDB 4.16 (i486-slackware-linux), Copyright 1996 Free Software
>> > Foundation, Inc.
>> > Core was generated by `sh ./configure --prefix=/home/mydir/curl
>> > --with-ssl'.
>> > Program terminated with signal 11, Segmentation fault.
>> > #0 0x80705a3 in ?? ()
>> > (gdb)
>> >
>> So this at least proves that bash is the program that cored. I'm not
>> quite
>> sure what we should do about this.
>>
>> Perhaps you can ask your admins to upgrade your bash?
>>
>> You might be able to detect exctly what in the configure script that
>> causes
>> bash to crash by invoking configure like this:
>>
>> $ sh -x ./configure --prefix=/home/mydir/curl --with-ssl
>>
>> ... since -x will give you a "trace" on what the shell is doing,
>> sent to the
>> terminal.
>>
>>

-------------------------------------------------------
This SF.net email is sponsored by: Get the new Palm Tungsten T
handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en
Received on 2002-12-03