-fPIC for a port that is just a library on amd64?

Kris Kennaway kris at obsecurity.org
Wed Apr 19 17:51:04 UTC 2006


On Wed, Apr 19, 2006 at 12:35:07PM -0500, Larry Rosenman wrote:
> Kris Kennaway wrote:
> > On Wed, Apr 19, 2006 at 09:52:38AM -0500, Larry Rosenman wrote:
> >> What's the best way to get a port to add -fPIC to the compile for a
> >> port that generates just an archive library (textproc/libxdiff)?
> >> 
> >> I was able to force the issue with CFLAGS=-fPIC make;CFLAGS=-fpic
> >> make install, but it would be nice if the port could do it
> >> automagically. 
> > 
> > It would be nice if the software was already correct so it happened
> > automatically :-)
> > 
> >> The issue is that the pecl-xdiff extension uses this library and
> >> wants to be a shared object.
> > 
> > If it's only compiling a shared library object (not static object or
> > other binaries), then adding CFLAGS+= -fPIC to the port makefile is
> > acceptable.  Better, add it to the software makefile and contribute
> > your patch back upstream.
> > 
> > Kris
> 
> It's just compiling a static object (a libxdiff.a).
> 
> I just submitted a patch to the port that if ${MACHINE} == amd64 
> I do the CFLAGS+= -fPIC
> but I'm not sure that's acceptable to you folks on portmgr.

How is this object used?  Is it really supposed to be static?

Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20060419/492ded7c/attachment.pgp


More information about the freebsd-ports mailing list