[Buildroot] backtrace patch and execinfo.h missing on uclibc

[Buildroot] backtrace patch and execinfo.h missing on uclibc

[Sebastián Treu]

Hi,

I have read another threads about it without any success on solve my
problem. I also ask in IRC and gently they told me about a patch. But
without any more information, and I didn't continue asking to don't
bother people there. I don't like to bother anywhere, but I can't
manage to solve my problem.

I patched manually with the patch:
http://repo.or.cz/w/buildroot.git/blob_plain/HEAD:/toolchain/gcc/4.4.1/301-missing-execinfo_h.patch

But execinfo.h does not appears on the include directory. I'm not
really looking for a solution, I mean, If someone tell me that it's
imposible to build that package with uclibc toolchain, then I'll see
what to do. Maybe I'll switch to glibc and make all the systems
again...such a pitty.

I have also tried pasting the execinfo.h file from glibc toolchain
made by the openwrt source without success. It found the file
included, but errors on function definitions arrives.

I thought in building that package only with glibc, and I asked that
on IRC. They told me that it's hard to get it working like that.

If someone can reply this with the no-solution or the solution I will
be pleased.

Thanks in advance,
Best regards,
-- 
If you want freedom, compile the source. Get gentoo.

Sebasti?n Treu
http://labombiya.com.ar

[Buildroot] backtrace patch and execinfo.h missing on uclibc

[Thomas Petazzoni]

On Sun, 14 Feb 2010 04:26:28 -0300
Sebasti?n Treu <sebastian.treu@gmail.com> wrote:

> I have read another threads about it without any success on solve my
> problem. I also ask in IRC and gently they told me about a patch. But
> without any more information, and I didn't continue asking to don't
> bother people there. I don't like to bother anywhere, but I can't
> manage to solve my problem.

Can you explain what your problem is ?

I.e: give your .config file, tell us about the error you're having, how
we can reproduce it, etc.

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

[Buildroot] backtrace patch and execinfo.h missing on uclibc

[Sebastián Treu]

Hi Thomas,

On Sun, Feb 14, 2010 at 7:44 AM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Can you explain what your problem is ?

I made a fs with buildroot using uclibc with native tools to compile
on an embedded device (some package can't be crosscompiled, or are
hard to understand how). I have compiled successfully  a lot of
packages, perl, gnutls, zlib, bzip, etc. I crosscompiled mysql (native
I ran out of memory) successfull too, with the same toolchain (not
actually the same, the one you use to crosscompile but the same that
uses buildroot to build the native toolchain and the fs).

Using the native compiler and toolchain in the device to build
ZoneMinder, I get an error about the header file missing: execinfo.h.
I have read that this header is used to implement backtrace. The error
is simply that "no such file or directory", and in fact that file
isn't found by me when searching it in the native toolchain or in the
crosscompile toolchain. Trying to crosscompile I had another errors
too, for example: "asm imposible constraint" but when looking the
code, the line was the FD_ISSET macro from select. (?) Anyway,
execinfo.h is not generated neither in the native nor in the cross.

I use openwrt too. I have seen that If I build a crosscompile
toolchain with glibc, execinfo.h is located in the includes files, but
there's no such file with uclibc. Now I'm using that toolchain to
crosscompile all the things, make the openwrt kernel, the fs and see
If it works. Unfortunately, openwrt doesn't build a native toolchain
so I need to crosscompile everything.

But...continuing with problems I get an error with that toolchain
crosscompiling the needed package! (bad luck? nah...) I won't ask for
help about that toolchain as isn't the topic of this list. In other
instance I'll see what to do on #openwrt.


Synthesis:
--------------
Error: execinfo.h no such file or directory. (on native build)

Toolchain: From buildroot-2009.11
Linux Headers: 2.6.31.x
uClibc: 0.9.30.1
binutils: 2.19.1
gcc:
Configured with: /usr/src/buildroot/buildroot-2009.11/output/toolchain/gcc-4.3.
4/configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=mips-linux-uclibc
--target=mips-linux-uclibc --enable-languages=c,c++ --with-gxx-include-dir=/usr
/include/c++ --disable-__cxa_atexit --with-gnu-ld --disable-libssp --enable-tls
 --enable-shared --disable-nls --enable-threads --disable-multilib --disable-de
cimal-float --with-float=soft --with-abi=32 --with-tune=mips32
Thread model: posix
gcc version 4.3.4 (GCC)

And I put the .config with nopaste to not flood the email:
http://pastie.org/824917

Thanks again for your interest.
Regards,
-- 
If you want freedom, compile the source. Get gentoo.

Sebasti?n Treu
http://labombiya.com.ar

[Buildroot] backtrace patch and execinfo.h missing on uclibc

[Thomas Petazzoni]

Hi Sebastian,

On Sun, 14 Feb 2010 20:42:54 -0300
Sebasti?n Treu <sebastian.treu@gmail.com> wrote:

> I made a fs with buildroot using uclibc with native tools to compile
> on an embedded device (some package can't be crosscompiled, or are
> hard to understand how). I have compiled successfully  a lot of
> packages, perl, gnutls, zlib, bzip, etc. I crosscompiled mysql (native
> I ran out of memory) successfull too, with the same toolchain (not
> actually the same, the one you use to crosscompile but the same that
> uses buildroot to build the native toolchain and the fs).
> 
> Using the native compiler and toolchain in the device to build
> ZoneMinder, I get an error about the header file missing: execinfo.h.
> I have read that this header is used to implement backtrace. The error
> is simply that "no such file or directory", and in fact that file
> isn't found by me when searching it in the native toolchain or in the
> crosscompile toolchain.

uClibc doesn't implement the backtrace() function, which is a
glibc-specific function.

You should compile ZoneMinder with -enable-crashtrace=no.

Anyway, I would recommend cross-compiling rather than doing native
compilation. The installation of development tools to the target is not
very well tested/supported in Buildroot.

> Trying to crosscompile I had another errors too, for example: "asm
> imposible constraint" but when looking the code, the line was the
> FD_ISSET macro from select. (?) Anyway, execinfo.h is not generated
> neither in the native nor in the cross.

Could you be more specific ? Which package ?

> I use openwrt too. I have seen that If I build a crosscompile
> toolchain with glibc, execinfo.h is located in the includes files, but
> there's no such file with uclibc. Now I'm using that toolchain to
> crosscompile all the things, make the openwrt kernel, the fs and see
> If it works. Unfortunately, openwrt doesn't build a native toolchain
> so I need to crosscompile everything.

As said above, backtrace() is a glibc-specific function, so any glibc
toolchain will contain it, while any uclibc toolchain won't contain
it.

Cheers,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com