Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Bad gcc packaging (libgcc-s1 instead of libgcc1)
Date: Thu, 15 Mar 2007 21:30:22 +1030	[thread overview]
Message-ID: <45F92746.2020608@whitby.id.au> (raw)

I'm getting a libgcc-s1 package emitted by gcc_4.1.1.bb instead of the
normal libgcc1.  This is poisoning all builds that depend on libgcc1,
and is polluting the slugos feeds with bad dependencies.

I believe it is caused by the patch in
http://lists.linuxtogo.org/pipermail/openembedded-commits/2007-March/004007.html

I have tested reverting that patch locally, and the libgcc-s1 package
was not emitted.

So I wish to revert that patch.

I'm looking for confirmation that this problem is happening to others.
I will revert the patch locally on our autobuilder, and wait for
confirmation before committing that reversion.

-- Rod



             reply	other threads:[~2007-03-15 11:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15 11:00 Rod Whitby [this message]
2007-03-15 11:52 ` Bad gcc packaging (libgcc-s1 instead of libgcc1) Koen Kooi
2007-03-15 16:57   ` Rod Whitby

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=45F92746.2020608@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