This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: V8 test-in-container patch
- From: DJ Delorie <dj at redhat dot com>
- To: Szabolcs Nagy <szabolcs dot nagy at arm dot com>
- Cc: carlos at redhat dot com, libc-alpha at sourceware dot org, nd at arm dot com, fweimer at redhat dot com, joseph at codesourcery dot com
- Date: Wed, 10 Oct 2018 15:23:38 -0400
- Subject: Re: V8 test-in-container patch
Szabolcs Nagy <szabolcs.nagy@arm.com> writes:
> is this step really needed? i thought all binaries in
> the testroot are newly built so we should know exactly
> the dependencies (including dlopen ones which are not
> handled by this logic).
The step is needed to handle DSOs that gcc adds dependencies for (like
libgcc_s.so). We install them in the testroot in the same location as
outside the testroot. This may be in /lib, or may be in
/home/me/cross/glibc/arm/lib, etc.
We do this part before the "make install" to ensure if any glibc DSOs
are pulled in from outside the build, they get overwritten by built
DSOs.
Adding flags to find our own DSOs at this step isn't important because
we need to copy them, it's important because we don't want to copy the
wrong ones into a location that might override the newly built ones
(i.e. earlier in ld.so's search path).