I was inquiring as to who here is running glibc 2.0.1, and has a.out
binaries with no ELF counterparts (doom, et. al., etc). e.g. I am using
the glibc with gcc 2.7.2.2, correctly installed and configured (everythin
bloody works when changing the linux headers to the gnu headers and a bit
of tweaking... well, all but uae ;)). I have a few existing a.out programs
that work, for which there is no elf counterpart... under glibc:
5:59 p2 [hagan] /home/neptho %xhexed
./xhexed: can't load dynamic linker '/lib/ld.so'
6:00 p2 [hagan] /home/neptho %/lib/ld.so `which xhexed`
xhexed: error in loading shared libraries
xhexed: cannot open shared object file: No such file or directory
6:01 p2 [hagan] /home/neptho %file `which xhexed`
/usr/X11/bin/xhexed: Linux/i386 demand-paged executable (ZMAGIC)
6:01 p2 [hagan] /home/neptho %cat `which xhexed` | sed s/ld.so/ld.ao/ > ~/test
6:01 p2 [hagan] /home/neptho %sudo ln -sf /lib/ld.so.1.8.10 /lib/ld.ao
6:01 p2 [hagan] /home/neptho %sudo ldconfig -v
6:01 p2 [hagan] /home/neptho %chmod 755 ~/test
6:01 p2 [hagan] /home/neptho %~/test
Hark, and there was program =).
My question remains, is glibc going to eventually support this old cryptic
a.out format for executables for the few programs that need it, or is this
cheap hack "The Only Viable Solution"?
Cheers,
Shawn
- http://neptho.needs.a.lobotomy.com/~neptho -
I wrote the worlds most optimizing compiler;
everything compiles down to a *single* NOP.