This is the mail archive of the
mailing list for the libstdc++ project.
Re: What are being done about the dependecy_libs - problem?
On Sat, Jul 06, 2002 at 02:05:55PM +0200, ULRIK MIKAELSSON wrote:
> grep /home/rawler/rpm/ `rpm -ql libstdc++`
> with the result:
> Binary file /usr/lib/libgcc_s.so matches
> Binary file /usr/lib/libgcc_s.so.1 matches
> Binary file /usr/lib/libstdc++.a matches
> Binary file /usr/lib/libstdc++.so matches
> Binary file /usr/lib/libstdc++.so.4 matches
> Binary file /usr/lib/libstdc++.so.4.0.0 matches
> (/usr/lib/libstdc++.la was also listed, of course but I've modified it
> The same thing goes for the libraries in the gcc package, they also
> contain references to my buildpaths.
Well, the build paths will show up for lots of reasons. Debugging info,
for example. But grep doesn't know that, of course, so it can't restrict
its search to only certain parts of the .so.
> What the libraries contain is paths to the headers used in the package
> (in /home/rawler/rpm/BUILD/gcc-3.1), I haven't found any other paths. I
> haven't found any reference to/home/rawler/rpm/buildroot in ANY of the
> files in my gcc rpm's or libstdc++, still this is what the kdelibs build
> complain about.
> The kde build still complains after I've manually fixed libstdc++.la. (Not
> that it contained the path /home/rawler/rpm/buildroot/ anyways.)
Is it libtool complaining, or the actual linker?
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace. We seek
not your counsel, nor your arms. Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen. - Samuel Adams