Date: Tue, 11 Apr 2006 12:20:29 -0700 From: Sean McNeil <sean@mcneil.com> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: freebsd-amd64@freebsd.org, freebsd-ports@freebsd.org Subject: Re: relocation R_X86_64_32 can not be used (Was: Re: (no subject)) Message-ID: <1144783229.79147.6.camel@triton.mcneil.com> In-Reply-To: <20060411191128.GA5576@troutmask.apl.washington.edu> References: <20060410235910.F1096@ganymede.hub.org> <20060411002924.E1096@ganymede.hub.org> <20060411033619.GA1495@troutmask.apl.washington.edu> <20060411010839.Q1096@ganymede.hub.org> <20060411043016.GA1866@troutmask.apl.washington.edu> <20060411150640.G1096@ganymede.hub.org> <20060411191128.GA5576@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2006-04-11 at 12:11 -0700, Steve Kargl wrote: > On Tue, Apr 11, 2006 at 03:07:08PM -0300, Marc G. Fournier wrote: > > On Mon, 10 Apr 2006, Steve Kargl wrote: > > > > >>cc -c -I/usr/include -static -DNO_IDEA memory.c > > >>cc -shared -o common.o stream.o registry.o config.o memory.o > > > ^^^^^^^ > > > > > >This isn't -static. > > > > You said to add it to CFLAGS ... which variable defines -shared vs > > -static? > > > > It appears the resin port doesn't use CFLAGS when cc is used > as the loader. I admit I forgot the other solution of adding > -fPIC to generate the needed symbols. Typically, *FLAGS depend on what you are doing: CFLAGS object files from C source CXXFLAGS object files from C++ source CPFLAGS C/C++ preprocessing. Sometimes added to above LDFLAGS executable from object files This has been a pretty consistent rule from what I've seen. So I would think the -shared is in his LDFLAGS. Cheers, Sean
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1144783229.79147.6.camel>