public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: Anyone else having libtool problems, especially if running ~amd64?
Date: Wed, 27 Feb 2008 19:21:27 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.02.27.19.21.27@cox.net> (raw)
In-Reply-To: pan.2008.02.27.16.01.05@cox.net

Duncan <1i5t5.duncan@cox.net> posted pan.2008.02.27.16.01.05@cox.net,
excerpted below, on  Wed, 27 Feb 2008 16:01:06 +0000:

> I'm having problems with libtool errors.

> Standard bugz url: http://bugs.gentoo.org/show_bug.cgi?id=211644

Traced down, thanks to the help I got on-bug.  It was a PEBCAK in the 
form of a bum qt-4.4.0-svn-snapshot ebuild from the forums (needed for 
kde-svn-head, as kde 4.1 will require qt-4.4.0).  The bum ebuild put some 
garbage in a file in /etc/env.d/ that is in turn used by env-update to 
generate /etc/ld.so.conf, thus putting garbage in it.  libtool was trying 
to parse that garbage and of course failing.  Fixing the ebuild (well, 
tested by reverting to an in-tree version of it, qt-4.3.4, 
FEATURES=binpkg makes that about a ten second job) and remerging solved 
the problem. =8^)

It's anyone's guess how long it would have taken me to figure that out on 
my own, as I hadn't the foggiest what to check next, given that I'd 
already tried the usual CFLAGS/CXXFLAGS/LDFLAGS/MAKEOPTS resets and 
revdep-rebuild wasn't helping either.  The devs pointed me right to it, 
even if it wasn't their bug that was the problem. =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@lists.gentoo.org mailing list



      reply	other threads:[~2008-02-27 19:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 16:01 [gentoo-amd64] Anyone else having libtool problems, especially if running ~amd64? Duncan
2008-02-27 19:21 ` Duncan [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=pan.2008.02.27.19.21.27@cox.net \
    --to=1i5t5.duncan@cox.net \
    --cc=gentoo-amd64@lists.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