[uClibc]Undefined __libc_start_main

[Victor Odhner]

Thanks!  I had not realized my "make" of uClibc had created
a customized copy of gcc.  Works like a dream.

I might not have seemed as confused as I was, because of
a typo:

> > I have built a uClibc compiler on my RedHat 7.1 box, ...

Should have said:
> > I have built a uClibc LIBRARY on my RedHat 7.1 box, ...

... I didn't know I'd built a compiler.

Is there any place I should have found all this in
the documentation?

Could I help with documentation?  If someone would
point me at stuff I should pull together, I'd be happy
to build some HowTos.  But I'd need pointers to raw
material since it's not in my head ...

Vic

Erik Andersen wrote:
> 
> On Sun Nov 18, 2001 at 02:22:29PM -0700, Victor Odhner wrote:
> > I have built a uClibc compiler on my RedHat 7.1 box, targeted to
> > the i386 for debug use.  Any time I try to link a program, even
> > "hello world", I get this "undefined reference" message:
> >
> > /usr/lib/crt1.o: In function `_start':
> > /usr/lib/crt1.o(.text+0x1d): undefined reference to `__libc_start_main'
> >
> > I have tried tricks like "ld -e main", but nothing seems to
> > give me a program that starts.
> >
> > Please advise!
> 
> What commands are you trying to use to do the linking?
> You could just do a 'make' followed by a 'make install'
> and then use /usr/i386-linux-uclibc/usr/bin/i386-uclibc-gcc
> to compile things.  Or you can do something like
> 
>     PATH=/usr/i386-linux-uclibc/bin:$PATH make
> 
> Either one of those should so the Right Thing(tm),
> 
>  -Erik
> 
> --
> Erik B. Andersen             http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--
> 
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://uclibc.org/mailman/listinfo/uclibc