> No, it's not. gcc's just not dumb enough to try to link a.out binaries
> against elf libs, so it keeps looking until it find's the a.out ones,
> and would give you an error if it couldn't. It finds them because they
> are in /etc/ld.so.conf, and consequently /etc/ld.so.cache (/lib &
> /usr/lib are assumed as common places to keep libs).
>
> > The library directory names I have seen used are i486-linux (ELF),
> > i486-linuxaout (a.out), i486-unknown-linuxoldld, m68k-linuxaout,
> > sparc-sun-solaris2, sparc-sun-sunos4.1, m68k-linux, and
> > alpha-linux. I'm sure there are others.
> >
>
> Anything is fine, as long as you put it in /etc/ld.so.conf (and run
> ldconfig), ld, and ld.so really couldn't care less where they are.
/etc/ld.so.conf, ld.so and ldconfig are for the dynamic linking process
when a process is started. This has nothing to do with the job of
gcc which calls ld with the appropriate options that tell ld where it
can find all the object files and libraries to produce an excecutable.
Ralf