Re: [Gcl-devel] gcl build failure

[Vadim V. Zhytnikov]

Thank! Now it's OK.

Camm Maguire wrote:

> Hi Vadim!
>
> OK, the way I was statically linking the libbfd produced the following
> compiler error here too on the nsocket.c test:
>
> intech19:/tmp$ gcc -o foo -g -O2   foo.c  -lm -lreadline -lncurses  
> -Wl,-static -lbfd -liberty
> /usr/bin/ld: /lib/ld-linux.so.2: indirect symbol `__libc_internal_tsd_set' to 
> `__libc_internal_tsd_set@@GLIBC_2.0' is a loop
> /lib/ld-linux.so.2: could not read symbols: Invalid operation
> collect2: ld returned 1 exit status
>
> I've committed what I think is a fix.  Please try it out!
>
> Take care,
>
> "Vadim V. Zhytnikov" <address@hidden> writes:
>
> > This is a multi-part message in MIME format.
> > --------------24E147AC5C43059D907F3ECA
> > Content-Type: text/plain; charset=koi8-r
> > Content-Transfer-Encoding: 7bit
> >
> > The configure logs for unsuccessful gcl build and older logs
> > for gcl cvs dated Feb 16 (builds successfully) are attached.
> > Take a look at nsock configure failure.
> > Maybe problem is related to static bfd and iberty linking?
> > All required packages seems to be present
> >    libbfd
> >   libdfd-devel
> >   libbfd-devel-static
> >   libiberty-devel
> >
> > Best wishes
> >
> > Vadim
> >
> > --
> >
> > [ Vadim V. Zhytnikov  <address@hidden>  <address@hidden> ]
> >
> >
> >

[ Vadim V. Zhytnikov  <address@hidden>  <address@hidden> ]