[PATCH] LibTomCrypt on amd64 and -fPIC

Kris Kennaway kris at obsecurity.org
Tue Sep 6 01:29:06 PDT 2005

On Mon, Sep 05, 2005 at 08:01:23PM -0400, Tom St Denis wrote:
> On 9/5/05, David O'Brien <obrien at freebsd.org> wrote:
> > On Wed, Aug 24, 2005 at 07:18:18PM -0700, shellreef at gmail.com wrote:
> > > To FreeBSD-amd64: Can we add -fPIC to make.conf? Are there any
> > > side-effects? (I'd prefer this as I use packages and would prefer to
> > > not compile from ports.)
> > 
> > No.  -fPIC should only be used to build shared libraries.  Not every
> > since piece of code compiled for AMD64.
> If the library doesn't build without -fPIC it's because they're using
> a custom compiler.  I've built LTC on 4.0.1, 3.4.4, 3.3.6 and 2.96
> boxes [it isn't stable on 4.01, 3.3.6 but it at least builds].

The issue is typically that the software tries to link a static
library (i.e. one compiled without -fPIC) against relocatable objects
(-fPIC), so the compiler version is not relevant.  This is only an
issue on some architectures like amd64, ia64 and sparc64.

Anyway, this port does seem to compile as-is on amd64.

-------------- 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-amd64/attachments/20050906/68cc9a4e/attachment.bin

More information about the freebsd-amd64 mailing list