Re: [Gcl-devel] cvs build on linux aborts

[robert read]

* Camm Maguire (address@hidden) [011230 08:09]:
> Greetings!  OK we certainly need to track this one down.  In sum, the
> issue seems to be:
> 
>       When compiled on libc2.2.4 Linux system, gcl will not run on
>       any Linux system.
>       When compiled on <= libc2.1.x Linux system, gcl will run on
>       *any* Linux system.
> 
> Please correct the above if it is in error, or confirm that this is
> the case if you haven't yet.

I also have an older Suse system with glibc 2.2. I'm building now.

> 
> 1) Robert -- do you have ssh access to this box?

I'll see what I can do, but that should possible.

> 2) Both -- can you please compile with -g only (alter 386-linux.defs
>    as necessary), run under the debugger, find out if this is a
>    segfault, and if so where?

Will do.

> 3) Vadim -- if memory serves, you tried to link statically, and this
>    did not work.  Correct?

I can try this, too.  I suppose I can do that by adding -static to CC in
386-linux.defs?

> 
> I do know of one explicit glibc issue that Dr. Schelter resolved for me
> back in 5/2000.  He documented this in the changelog, and it enabled
> dynamic linking against libc.  It was a change to rsym_elf to strip
> the @GLIB off of symbols so that linking happened correctly.  I had
> thought that maybe the new libc had a different labelling system, but
> them static linking would work.  Please confirm that it does not work.
> 
> 4) Robert, could you post the build output?

Sure, here is my make.log and also the config.log.  Notice in the
make.log that the same error occurs when raw_gcl starts up, although
it does not abort.

robert

config.log
Description: Text document

make.log
Description: Text document