Date: Tue, 7 Mar 2006 14:26:06 -0500 From: Kris Kennaway <kris@obsecurity.org> To: pfgshield-freebsd@yahoo.com Cc: ports@FreeBSD.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: amd64 and -fPIC Message-ID: <20060307192606.GA56153@xor.obsecurity.org> In-Reply-To: <20060307190712.68220.qmail@web32713.mail.mud.yahoo.com> References: <20060307184210.GA33347@xor.obsecurity.org> <20060307190712.68220.qmail@web32713.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Mar 07, 2006 at 08:07:12PM +0100, pfgshield-freebsd@yahoo.com wrote:
>=20
> --- Kris Kennaway <kris@obsecurity.org> ha scritto:=20
>=20
> ...
> > >=20
> > > That doesn't solve the problem, which is: the static library is
> > > almost useless, and users might actually want or need to use the
> > > static library.
> >=20
> > Why do you say it's useless? The point of a static library is for
> > static linking, and this works fine on amd64 or any other
> > architecture.
> >=20
>=20
> The problem is mixing static and shared libraries: this is perfectly legal
Unjustified assertion.
> and
> very often desired in most platforms except on amd64
and other modern arc=
hitectures.
Kris
--AhhlLboLdkugWU4S
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.1 (FreeBSD)
iD8DBQFEDd5OWry0BWjoQKURAlydAJ4ys6yovSBvaGOg3nkddEN+5xT68ACfTGJN
JoL31Ab3onSvEcSy6kl+SyU=
=/cOZ
-----END PGP SIGNATURE-----
--AhhlLboLdkugWU4S--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060307192606.GA56153>