From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: "Mats Kärrman" <Mats.Karrman@tritech.se>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: SDK build refers to existing installed SDK
Date: Wed, 26 Mar 2014 12:03:54 +0200 [thread overview]
Message-ID: <20140326100354.GA32501@lpalcu-linux> (raw)
In-Reply-To: <ED3E0BCACD909541BA94A34C4A164D4C5B3A652E@post.tritech.se>
On Wed, Mar 26, 2014 at 07:40:26AM +0000, Mats Kärrman wrote:
> On Wednesday, March 26, 2014 4:23 AM, Khem Raj wrote:
> > > Hi,
> > >
> > > I just ran into an unexpected error while doing some multitasking.
> > > Project is based on OE-core Dora "distroless".
> > >
> > > While my build machine was busy building a new SDK using "-c populate_sdk" I simultaneously deleted an older SDK that was installed under /usr/local and installed a different one. This resulted in the build stopping with the following error:
> > >
> > > | x86_64-oesdk-linux-gcc --sysroot=/home/makr/projects/xxx/svn/main/trunk/oe/build/tmp/sysroots/x86_64-nativesdk-oesdk-linux -DHAVE_CONFIG_H -I../ncurses -I/home/makr/projects/xxx/svn/main/trunk/oe/build/tmp/work/x86_64-nativesdk-oesdk-linux/nativesdk-ncurses/5.9-r15.1/ncurses-5.9/ncurses -isystem/home/makr/projects/xxx/svn/main/trunk/oe/build/tmp/sysroots/x86_64-nativesdk-oesdk-linux/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/include -D_GNU_SOURCE -DNDEBUG -I. -I../include -I/home/makr/projects/xxx/svn/main/trunk/oe/build/tmp/work/x86_64-nativesdk-oesdk-linux/nativesdk-ncurses/5.9-r15.1/ncurses-5.9/ncurses/../include -I/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/include -isystem/home/makr/projects/xxx/svn/main/trunk/oe/build/tmp/sysroots/x86_64-nativesdk-oesdk-linux/usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/include -O2 -pipe --param max-inline-insns-single=1200 -fPIC -c /home/makr/projects/xxx/svn/main/trunk/oe/build/tmp/work/x86
> _64-
> > > nativesdk-oesdk-linux/nativesdk-ncurses/5.9-r15.1/ncurses-5.9/ncurses/base/lib_beep.c -o ../obj_s/lib_beep.o
> > > | cc1: error: /usr/local/oecore-x86_64/sysroots/x86_64-oesdk-linux/usr/include: Permission denied
> > >
> > > The offending directory is given with an include directive which seems strange, building a new SDK should not poke around in an old one...
> > >
> > > Config & log files available on request.
> >
> > Was the installed SDK in your path that fed into the OE build env which was generating new SDK ?
>
> No, it was not.
> I have saved the output of "bitbake nativesdk-ncurses -e" if you're interested.
I had a quick look at the generated Makefile for nativesdk-ncurses and,
apparently, it seems to have -I${includedir} added to the compilation
flags. This doesn't look like the right thing...
laurentiu
>
> BR // Mats
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
prev parent reply other threads:[~2014-03-26 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-25 9:41 SDK build refers to existing installed SDK Mats Kärrman
2014-03-26 3:23 ` Khem Raj
2014-03-26 7:40 ` Mats Kärrman
2014-03-26 10:03 ` Laurentiu Palcu [this message]
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=20140326100354.GA32501@lpalcu-linux \
--to=laurentiu.palcu@intel.com \
--cc=Mats.Karrman@tritech.se \
--cc=openembedded-core@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