Hi! I just made up a cross-compiler for the HURD, but the linker has minor problems:
Given the minimal C program: -------- int main() { return(0); } --------- and this command line: ~$ i586-pc-gnu-gcc test.c I get this output: [blah bloh] /usr/local/lib/gcc-lib/i586-pc-gnu/2.96/collect2 -m elf_i386 -dynamic-linker /lib/ld.so crt1.o crti.o /usr/local/lib/gcc-lib/i586-pc-gnu/2.96/crtbegin.o -L/usr/local/lib/gcc-lib/i586-pc-gnu/2.96 /tmp/ccTC2c4u.o -lgcc -lc -lgcc /usr/local/lib/gcc-lib/i586-pc-gnu/2.96/crtend.o crtn.o /usr/local/bin/i586-pc-gnu-ld: cannot open crt1.o: No such file or directory collect2: ld returned 1 exit status Up to the link everything works fine, but then the compiler fronend (at least I guess it's responsible for that) passes the various .o files without leading path to the linker. The same thing done with the linux native linker prepend /usr/lib to them and evrything is ok. I can add the path manually, and I get an a.out (which hopefully will run on the HURD ;-)), so the linker itself should be okay. I guess this has something to do with the 'spec' file. I poked into it, but didn't understand it and could find no good documentation. Anybody out there who knows how I can get i586-pc-gnu-gcc to prepend /usr/local/i586-pc-gnu/lib automatically? Thanks, Andy -- Andreas Rottmann | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED] Pfeilgasse 4-6/725 | A-1080 Wien | Austria | Europe http://www.8ung.at/rotty | GnuPG Key: www.8ung.at/rotty/dru.asc Fingerprint | 3E9A C485 49A4 1D17 2EA7 2BA7 22AE C9BF 8173 6279 [one of 78,35% Austrians who didnīt vote for Haider!]