From: Junqian Gordon Xu <xjqian@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: linux-libc-headers build problem for tosa
Date: Sun, 22 Apr 2007 02:54:23 -0500 [thread overview]
Message-ID: <462B14AF.50903@gmail.com> (raw)
I'm testing my OE build system after upgrading my host to Debian Lenny
(testing). host gcc version: gcc (GCC) 4.1.2 20061115 (prerelease)
(Debian 4.1.1-21), But I can't pass the stage of building
linux-libc-headers-2.6.xx in either Angstrom or OZ-3.5.5 distro.
My local.conf is minimally modified with machine=tosa and qemu-native
assumed.
Angstrom bug report: http://bugs.openembedded.org/show_bug.cgi?id=2128
OZ-3.5.5 bug report: http://bugs.openembedded.org/show_bug.cgi?id=2132
Any idea what's wrong?
Gordon
next reply other threads:[~2007-04-22 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 7:54 Junqian Gordon Xu [this message]
2007-04-22 10:17 ` linux-libc-headers build problem for tosa cyril Romain
2007-04-22 12:06 ` cyril Romain
2007-04-22 13:30 ` Richard Purdie
2007-04-22 19:39 ` Leon Woestenberg
2007-04-23 6:19 ` Junqian Gordon Xu
2007-04-23 7:14 ` Holger Freyther
2007-04-24 3:02 ` Junqian Gordon Xu
2007-04-25 14:19 ` Leon Woestenberg
2007-04-25 19:53 ` Justin Patrin
2007-04-28 4:50 ` Junqian Gordon Xu
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=462B14AF.50903@gmail.com \
--to=xjqian@gmail.com \
--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 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.