public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge --depclean - libcurl.la
Date: Thu, 2 Jun 2011 10:22:20 -0500	[thread overview]
Message-ID: <BANLkTi=zbTY7+MCbkudUyfpNpXa6Uww5pg@mail.gmail.com> (raw)
In-Reply-To: <e7ce9ada6c5b.4de7a41b@optonline.net>

On Thu, Jun 2, 2011 at 9:54 AM,  <dhkuhl@optonline.net> wrote:
> emerge --depclean removed libcurl.la a few days ago.  I have a program
> that's not in world that uses it when built:  libtool complains that it's
> missing.  In /usr/lib64 there are libcurl .so files but no .la files.
>
> How can I get the libcurl.la library back and keep it so emerge
> --depclean doesn't remove it?

Have you run "lafilefixer --justfixit"? I wonder if you have old .la
files from packages emerged before portage 2.1.9.

After running it once, you shouldn't need it anymore since portage
will auto-fix them upon installation.

You should run the lafilefixer command before trying revdep-rebuild,
or else you might have a lot of unnecessary emerges.

AFAIK the usage of .la files is basically deprecated and only a few
packages still require them. Flameeyes posted a lot of details about
it on his blog last year. (http://blog.flameeyes.eu)



  reply	other threads:[~2011-06-02 15:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 14:54 [gentoo-user] emerge --depclean - libcurl.la dhkuhl
2011-06-02 15:22 ` Paul Hartman [this message]
2011-06-02 15:44   ` dhkuhl
2011-06-04  0:38     ` [gentoo-user] " walt
  -- strict thread matches above, loose matches on Subject: below --
2011-06-03 18:36 [gentoo-user] " dhk
2011-06-03 22:45 ` Mick
2011-06-04  0:48 dhkuhl
2011-06-06 11:53 dhk

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='BANLkTi=zbTY7+MCbkudUyfpNpXa6Uww5pg@mail.gmail.com' \
    --to=paul.hartman+gentoo@gmail.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