Date: Mon, 6 Sep 2010 05:12:53 +1000 From: Peter Jeremy <peterjeremy@acm.org> To: jhell <jhell@DataIX.net> Cc: bf1783@gmail.com, "b. f." <bf1783@googlemail.com>, FreeBSD Ports <freebsd-ports@freebsd.org> Subject: Re: math/blas linking to gfortran with LDADD?= -lgfortran Message-ID: <20100905191253.GA91710@server.vk2pj.dyndns.org> In-Reply-To: <4C7D70CA.2070104@DataIX.net> References: <AANLkTinhAPY-PEH_TegMAEx1ejHf_WoEL8KZU%2BoXGhFD@mail.gmail.com> <4C7D70CA.2070104@DataIX.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--PEIAKu/WMn1b1Hv9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2010-Aug-31 17:14:50 -0400, jhell <jhell@DataIX.net> wrote: >On 08/31/2010 15:06, b. f. wrote: >> Would you elaborate, please? Where is a transcript showing the linking = failure? >> Would you mail it to me off-list? > >Simply -lgfortran by it self should not work. Since lib directories Actually, IMO, since libgfortran.so is a support library for gfortran (much like libgcc_s.so is), it is reasonable for a user to expect that '-lgfortran' _is_ sufficient and the current behaviour is a bug. ports/129518 says I'm not the only person who think that. >-L/usr/local/lib/gcc44 would have to be passed to LDFLAGS in order for >it to be found. And '-R/usr/local/lib/gcc44' as well. Note that a work-around has been added to bsd.gcc.mk so that ports with USE_GCC shouldbehave correctly and the problem is limited to using a non-base gcc outside the ports system. --=20 Peter Jeremy --PEIAKu/WMn1b1Hv9 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (FreeBSD) iEYEARECAAYFAkyD67UACgkQ/opHv/APuIeOEwCdH8iRUZ1CHFeojhuIj64+peaq vP4An1JWBpWS/Fg2i7Dhojs+2ycNS0i5 =U9oK -----END PGP SIGNATURE----- --PEIAKu/WMn1b1Hv9--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100905191253.GA91710>