From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [CFT, PATCH] libelf 64bit problems vs. ltrace
Date: Fri, 21 Sep 2007 17:02:44 +0200 [thread overview]
Message-ID: <20070921150244.GE5788@aon.at> (raw)
In-Reply-To: <20070920092033.GB27699@aon.at>
ping!
I'll happily keep this fixes local if noone cares to double-check that
they help others, too..
On Thu, Sep 20, 2007 at 11:20:33AM +0200, Bernhard Fischer wrote:
>On Wed, Sep 19, 2007 at 09:36:00PM +0200, Bernhard Fischer wrote:
>>On Wed, Sep 19, 2007 at 09:06:54PM +0200, Cristian Ionescu-Idbohrn wrote:
>>>but libvorbis fails to build:
>>>
>>> In file included from mdct.c:44:
>>> ../include/vorbis/codec.h:26:21: error: ogg/ogg.h: No such file or
>>> directory
>>>
>>>Can't seem to be able to build ltrace; something to do with configure not
>>>being able to locate gelf.h, but it's there:
>>>staging_dir/usr/include/libelf, as libelf build ok; I get a configure
>>>error:
>>>
>>> checking gelf.h usability... no
>>> checking gelf.h presence... no
>>> checking for gelf.h... no
>>> configure: error: ***** gelf.h not found *****
>>>
>>>config.log says in more than one place:
>>>
>>> /usr/include/libelf/gelf.h:49:2: error: #error "GElf is not supported on
>>> this sysystem."
>>>
>>>and bails out further down with:
>>>
>>> configure:3629: checking for gelf.h
>>> configure:3636: result: no
>>> configure:3643: error: ***** gelf.h not found *****
>>>
>>>ac_cv_header_gelf_h=no may have something to do with it.
>>>
>>>Any ideas?
>>
>>I've updated ltrace some months ago, but i admit that i have no idea
>>which box this big patches are on :-/
>>...
>>$ ls -ltrn buildroot.mine.OLD.OLD/package/ltrace/
>>total 804
>>-rw-r--r-- 1 1000 1000 627890 Apr 6 14:58 ltrace-svn-20070406.00.patch
>>-rw-r--r-- 1 1000 1000 173414 Apr 6 15:04 ltrace-svn-20070406.01.autoreconf.patch
>>-rw-r--r-- 1 1000 1000 2298 Apr 6 15:07 ltrace.mk
>>-rw-r--r-- 1 1000 40 241 Apr 6 15:25 Config.in
>>
>>I.e. Not too good.
>>
>>Perhaps try this updated version?
>
>The attached builds at least (with largefile enabled for a start).
>Can you confirm that this works for you so i can apply it?
>
>Too big for the list, so it's here:
>http://uclibc.org:/~aldot/buildroot/br2.libelf64-cluebait+ltrace-update.00.diff.bz2
>
>TIA for testing it..
next prev parent reply other threads:[~2007-09-21 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 19:06 [Buildroot] [patch] here are some more cleanup patches Cristian Ionescu-Idbohrn
2007-09-19 19:36 ` Bernhard Fischer
2007-09-20 9:20 ` [Buildroot] [CFT, PATCH] libelf 64bit problems vs. ltrace Bernhard Fischer
2007-09-21 15:02 ` Bernhard Fischer [this message]
2007-09-19 20:14 ` [Buildroot] [patch] here are some more cleanup patches Bernhard Fischer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070921150244.GE5788@aon.at \
--to=rep.dot.nop@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox