From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: strange error
Date: Fri, 22 Jul 2011 08:02:27 -0600 [thread overview]
Message-ID: <4E2982F3.1030802@mlbassoc.com> (raw)
In-Reply-To: <4E298200.1040302@nedap.com>
On 07/22/2011 07:58 AM, Jaap de Jong wrote:
> funny error when the OE_BASE dirname contains "-OS"
> It looks like it all occurrences in the gcc line with "-OS" are replaced by "-O1S" leading to a wrong path...
This is just one manifestation that seems to happen any time the build directory name contains "-".
My practice is to just avoid naming my OE build trees with "-" in them.
> | make[1]: Entering directory `/home/jdj/OE-OS/build/tmp-angstrom_2008_1/work/i686-linux/libgcrypt-native-1.4.1-r0/libgcrypt-1.4.1'
> | Making all in mpi
> | make[2]: Entering directory `/home/jdj/OE-OS/build/tmp-angstrom_2008_1/work/i686-linux/libgcrypt-native-1.4.1-r0/libgcrypt-1.4.1/mpi'
> | make[2]: Nothing to be done for `all'.
> | make[2]: Leaving directory `/home/jdj/OE-OS/build/tmp-angstrom_2008_1/work/i686-linux/libgcrypt-native-1.4.1-r0/libgcrypt-1.4.1/mpi'
> | Making all in cipher
> | make[2]: Entering directory `/home/jdj/OE-OS/build/tmp-angstrom_2008_1/work/i686-linux/libgcrypt-native-1.4.1-r0/libgcrypt-1.4.1/cipher'
> | `echo /bin/sh ../i686-linux-libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../src -I../src
> -isystem/home/jdj/OE-OS/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include -I/home/jdj/OE-OS/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include
> -isystem/home/jdj/OE-OS/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include -O2 -g -fvisibility=hidden -Wall -Wpointer-arith -c ./tiger.c | sed -e 's/-O[2-9s]*/-O1/g' `
> | i686-linux-libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../src -I../src -isystem/home/jdj/OE-O1S/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include
> -I/home/jdj/OE-O1S/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include -isystem/home/jdj/OE-O1S/build/tmp-angstrom_2008_1/sysroots/i686-linux/usr/include -O1 -g
> -fvisibility=hidden -Wall -Wpointer-arith -c ./tiger.c -fPIC -DPIC -o .libs/tiger.o
> | In file included from ../src/visibility.h:245:0,
> | from ../src/g10lib.h:39,
> | from ./tiger.c:26:
> | ../src/gcrypt.h:29:23: fatal error: gpg-error.h: No such file or directory
> | compilation terminated.
> | make[2]: *** [tiger.lo] Error 1
> | make[2]: Leaving directory `/home/jdj/OE-OS/build/tmp-angstrom_2008_1/work/i686-linux/libgcrypt-native-1.4.1-r0/libgcrypt-1.4.1/cipher'
> | make[1]: *** [all-recursive] Error 1
> | make[1]: Leaving directory `/home/jdj/OE-OS/build/tmp-angstrom_2008_1/work/i686-linux/libgcrypt-native-1.4.1-r0/libgcrypt-1.4.1'
> | make: *** [all] Error 2
> | + die 'oe_runmake failed'
> | + oefatal 'oe_runmake failed'
> | + echo FATAL: 'oe_runmake failed'
> | FATAL: oe_runmake failed
> | + exit 1
> NOTE: package libgcrypt-native-1.4.1-r0: task do_compile: Failed
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2011-07-22 14:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-22 13:58 strange error Jaap de Jong
2011-07-22 14:02 ` Gary Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-06-10 17:48 Strange error Mauro Ziliani
2017-03-06 12:15 Gary Thomas
2017-03-06 17:20 ` Matthew McClintock
2007-05-19 22:30 STRANGE ERROR Sasa Ostrouska
2007-05-19 23:34 ` Andrew Morton
2007-05-20 16:51 ` Vitaly Bordug
2004-08-30 21:26 Strange error Gérard Parat / F6FGZ
2003-04-13 10:38 Strange ERROR Stas Sergeev
2003-04-11 16:30 Jacek Nowosielski
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=4E2982F3.1030802@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.