This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hello, I suscessfully compiled a toolchain for MIPS big endian with gcc 3.4.1 and glibc 2.3.2, kernel 2.6.8.1. The statically-linked simple "Hello World" program works (either using MIPS-I instruction set or MIPS-II instruction set). I used crosstools-0.28-rc35 by Dan Kegel. There is only one thing I don't understand clearly : the organization of the resulting toolchain. In mips-unknown-linux-gnu/gcc-3.4.1-glibc-2.3.2/, I have : * A bin/ directory which contains binairies like mips-unknown-linux-gnu-gcc. * A mips-unknown-linux-gnu directory which itself contains a bin/ directory which contains binaries like gcc, ld, ar ... These binaries are the same as the one present in mips-unknown-linux-gnu (same MD5). So why are they present with another name at an other place ? More generally, what is this mips-unknown-linux-gnu directory ? It seems important because if I delete it, I can't compile a program anymore because glibc headers aren't present. The list of files of the resulting toolchain is available at http://thomas.enix.org/pub/crosstools-result-toolchain.gz Thanks, Thomas -- PETAZZONI Thomas - thomas.petazzoni@enix.org http://thomas.enix.org - Jabber: kos_tom@sourcecode.de KOS: http://kos.enix.org/ - Lolut: http://lolut.utbm.info Fingerprint : 0BE1 4CF3 CEA4 AC9D CC6E 1624 F653 CB30 98D3 F7A7 ------ Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/ Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |