From: Pandu Poluan <pandu@poluan.info>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Build problems due to invalid libtool arguments
Date: Tue, 27 Dec 2011 08:15:28 +0700 [thread overview]
Message-ID: <CAA2qdGX3-+thuNUzLkVXqbyacbmJ_925_j6CDSeWsB4Q5AnMCw@mail.gmail.com> (raw)
In-Reply-To: <4EF8FBF2.6040006@wonkology.org>
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]
On Dec 27, 2011 6:01 AM, "Alex Schuster" <wonko@wonkology.org> wrote:
>
> I wrote:
>
> > The problem is that in the libtool linking phase the arguments "/usr/bin
> > /usr/sbin /bin /sbin" are given along the libraries and library paths. I
> > have no idea why this happens, and how to solve this. Something must be
> > wrong on my system. But what? For libggi, emerging with USE=-aalib sort
> > of solved this. But I have no idea what to do about pygtksourceview. As
> > all gthe KDE stuff seems to depend on this, I cannot continue
>
> I found a workaround, after looking more closely to the emerge -t
> output. pygtksourceview is needed when git is built only with the gtk
> USE flag. So I can continue, but it just happened again with
> dev-db/libiodbc, whatever this is, and whatever this may depend on.
> There is something wrong on this system, and I have no idea where to look.
>
Have you tried revdep-rebuild? python-updater?
Rgds,
[-- Attachment #2: Type: text/html, Size: 1168 bytes --]
next prev parent reply other threads:[~2011-12-27 1:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-26 18:23 [gentoo-user] Build problems due to invalid libtool arguments Alex Schuster
2011-12-26 22:57 ` Alex Schuster
2011-12-27 1:15 ` Pandu Poluan [this message]
2011-12-27 1:53 ` Alex Schuster
2011-12-27 8:08 ` Walter Dnes
2011-12-27 10:10 ` Alex Schuster
2011-12-27 14:21 ` [gentoo-user] " James
2011-12-29 8:56 ` Sebastian Beßler
2011-12-29 11:09 ` Pandu Poluan
2011-12-29 11:42 ` Dale
2011-12-27 14:37 ` [gentoo-user] " Michael Mol
2011-12-27 16:10 ` Dale
2011-12-27 16:32 ` [solved] " Alex Schuster
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=CAA2qdGX3-+thuNUzLkVXqbyacbmJ_925_j6CDSeWsB4Q5AnMCw@mail.gmail.com \
--to=pandu@poluan.info \
--cc=gentoo-user@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