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]  Anyone else having libtool problems, especially if running ~amd64?
Date: Wed, 27 Feb 2008 16:01:06 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.02.27.16.01.05@cox.net> (raw)

I'm having problems with libtool errors.  It appears a patch may not be 
taking properly according to one of the log files (see the bug).  With 
xine-lib-1.1.10.1-r1, I tried plain CFLAGS/CXXFLAGS/LDFLAGS and tried 
MAKEOPTS=-j1, no difference.  The original ebuild merged fine for me on 
Feb. 11, but after -r1 failed I tried it again, and it fails now too, so 
it's something that changed since the 11th.  FWIW, my last system libtool 
update was Feb. 2 (so before the successful merge on the 11th), but I 
think xine-lib ships and uses its own version (many packages do).

revdep-rebuild doesn't show anything but a couple kde4-svn packages (from 
the kde overlay) to rebuild and they shouldn't be related.  gdb won't 
merge either, with similar but not identical libtool errors (xine-lib 
spits out the libtool usage, gdb doesn't, just says there's a libtool 
error).

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

Secure:           https://bugs.gentoo.org/show_bug.cgi?id=211644

-- 
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 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 16:01 Duncan [this message]
2008-02-27 19:21 ` [gentoo-amd64] Re: Anyone else having libtool problems, especially if running ~amd64? Duncan

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.16.01.05@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