On Sun, 2005-07-24 at 22:25 +0100, Neil Williams wrote: > On Sunday 24 July 2005 7:55 pm, skaller wrote:
> > I'm talking about the binary package(s). > > Don't forget that Debian is on so many different platforms, compiling the > main.o on one platform is simply not going to work on others. I must be REALLY bad at explaining things! > Honest, take a look around a Debian system installed using only binary > packages. How many object files can you find? /usr/lib/gcc-lib/x86_64-linux/3.3.5/crtbegin.o /usr/lib/gcc-lib/x86_64-linux/3.3.5/crtbeginS.o /usr/lib/gcc-lib/x86_64-linux/3.3.5/crtbeginT.o /usr/lib/gcc-lib/x86_64-linux/3.3.5/crtend.o /usr/lib/gcc-lib/x86_64-linux/3.3.5/crtendS.o /usr/lib/crt1.o /usr/lib/crti.o /usr/lib/crtn.o /usr/lib/gcrt1.o /usr/lib/Mcrt1.o /usr/lib/Scrt1.o /usr/lib32/Mcrt1.o /usr/lib32/Scrt1.o /usr/lib32/crt1.o /usr/lib32/crti.o /usr/lib32/crtn.o /usr/lib32/gcrt1.o .. which suggests I should put the file in /usr/lib, same place gcc puts its stuff. The other option is /usr/lib/felix/rtl, which avoids cluttering /usr/lib: the felix standard library itself is in /usr/lib/felix/lib so that subdirectory name is already taken for a different purpose. -- John Skaller <skaller at users dot sourceforge dot net>
signature.asc
Description: This is a digitally signed message part
