All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [beagleboard] Unable to build Angstrom meta-toolchain
Date: Fri, 19 Aug 2011 07:32:54 -0700	[thread overview]
Message-ID: <4E4E7416.1070105@gmail.com> (raw)
In-Reply-To: <4E4E62AB.1050603@balister.org>

On 8/19/2011 6:18 AM, Philip Balister wrote:
> On 08/19/2011 02:33 AM, Stefan Herbrechtsmeier wrote:
>> Am 18.08.2011 19:48, schrieb Peter Housel:
>>> On Thu, 2011-08-18 at 15:10 +0200, fabian büttner wrote:
>>>> Hi,
>>>>
>>>> I am having troubles compiling the Angstrom SDK.
>>>>
>>>> I used the angstrom-setup-scripts to configure OE, sourced the
>>>> environment settings and built the base-image/console-image with
>>>> bitbake.
>>>>
>>>> While trying to compile the meta-toolchain, just when bitmake finishes
>>>> downloading task-sdk-bare_1.0-r2.6_armv7a.ipk, I am getting an error
>>>> output like this:
>>>>
>>>> http://pastie.org/2390409
>>>>
>>>> After that, I tried building the meta-toolchain(i did a bitmake clean
>>>> meta-toolchain) without '-j2' but the error I receive is ultimately
>>>> the same:
>>>> * satisfy_dependencies_for: Cannot satisfy the following dependencies
>>>> * for task-sdk-bare:
>>>> * libstdc++-dev *
>>>> * opkg_install_cmd: Cannot install package task-sdk-bare.
>>>>
>>>> Unfortunately I am too unexperienced with OE/Angstrom to fix bugs
>>>> like that.
>>>> Maybe someone could give me a hint how to get around this show-stopper?
>>> I can confirm that I've been seeing this as well on recent
>>> 2011.03-maintenance, but haven't had a chance to troubleshoot the root
>>> cause yet.
>>>
>> It was inbtroduced with commit 105d881227d06f31c180dffb777ee63361b2f2b8
>> "gcc: Package libstdc++ gdb python helpers into dev package".
>> If no helpers exist the empty package will not be generated.
>> I have try to add
>> ALLOW_EMPTY_libstdc++-dev = "1"
>> to gcc-package-cross.inc but this breaks meta-toolchain as the files in
>> ${prefix}/${TARGET_SYS}/usr/include/c++ are missing.
>>
>> Only removing libstdc++-dev package from gcc-package-cross.inc fix the
>> problem.
>
> Does anyone know if dv has the same problem? I can't check easily at the
> moment.

what happens if you remove  libstdc++-dev libgcc-dev from PACKAGES in 
recipes/gcc/gcc-package-cross.inc ?
I will see if I can reproduce it here
>
> Philip
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




  reply	other threads:[~2011-08-19 14:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-18 13:10 [beagleboard] Unable to build Angstrom meta-toolchain fabian büttner
2011-08-18 17:48 ` Peter Housel
2011-08-18 19:45   ` fabian büttner
2011-08-19  9:33   ` Stefan Herbrechtsmeier
2011-08-19 13:18     ` Philip Balister
2011-08-19 14:32       ` Khem Raj [this message]
2011-08-19 16:58         ` Stefan Herbrechtsmeier
2011-08-19 19:12           ` fabian büttner
2011-08-22  8:41             ` Stefan Herbrechtsmeier
2011-08-19 21:03         ` fabian büttner
2011-08-19 22:05           ` Khem Raj
2011-08-19 22:35             ` fabian büttner
2011-08-19 23:31               ` Paul Menzel
2011-08-19 23:34               ` Paul Menzel
2011-08-20  9:55                 ` fabian büttner
2011-08-22  9:01                   ` Stefan Herbrechtsmeier
  -- strict thread matches above, loose matches on Subject: below --
2011-08-18 12:57 fabian büttner

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=4E4E7416.1070105@gmail.com \
    --to=raj.khem@gmail.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.