From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: Still not solved: glibc-dbg and insane.bbclass
Date: Sun, 07 Jun 2009 20:21:09 +0200 [thread overview]
Message-ID: <h0h0el$60i$1@ger.gmane.org> (raw)
In-Reply-To: <20090607175542.GA26712@fh-wedel.de>
On 07-06-09 19:55, Martin Dietze wrote:
> Hi,
>
> just as my build broke again wiht this issue:
> glibc-package.bbclass defines PACKAGES which always contains
> glibc-dbg, however the build is without debug symbols for build
> time reasons. I guess eventually we'd like to configure from
> somewhere whether or not we want debug code and the glibc-dbg
> package.
>
> Do we have any "official" mechanism we can use to accomplish
> this? Since this is something which *always* breaks builds I'd
> think we should do something about this sooner rather than
> later.
What's exactly breaking? It's perfectly legal (and needed for
depchains!) for -dbg package to be empty.
regards,
Koen
next prev parent reply other threads:[~2009-06-07 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-07 17:55 Still not solved: glibc-dbg and insane.bbclass Martin Dietze
2009-06-07 18:21 ` Koen Kooi [this message]
2009-06-07 19:18 ` Martin Dietze
2009-06-08 5:35 ` Koen Kooi
2009-06-08 9:58 ` Martin Dietze
2009-06-07 23:28 ` Rolf Leggewie
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='h0h0el$60i$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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.