From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Bad gcc packaging (libgcc-s1 instead of libgcc1)
Date: Fri, 16 Mar 2007 03:27:13 +1030 [thread overview]
Message-ID: <45F97AE9.8060705@whitby.id.au> (raw)
In-Reply-To: <1173959533.45f9336d50790@dominion.kabel.utwente.nl>
Koen Kooi wrote:
> I think putting a construction like
> gcc-package-cross.inc has:
>
> python do_package() {
> if bb.data.getVar('DEBIAN_NAMES', d, 1):
> bb.data.setVar('PKG_libgcc', 'libgcc1', d)
> bb.build.exec_func('package_do_package', d)
> }
>
> in gcc-package.inc should work. Could you test that?
That works here.
> Sorry for breaking everyones packages.
Apology accepted.
-- Rod
prev parent reply other threads:[~2007-03-15 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-15 11:00 Bad gcc packaging (libgcc-s1 instead of libgcc1) Rod Whitby
2007-03-15 11:52 ` Koen Kooi
2007-03-15 16:57 ` Rod Whitby [this message]
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=45F97AE9.8060705@whitby.id.au \
--to=rod@whitby.id.au \
--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