From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: commit 806811bf2d72827d3031bfcd5dbab1e82324d34e breaks distros
Date: Fri, 16 Oct 2009 22:59:11 -0400 [thread overview]
Message-ID: <4AD932FF.9000107@balister.org> (raw)
In-Reply-To: <4AD90574.1080800@mwester.net>
[-- Attachment #1: Type: text/plain, Size: 1265 bytes --]
On 10/16/2009 07:44 PM, Mike Westerhof wrote:
> The following commit breaks numerous non-angstrom distros:
>
> commit 806811bf2d72827d3031bfcd5dbab1e82324d34e
> Author: Denys Dmytriyenko<denis@denix.org>
> Date: Wed Oct 14 14:25:07 2009 -0400
>
> angstrom: clean ups of the external toolchain support
>
>
> The symptom of the problem is this:
>
> $ bitbake slugos-image
> ERROR: Unable to parse conf/bitbake.conf (Could not include required
> file conf/distro/include/glibc.inc)
> $
>
> It seems that glibc.inc has been removed, and possibly replaced by
> either an external or an internal variant, but no non-angstrom distros
> have been updated.
>
> Please forgive me if there was a discussion of this change on the
> mailing list; I have been locked away behind corporate firewalls, and
> living on-the-road for the past months, and just haven't been able to
> keep up. :(
>
> How do I fix this, please?
Denys works a 9-5 real job. I'll try and chase him down over the weekend.
Philip
>
> -Mike (mwester)
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3316 bytes --]
next prev parent reply other threads:[~2009-10-17 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 23:44 commit 806811bf2d72827d3031bfcd5dbab1e82324d34e breaks distros Mike Westerhof
2009-10-17 2:59 ` Philip Balister [this message]
2009-10-17 3:13 ` Denys Dmytriyenko
2009-10-17 21:35 ` Khem Raj
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=4AD932FF.9000107@balister.org \
--to=philip@balister.org \
--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.