From: Jamie Lenehan <lenehan@twibble.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: problems doing bitbake task-base
Date: Wed, 13 Jun 2007 22:39:08 +1000 [thread overview]
Message-ID: <20070613123908.GA19284@twibble.org> (raw)
In-Reply-To: <ae36f8040706071545i772205b2m85d251b45c7f26d7@mail.gmail.com>
On Fri, Jun 08, 2007 at 08:53:49AM +1000, "Luís Cargnini" wrote:
> new problems:
> (BD06DC30:~/puc/instramed/openembedded) lvcargnini% bitbake task-base
> NOTE: Handling BitBake files: - (4588/4588) [100 %]
> NOTE: Parsing finished. 4373 cached, 0 parsed, 215 skipped, 0 masked.
> NOTE: build 200706071941: started
[...]
> SysV.xs:7:25: error: asm/page.h: No such file or directory
> make[1]: *** [SysV.o] Error 1
> make[1]: Leaving directory
> `/home/lvcargnini/puc/instramed/openembedded/tmp/work/i686-linux/perl-native-5.8.8-r11/perl-5.8.8/ext/IPC/SysV'
[...]
This is an issue with the version linux-headers not including
asm/page.h.
Creating an empty asm/page.h (in /usr/include) would get past this,
but could cause other issues.
Does the latest version of linux-headers for gentoo put this back or
is it gone for good? Checking the latest kernel here (not gentoo, I
don't use that) and it seems be getting installed as part of make
headers_install - so it looks like it's back. So you might want to
try the latest gentoo version of linux-headers before doing anything
else.
If you update your host to the latest version and it still has
problems then put a bug in the OE bug tracker and I can look at
fixing this. Perl is only including it in order to get the definition
of getpagesize which has been defined in unistd.h for a long time
now, so just removing that include for perl should (in theory) work
without any issues (unless you had a really old system?)
--
Jamie Lenehan <lenehan@twibble.org>
next prev parent reply other threads:[~2007-06-13 12:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-03 2:59 problems doing bitbake task-base Luís Cargnini
2007-06-03 18:13 ` Philip Balister
2007-06-03 19:27 ` Holger Freyther
2007-06-04 3:19 ` Luís Cargnini
2007-06-04 7:35 ` Koen Kooi
2007-06-04 12:55 ` Luís Cargnini
2007-06-04 13:01 ` Luís Cargnini
2007-06-04 13:19 ` Koen Kooi
2007-06-05 17:04 ` Luís Cargnini
2007-06-05 18:36 ` Luís Cargnini
2007-06-05 19:09 ` Holger Freyther
2007-06-05 19:51 ` Luís Cargnini
2007-06-05 21:01 ` Koen Kooi
2007-06-06 1:06 ` Luís Cargnini
2007-06-06 1:52 ` Luís Cargnini
2007-06-06 2:26 ` Luís Cargnini
2007-06-06 6:19 ` Koen Kooi
2007-06-06 6:42 ` Koen Kooi
2007-06-06 16:37 ` Luís Cargnini
2007-06-06 17:36 ` Luís Cargnini
2007-06-06 18:43 ` Luís Cargnini
2007-06-07 22:45 ` Luís Cargnini
2007-06-12 15:17 ` Luís Cargnini
2007-06-12 15:23 ` Koen Kooi
2007-06-12 16:34 ` Luís Cargnini
2007-06-12 16:46 ` Koen Kooi
2007-06-12 18:06 ` Luís Cargnini
2007-06-12 18:40 ` Luís Cargnini
2007-06-13 12:39 ` Jamie Lenehan [this message]
2007-06-13 16:31 ` Luís Cargnini
2007-06-14 1:35 ` Jamie Lenehan
2007-06-14 2:40 ` Luís Cargnini
2007-06-14 2:53 ` Jamie Lenehan
2007-06-18 13:14 ` Luís Cargnini
2007-06-20 16:48 ` Luís Cargnini
2007-06-22 4:57 ` Jamie Lenehan
[not found] ` <ae36f8040706212233kcaf86b0k9498869fce6cddff@mail.gmail.com>
2007-06-22 14:09 ` Luís Cargnini
2007-06-24 21:49 ` Luís Cargnini
2007-06-24 21:50 ` Luís Cargnini
2007-06-05 19:13 ` Michael Krelin
2007-06-05 19:51 ` Holger Freyther
2007-06-05 20:27 ` Michael Krelin
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=20070613123908.GA19284@twibble.org \
--to=lenehan@twibble.org \
--cc=openembedded-devel@lists.openembedded.org \
/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