This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: assertion fails in elf/get-dynamic-info.h


* Chris Aoki:

> So please allow me to retry my original questions:
>
> 1.  Do the assertions intentionally defeat the purpose of the
>      -Wl,-rpath and -Wl,—dynamic-linker flags given in the testing
>      instructions?

No.

> 2.  If so, what is the rationale underlying the assertions?

LD_LIBRARY_PATH probably will not work at all if the dynamic linker
has these settings.  )The code is simply not prepared for this.)

> 3.  If not, how should the build be configured to support the
>      documented testing instructions?

You must not specify an rpath when linking the dynamic linker.  If
your toolchain does that unconditionally, this looks like a toolchain
bug (maybe sysroot-related?).  It is certainly possible to build
upstream GCC in such a way that it does not do this (and I think it's
the default).

> 4.  Should the assertion in elf/get-dynamic-info.h be disabled at
>      configuration time if the compiler used to build glibc supplies
>      -Wl,-rpath implicitly?

No, ld.so must not have a DT_RPATH or DT_RUNPATH.

> If not, then perhaps the documented build instructions should be
> modified to comply with the assertion, though I’m not sure how one
> should go about it.   If glibc requires a newer compiler, the complexity
> of the steps required to get the newer compiler installed on the system
> could be considerable.

The compiler does not have to be installed.  See
scripts/build-many-glibcs.py how to do that.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]