libc update progress?

Jeroen Ruigrok/asmodai asmodai at
Sat Apr 30 02:55:05 PDT 2005

I think we got a ton more problems.

Right now I cannot even compile perl 5.8.6 or python 2.4.1 normally without
running into linking issues:

ld -Wl, -o li Modules/getbuildinfo.o  Parser/acceler.o  .......
/usr/libexec/binutils215/elf/ld: warning: cannot find entry symbol _start;
defaulting to 08048b38

cc -o -L/usr/local/lib perl.o malloc.o gv.o toke.o perly.o op.o pad.o
 regcomp.o dump.o util.o mg.o reentr.o hv.o av.o run.o pp_hot.o sv.o pp.o scope.
o pp_ctl.o pp_sys.o doop.o doio.o regexec.o utf8.o taint.o deb.o universal.o xsu
tils.o globals.o perlio.o perlapi.o numeric.o locale.o pp_pack.o pp_sort.o  -lm
-lcrypt -lutil -lc
/usr/lib/crt1.o(.text+0x89): In function `_start':
/usr/src/lib/csu/i386/crt1.c:123: undefined reference to `main'

I find it a bit hard to think that such wide spread programs would be
messing up on this front, my take is that binutils 2.15's configuration
might be a kind too clean.  From what I remember it's a matter of
--dynamic-linker, which cc should automatically pass along to ld.  But that
makes me wonder about the perl case.

Ruby, on the other hand did/does compile.

Jeroen Ruigrok van der Werven <asmodai(at)> / asmodai / kita no mono
Free Tibet! |   |
A place for everything, and everything in its place...

More information about the Kernel mailing list