From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: staging problem
Date: Fri, 21 May 2010 08:47:32 -0600 [thread overview]
Message-ID: <4BF69D04.5060506@mlbassoc.com> (raw)
Trying a clean build
MACHINE="beagleboard"
DISTRO="angstrom-2008.1"
org.openembedded.dev 2c153f33b8ebb807a622ad9ae92ed5341a356740
I get failures like this (in many packages):
/local/Angstrom_BeagleBoard/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/regex.h:138: error: expected '=', ',', ';', 'asm' or '__attribute__' before 're_void'
/local/Angstrom_BeagleBoard/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/regex.h:298: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int'
/local/Angstrom_BeagleBoard/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/regex.h:307: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'int'
/local/Angstrom_BeagleBoard/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/regex.h:309: error: expected '=', ',', ';', 'asm' or '__attribute__' before 're_void'
/local/Angstrom_BeagleBoard/tmp/sysroots/armv7a-angstrom-linux-gnueabi/usr/include/regex.h:310: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'size_t'
The problem is that the compiler include file <regex.h> is
not the standard/default one, rather the file from tcl!
I replaced the bogus regex.h file with the correct one and
my build completes & runs.
* Any ideas how/why this happens? I'm sure it has to do with
the recent RP changes.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2010-05-21 14:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:47 Gary Thomas [this message]
2010-05-21 20:27 ` staging problem Khem Raj
2010-05-21 20:42 ` Koen Kooi
2010-05-21 22:17 ` Gary Thomas
2010-05-22 11:51 ` Gary Thomas
2010-05-22 19:25 ` Koen Kooi
2010-05-23 9:22 ` Koen Kooi
2010-05-23 15:17 ` Khem Raj
2010-05-23 15:59 ` Koen Kooi
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=4BF69D04.5060506@mlbassoc.com \
--to=gary@mlbassoc.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.