Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 26 Sep 2011 13:59:54 -0700
From:      Xin LI <delphij@delphij.net>
To:        Chris Rees <crees@freebsd.org>
Cc:        Rainer Hurling <rhurlin@gwdg.de>, freebsd-ports@freebsd.org, autotools@freebsd.org
Subject:   Re: Shared libs problem with ports under 10-CURRENT
Message-ID:  <4E80E7CA.90902@delphij.net>
In-Reply-To: <CADLo83-BUBWP4qeMqe2dwfJnMsXFBhU3yq_avgKMS30OF3-XgQ@mail.gmail.com>
References:  <4E805A27.90106@gwdg.de> <CADLo83-BUBWP4qeMqe2dwfJnMsXFBhU3yq_avgKMS30OF3-XgQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 09/26/11 11:25, Chris Rees wrote:
> On 26 September 2011 11:55, Rainer Hurling <rhurlin@gwdg.de>
> wrote:
>> This morning I tried to upgrade my ports after installing the new
>> 10-CURRENT (amd64).
>> 
>> Unfortunately now I am not able to build ports using shared
>> libraries like ports/libXext any more. They only build .a and .la
>> files, but not .so ones.
>> 
>> Is it possible that there is something wrong now with libtool-2.4
>> (or the linker /usr/bin/ld)?
>> 
>> #libtool --features host: amd64-portbld-freebsd10.0 disable
>> shared libraries enable static libraries
>> 
>> 
>> Does anyone else observes this behaviour? I would really
>> appreciate some help.
>> 
> 
> Excerpt from libtool configure script:
> 
> dgux*) archive_cmds='$LD -G -h $soname -o $lib $libobjs $deplibs
> $linker_flags' hardcode_libdir_flag_spec='-L$libdir' 
> hardcode_shlibpath_var=no ;;
> 
> freebsd1*) ld_shlibs=no ;;
> 
> # FreeBSD 2.2.[012] allows us to include c++rt0.o to get C++
> constructor # support.  Future versions do this automatically, but
> an explicit c++rt0.o # does not break anything, and helps
> significantly (at the cost of a little # extra space). 
> freebsd2.2*)
> 
> I've mentioned this to an autotools member, who has offered to fix
> it fairly soon :)

I'm thinking this needs a full audit as well.  A lot of ports hardcode
knowledge about freebsd 1.x and mistakenly use 'freebsd1*' to match
them, due to copy of GNU autotools code.

Cheers,
- -- 
Xin LI <delphij@delphij.net>	https://www.delphij.net/
FreeBSD - The Power to Serve!		Live free or die
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.18 (FreeBSD)

iQEcBAEBCAAGBQJOgOfKAAoJEATO+BI/yjfB2+0IALXGpsdosAqZg5qzrFXfyJcx
aOX48azLOZSMcPiDU9jJfHzR2bseB0EWbeclWJ8kcC+A3tIkIwqFLiU5YB81pfi1
cy9f1ow0ZF4F/76Me2N1OtnzuexvcWRnL9EJ7Mk5TdIkWlp5uFtFP5QvIgcBDj25
ejgfSiZDO7xOHku1yvZvNYKwSc5MfGEHKeozeIGyRiSu3TUhB3f/dQ0lpbxLPXJC
IaDfefeNAARHUna5Hr8gJs8rGhy6fZoTiSm4NgDz5/yEiS/4dXr7E1mufooEsgtn
+7RQ0KvVycCfB/WjoxrCyIOvHWKbi5debcdS+ANBeW06su8nmuG78+dRT4l/q6w=
=nBye
-----END PGP SIGNATURE-----



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E80E7CA.90902>