From: Tom Rini <tom_rini@mentor.com>
To: Andreas Fenkart <andreas.fenkart@streamunlimited.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 0/1] gcc-cross-sdk: fix C++ headers include, bump PR.
Date: Tue, 20 Jul 2010 11:29:46 -0700 [thread overview]
Message-ID: <4C45EB1A.1060407@mentor.com> (raw)
In-Reply-To: <20100720112607.GA9142@biggy>
Andreas Fenkart wrote:
> Hi
>
> The location of C++ headers has changed in gcc-cross-sdk_4.3.x
> and above. See error message during packaging step:
>
> NOTE: the following files were installed but not shipped in any package:
> NOTE: /opt/angstrom/arm/arm-angstrom-linux-uclibcgnueabi/include/c++/4.3.2/ios
> NOTE: /opt/angstrom/arm/arm-angstrom-linux-uclibcgnueabi/include/c++/4.3.2/map
> NOTE: /opt/angstrom/arm/arm-angstrom-linux-uclibcgnueabi/include/c++/4.3.2/new
> ...
I'm looking into these patches and the possible reasons for this and
that to happen as it does.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-07-20 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 11:26 [PATCH 0/1] gcc-cross-sdk: fix C++ headers include, bump PR Andreas Fenkart
2010-07-20 11:26 ` [PATCH 1/1] " Andreas Fenkart
2010-07-20 18:29 ` Tom Rini [this message]
2010-07-20 19:46 ` [PATCH 0/1] " Tom Rini
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=4C45EB1A.1060407@mentor.com \
--to=tom_rini@mentor.com \
--cc=andreas.fenkart@streamunlimited.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox