Date: Wed, 19 Apr 2006 14:27:40 -0400 From: Kris Kennaway <kris@obsecurity.org> To: Larry Rosenman <ler@lerctr.org> Cc: freebsd-ports@freebsd.org, 'Kris Kennaway' <kris@obsecurity.org> Subject: Re: -fPIC for a port that is just a library on amd64? Message-ID: <20060419182740.GA72235@xor.obsecurity.org> In-Reply-To: <02e801c663da$bbaa2c30$0202fea9@aus.pervasive.com> References: <20060419175036.GA71370@xor.obsecurity.org> <02e801c663da$bbaa2c30$0202fea9@aus.pervasive.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--cWoXeonUoKmBZSoM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Apr 19, 2006 at 12:57:32PM -0500, Larry Rosenman wrote:
> Kris Kennaway wrote:
>=20
> >>=20
> >> It's just compiling a static object (a libxdiff.a).
> >>=20
> >> I just submitted a patch to the port that if ${MACHINE} =3D=3D amd64 I
> >> do the CFLAGS+=3D -fPIC but I'm not sure that's acceptable to you
> >> folks on portmgr.=20
> >=20
> > How is this object used? Is it really supposed to be static?
> >=20
> > Kris
>=20
> I was going by the port which did NOT configure it with --enable-shared.
>=20
> It appears to build a shared object if I configure it with --enable-share=
d.
>=20
> I didn't look at the history of the port. It's currently a ports@ port, =
and
> the PR I sent (ports/96062)
> has me grab maintainership.
>=20
> If you want me to, I can update it to build shared, but I need to test it
> some.
OK, but you didn't answer my question :-)
Kris
--cWoXeonUoKmBZSoM
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)
iD8DBQFERoEbWry0BWjoQKURAnApAKD14mikYQiq4AKKEC/lJYI6hnjmngCg9atw
9kp/O5eqQOF0dhbXB+bDeHk=
=QE2z
-----END PGP SIGNATURE-----
--cWoXeonUoKmBZSoM--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060419182740.GA72235>