[uClibc] pthread_mutexattr_settype undefined in cvs
Manuel Novoa III
mjn3 at codepoet.org
Fri Feb 13 02:15:24 UTC 2004
On Fri, Feb 13, 2004 at 09:45:13AM +0800, Selwyn Tang wrote:
> On 02/12/04 12:57, Manuel Novoa III wrote:
> > It built fine here in a native environment. For an explanation of
>
> Do you mean an environment using uClibc? Is it from cvs or 0.9.26? (But
> I think the parts of the code I concern did not change from 0.9.26).
I mean a buildroot-generated rootfs for i386.
> > The function pthread_mutexattr_settype is not part of libc. It is
> > in libpthread. The configure step should have arranged to add -lpthread
> > to the link.
>
> Maybe it's due to the problem of autotools in my buildroot environment.
> Now, I have recompiled libtools, autoconf and automake inside my
> chroot'd environment, and the autogen.sh and configure scripts no longer
> output any warnings about invalid syntax for autom4ke or things like
> that. The build of my directfb is smooth now.
That could have been the cause. I had no problems with the versions
build with buildroot.
> But my concern is that when I compiled autotools inside my buildroot
> development environment, are they built to run on my target? To my
> understanding, the buildroot development environment is meant to be run
> on my host, and to produce binaries for my target. But since my host and
> target are both of the x86 architecture, this problem just doesn't
> matter. So I don't know if I understand it correctly, and if my way of
> recompiling autotools inside the buildroot environment correct.
The rootfs image created by buildroot is _for_ the target. But if
the build and target archs are the same, then you can chroot into it
and it is essentially a native environment. If build and target
archs are not the same, then you need to cross compile, which adds
complications of course. Hence all the buildroot/make/*.mk files
and the various settings in the main Makefile.
Manuel
More information about the uClibc
mailing list