All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: OE Staging ABI Change Warning
Date: Mon, 03 Mar 2008 11:20:16 -0600	[thread overview]
Message-ID: <47CC3350.8010209@dls.net> (raw)
In-Reply-To: <1204303564.8126.38.camel@dax.rpnet.com>



Richard Purdie wrote:
> Hi,
>
> OE.dev is now just about ready to switch to using sysroot. The compilers
> have been updated to activate sysroot and the fixes I/Poky have for
> various pkgconfig issues have been committed....

Unslung now fails when building gcc-cross.  I presume this is a result 
of this activity (it build before the Feb 28 commits), but I do not 
understand the issues about sysroot and all well enough to even begin to 
be able to troubleshoot.  Is the patch attached to this original email 
supposed to fix this?  Is there something broken in the recipe, as 
implied by this thread, that I need to fix?  If so, what would that be?

[skipping over the normal compilation output in the logs...]
gcc -DIN_GCC -DHAVE_CONFIG_H 
-isystem/stuff/slug/unslung/tmp/staging/i686-linux/include -O2 -DIN_GCC 
-DCROSS_\
COMPILE -W -Wall -Wwrite-strings -Wstrict-prototypes 
-Wmissing-prototypes -pedantic -Wno-long-long -Wno-error\
 -DHAVE_CONFIG_H -DGENERATOR_FILE 
-isystem/stuff/slug/unslung/tmp/staging/i686-linux/include -W -Wall -Wwrite\
-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic 
-Wno-long-long  -Wno-error -I. -I.. -I/stuff/slug\
/unslung/tmp/work/gcc-cross-3.4.4-r8/gcc-3.4.4/gcc/fixinc 
-I/stuff/slug/unslung/tmp/work/gcc-cross-3.4.4-r8/g\
cc-3.4.4/gcc/fixinc/.. 
-I/stuff/slug/unslung/tmp/work/gcc-cross-3.4.4-r8/gcc-3.4.4/gcc/fixinc/../config 
-I/st\
uff/slug/unslung/tmp/work/gcc-cross-3.4.4-r8/gcc-3.4.4/gcc/fixinc/../../include  
-o fixincl fixincl.o fixtest\
s.o fixfixes.o server.o procopen.o fixlib.o 
/stuff/slug/unslung/tmp/work/gcc-cross-3.4.4-r8/gcc-3.4.4/build.i\
686-linux.armeb-linux/gcc/../libiberty/libiberty.a
echo timestamp > full-stamp
./fixincl -v < /dev/null
'fixincl version 1.1'
chmod 755 ../fixinc.sh
make[4]: Leaving directory 
`/stuff/slug/unslung/tmp/work/gcc-cross-3.4.4-r8/gcc-3.4.4/build.i686-linux.armeb-\
linux/gcc/fixinc'
The directory that should contain system headers does not exist:
  /stuff/slug/unslung/tmp/staging/armeb-linux/usr/include
make[3]: *** [stmp-fixinc] Error 1
make[3]: Leaving directory 
`/stuff/slug/unslung/tmp/work/gcc-cross-3.4.4-r8/gcc-3.4.4/build.i686-linux.armeb-\
linux/gcc'
make[2]: *** [all-gcc] Error 2
make[2]: Leaving directory 
`/stuff/slug/unslung/tmp/work/gcc-cross-3.4.4-r8/gcc-3.4.4/build.i686-linux.armeb-\
linux'
FATAL: oe_runmake failed



In particular, note the error message which claims that the 
...gcc-3.4.4/usr/include file does not exist.  No, it does not -- it's 
at ...gcc-3.4.4/include instead.

Thanks,
Mike (mwester)



  parent reply	other threads:[~2008-03-03 17:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-29 16:46 OE Staging ABI Change Warning Richard Purdie
2008-02-29 17:24 ` Leon Woestenberg
2008-02-29 18:04   ` Richard Purdie
2008-02-29 18:29     ` Leon Woestenberg
2008-02-29 22:43       ` Richard Purdie
2008-03-03  1:07 ` Holger Freyther
2008-03-03  9:37   ` Richard Purdie
2008-03-03 12:12     ` Holger Freyther
2008-03-03 12:46       ` Koen Kooi
2008-03-03 14:34         ` Richard Purdie
2008-03-03 14:43           ` Koen Kooi
2008-03-03 15:46           ` Rod Whitby
2008-03-03 16:14             ` Leon Woestenberg
2008-03-03 16:39               ` Leon Woestenberg
2008-03-03 17:20 ` Mike (mwester) [this message]
2008-03-04  0:08 ` Koen Kooi
2008-03-04 16:53 ` Koen Kooi
2008-03-06 12:42   ` Richard Purdie
2008-03-06 12:58     ` 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=47CC3350.8010209@dls.net \
    --to=mwester@dls.net \
    --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.