Date: Fri, 01 Aug 1997 19:20:54 -0700 From: Amancio Hasty <hasty@rah.star-gate.com> To: John Polstra <jdp@polstra.com> Cc: current@freebsd.org Subject: Re: second post: elf patches for -current Message-ID: <199708020220.TAA07109@rah.star-gate.com> In-Reply-To: Your message of "Fri, 01 Aug 1997 18:46:10 PDT." <199708020146.SAA09667@austin.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Tnks I will give it a try. Really, interested on this stuff for large C++ packages such as ACE. I suggest that you add a little README.current to your elfkit directory mostly because I think thats where people will go for information about elf on FreeBSD at any rate thats what I did 8) Tnks again, Amancio >From The Desk Of John Polstra : > In article <199708011006.DAA03932@rah.star-gate.com>, > Amancio Hasty <hasty@rah.star-gate.com> wrote: > > > > I downloaded the elfkit from John's ftp site and noticed that the > > README file was dated from 1996/04/16 and that it requires the > > include files from FreeBSD 2.1 . > > > > Doesn't make sense that we should patches for freebsd -current that > > does not require the include files from 2.1? > > ElfKit is almost obsolete, because just about everything you need > is now in -current. You can build the FreeBSD compiler for ELF by > specifying "BINFORMAT=elf". The standard libc in -current (and I > think in -2.2 also) can be built for ELF, and it works just fine. > You don't have to do anything special; just compile it with the > ELF tools. > > The current version of GNU binutils has all the FreeBSD-ELF support > in it. Just configure it like this and then build it: > > ./configure --prefix=/usr/local/elf --host=i386-unknown-freebsd \ > --target=i386-unknown-freebsdelf > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "Self-knowledge is always bad news." -- John Barth
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708020220.TAA07109>