Date: Fri, 04 Jul 2008 15:36:35 +0300 From: Andriy Gapon <avg@icyb.net.ua> To: Dmitry Marakasov <amdmi3@amdmi3.ru> Cc: FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: gnash-0.8.3: build fails on 6.3 Message-ID: <486E1953.90108@icyb.net.ua> In-Reply-To: <20080703223457.GA41872@hades.panopticon> References: <4860EC81.1010302@icyb.net.ua> <20080624165126.GJ4022@hades.panopticon> <48620622.50808@icyb.net.ua> <20080701193629.GB45179@hades.panopticon> <486D108E.8030100@icyb.net.ua> <486D12D5.1060304@icyb.net.ua> <20080703223457.GA41872@hades.panopticon>
next in thread | previous in thread | raw e-mail | index | archive | help
on 04/07/2008 01:34 Dmitry Marakasov said the following: > * Andriy Gapon (avg@icyb.net.ua) wrote: > >> A s we can see -L/usr/lib comes before gcc-4.2.4 path and thus base >> libstdc+ is picked over the correct one. >> >> Since you can not reproduce this in clean environment I wonder where >> that -L/usr/lib comes from. > Seems like you're right, I don't have -L/usr/lib in gcc args when > building gnash. > > Could you please send me conf* files from the workdir (config.log etc.) > and all Makefile* files (Makefile, Makefile.in from all subdirs). > Dmitry, I decided to do some more local research before sending you that bulk data. Here's what I have so far. 1. There is no -L/usr/lib in the corresponding libtool invocation, so it means that libtool itself adds it. 2. There is the following line in libtool script (in gnash base dir): sys_lib_search_path_spec=" /usr/lib/" 3. In configure script I see that is set based on $CC -print-search-dirs 4. gcc42 -print-search-dirs produces "good" list of directories where its specific directories precede /usr/lib. 5. But gcc -print-search-dirs produces only /usr/lib. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?486E1953.90108>