public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Build problems due to invalid libtool arguments
Date: Tue, 27 Dec 2011 14:21:09 +0000 (UTC)	[thread overview]
Message-ID: <loom.20111227T151414-642@post.gmane.org> (raw)
In-Reply-To: 4EF9997B.2020001@wonkology.org

Alex Schuster <wonko <at> wonkology.org> writes:


> > as fast.  Change to 'MAKEOPTS="-j1"' and see what happens.

 +1


> I still get the same error. And the emerge -e also did not clean things up.

Yep. Sometimes on setting up a new system, I lower the bar on what I install,
resync the system and a day or 2 later, complete the install.


My little catch all, after hacking at the system is:

env-update && source /etc/profile && etc-update && eix-update

Run it often and resync every 12 hours too.

Also check your profile.


On lib tool, see if you have this script and run it:

fix_libtool_files.sh 3.3.4

Not sure where I found that puppy, but hopefully it fixes your
issues with libtool.


Just shots in the dark, YMMV!


James




  reply	other threads:[~2011-12-27 14:23 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
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     ` James [this message]
2011-12-29  8:56       ` [gentoo-user] " 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=loom.20111227T151414-642@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --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