From: Cristian Ionescu-Idbohrn <cristian.ionescu-idbohrn@axis.com>
To: buildroot@busybox.net
Subject: [Buildroot] [patch] here are some more cleanup patches
Date: Wed, 19 Sep 2007 21:06:54 +0200 (CEST) [thread overview]
Message-ID: <0709192052250.18886@somehost> (raw)
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?
Cheers,
--
Cristian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: br-2007-09-19.submit.patch
Type: text/x-diff
Size: 21699 bytes
Desc:
Url : http://busybox.net/lists/buildroot/attachments/20070919/91ad3bcd/attachment-0001.bin
next reply other threads:[~2007-09-19 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 19:06 Cristian Ionescu-Idbohrn [this message]
2007-09-19 19:36 ` [Buildroot] [patch] here are some more cleanup patches Bernhard Fischer
2007-09-20 9:20 ` [Buildroot] [CFT, PATCH] libelf 64bit problems vs. ltrace Bernhard Fischer
2007-09-21 15:02 ` Bernhard Fischer
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=0709192052250.18886@somehost \
--to=cristian.ionescu-idbohrn@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.