i486-linux v. i486-unknown-linux

i486-linux v. i486-unknown-linux

Post by Curti » Tue, 05 Mar 1996 04:00:00



After the configure script is run you can go into config.status and
change it from i?345o86-unknown-linux to i?345o86-linux.

Curtiss



>GNU things (gcc, binutils) install as i486-unknown-linux by default, but
>some of the precompiled binaries that are available are set up as
>i486-linux.  This has caused a little bit of pain for me.  It seems to me
>that we should standardize on i486-linux for ELF and i486-linuxaout for
>a.out.  This would mean getting FSF to change the canonical names for
>linux systems.  Any thoughts?  I couldn't find anything in the fsstnd
>about this.

>Grant

 
 
 

1. HELP!!:/usr/i486-unknown-linux-gnulibc1/bin/ld: no input files

I just installed glibc-2.0.4.  I followed the HOWTO to the letter.

I tried a test compile and got the following results:

linux:/work/tmp# gcc -o hello hello.c
/usr/i486-unknown-linux-gnulibc1/bin/ld: no input files

evidently, gcc is not passing an object file or something to ld.  Gcc
will generate an object file, but ld won't link it:

linux:/work/tmp# gcc -c hello.c
linux:/work/tmp# ls
hello.c  hello.o
linux:/work/tmp# ld hello.o
ld: warning: cannot find entry symbol _start; defaulting to 08048080
hello.o: In function `main':
hello.o(.text+0x9): undefined reference to `printf'

Does anyone have any ideas why this happens?

I am using Slakware 3.4, gcc 2.7.2.3

I need to get this working, because I have work I need to compile.
--
Matthew Vanecek


send me mail.  I appreciate your effort! :-)

Studies in Business Computers at the University of North Texas
http://www.unt.edu/bcis
*****************************************************************
Visit my Website at http://people.unt.edu/~mev0003
*****************************************************************
For 93 million miles, there is nothing between the sun and my shadow
except me. I'm always getting in the way of something...

2. Q: Setting up xdm in Slackware 7

3. /usr/lib/gcc-lib/i386-linux and /usr/lib/gcc-lib/i486-linux

4. Pascal compiler

5. When i486 is not i486 architecture

6. Embedded Domain

7. /usr/i486-linux/bin/ld: cannot open -lXt: No such file or directory

8. debugging a weird devfs/md problem...

9. Compiling and get /usr/i486-linux not found?

10. /usr/i486-linux/bin/ld can not find files that exist!

11. What is /usr/i486-linux?

12. Linux eats i486's

13. Linux on i486 with PCI bus?