Date: Fri, 10 Mar 2000 18:55:34 -0600 From: Oscar Bonilla <obonilla@fisicc-ufm.edu> To: Chuck Robey <chuckr@picnic.mat.net> Cc: Oscar Bonilla <obonilla@fisicc-ufm.edu>, Alfred Perlstein <bright@wintelcom.net>, Kris Kennaway <kris@hub.freebsd.org>, freebsd-hackers@FreeBSD.ORG Subject: Re: inner workings of the C compiler Message-ID: <20000310185534.A94778@fisicc-ufm.edu> In-Reply-To: <Pine.BSF.4.21.0003101939150.32633-100000@picnic.mat.net> References: <20000310182602.A94174@fisicc-ufm.edu> <Pine.BSF.4.21.0003101939150.32633-100000@picnic.mat.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Mar 10, 2000 at 07:49:32PM -0500, Chuck Robey wrote: > Notice here the order it links, and what files it links in. First, if > you're using nostdlib, then you have to call out your own libs, all of > them, and you forgot to do libgcc. I've been able to move the lib calls I don't really need libgcc since I'm only calling funtions in libc, but... > before and after the object files, so I don't think that order matters, as > long as you get both, but the objects (in order) are: > > crt1.o crti.o crtbegin.o ccn35733.o (your obj, that is) , then > crtend.o crtn.o > > It calls out the ld-elf.so.1, but I don't think that's really linked > in. I've been doing all my stuff statically linked, so I could be wrong > on that part of it. I don't think you need to care about the -L calls, > because when you use the full path, -L doesn't really matter. > > Always remember that -v, when your messing with tools. > That ordering completly solved it!! thanks... now I can get back to getting the NSS code into libc. kind regards and many thanks, -oscar -- pgp public key: finger obonilla@fisicc-ufm.edu pgp fingerprint: 6D 18 8C 90 4C DF F0 4B DF 35 1F 69 A1 33 C7 BC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000310185534.A94778>