public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Houser <chouser@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: [gentoo-dev] binutils / gcc / objprelink
Date: Tue Sep 25 12:11:01 2001	[thread overview]
Message-ID: <20010925140847.A489082@plato.zk3.dec.com> (raw)

dev-util/objprelink depends on a /usr/lib/libiberty.a that includes
'htab_find_slot_with_hash' as well as other 'htab_*' things.

PROBLEM 1:
If this dependency is unresolved, the ebuild blindly continues, causing
later qt ebuilds to fail mysteriously.  The objprelink ebuild has now
been fixed in dev-util/objprelink-0-r1.ebuild.

But why would the libiberty dependency be unresolved, when the
objprelink ebuild clearly states that it depends on sys-devel/gcc
and sys-devel/binutils?

PROBLEM 2:
Both gcc-2.95.3-r5 and binutils-2.11.90.0.27 install (different)
/usr/lib/libiberty.a's, and the one gcc installs doesn't have the
'htab_*' functions that objprelink needs.

This problem is NOT solved.  It seems to me that gcc shouldn't be
installing a broken libiberty, but what do I know?  It also seems that
portage could try to catch this sort of problem during 'merge'.  It'd be
nice, anyway.

As a work-around, I re-merged binutils, which over-wrote gcc's
libiberty, and now objprelink builds fine.

PROBLEM 3:
This isn't directly related, but I noticed along the way that portage
seems to think that sys-devel/binutils-2.11.90.0.7 is newer than
sys-devel/binutils-2.11.90.0.27 -- that doesn't seem right.

--Chouser



                 reply	other threads:[~2001-09-25 18:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20010925140847.A489082@plato.zk3.dec.com \
    --to=chouser@gentoo.org \
    --cc=gentoo-dev@cvs.gentoo.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