public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arttu V." <arttuv69@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Only two people in the gentoo world is having this  problem?
Date: Fri, 12 Mar 2010 21:07:00 +0200	[thread overview]
Message-ID: <fecdbac61003121107i4c01296bxb3fabc06ad578f71@mail.gmail.com> (raw)
In-Reply-To: <47a330c51003120523n61a9d94dq58d132c50e1fae00@mail.gmail.com>

On 3/12/10, Damian <damian.only@gmail.com> wrote:
>> Bummer. Are you sure your libarchive.la is not another orphan, just
>> like liblzmadec.la was?
> Indeed.  libarchive.la is not owned by any package. Is this a symptom
> of a bigger problem?

Probably not, unless running Gentoo is considered a big problem. :)

You can read many things about the problems of dynamic vs static
linking from, e.g., flameeyes' blog.

>> Please check (if you are still interested in hunting down the cause).
> Sure, and I really appreciate the gentoo community help.

Ah, I got the impression that you might have been satisfied with USE="-lzma".

>> You should probably only end up with that la file if you have
>> USE="static-libs" for libarchive -- which (if I'm reading correctly
>> the paludis output attached in the bug) you do not have currently
>> enabled.
> That's correct. Should I enable static-libs and recompile libarchive?

I don't think so, but I don't know what your system is for. If the box
currently runs without the static libs then I'd guess you don't need
them. I think you might want to hear a third opinion, if someone else
has one to lend.

>> But since you have the libarchive.la file on your system you may have
>> had the USE flag enabled at one point, or the ebuild may have changed
>> to allow separate dynamic and static building while your package
>> manager might not have kept up with its records.
> Ok, if that's the case I will report it to the paludis developers.

Given Neil's comment I think it might not be a bug, but rather a nasty
"feature", apparently of portage as well (that was news to me).

-- 
Arttu V.



      parent reply	other threads:[~2010-03-12 19:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-10  8:28 [gentoo-user] Only two people in the gentoo world is having this problem? Damian
2010-03-10 13:02 ` Mark Knecht
2010-03-10 14:05   ` Damian
2010-03-10 14:10     ` Mark Knecht
2010-03-10 14:25       ` Damian
2010-03-10 16:18         ` Mark Knecht
2010-03-11 15:09           ` Damian
2010-03-10 14:08   ` Michele Alzetta
2010-03-10 15:41 ` Paul Hartman
2010-03-10 20:58 ` Arttu V.
2010-03-11 15:03   ` Damian
2010-03-11 15:51     ` Mark Knecht
2010-03-11 21:39       ` Arttu V.
2010-03-11 22:51         ` Mark Knecht
2010-03-12  8:05         ` Damian
2010-03-12  8:34           ` Damian
2010-03-12 12:16             ` Arttu V.
2010-03-12 13:23               ` Damian
2010-03-12 13:57                 ` Neil Bothwick
2010-03-12 19:10                   ` Arttu V.
2010-03-12 22:53                     ` Neil Bothwick
2010-03-13  2:26                   ` Walter Dnes
2010-03-13 11:13                     ` Neil Bothwick
2010-03-12 19:07                 ` Arttu V. [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=fecdbac61003121107i4c01296bxb3fabc06ad578f71@mail.gmail.com \
    --to=arttuv69@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