thunderbird preparation: We've already been run in this tree

javeree · Guru Joined: 29 Jan 2006 Posts: 453

I try to emerge thunderbird-7.0.1-r1 and get following output in /var/log/portage/elog/mail-client:thunderbird-7.0.1-r1:20111121-152922.log and get a weird error in the 'prepare' step, followed by a killed ld during the compile. Obviously, this is not a common error (or else the ebuild would have not gone stable), but I could not find any mention of this error in google.

Aquous · l33t Joined: 08 Jan 2011 Posts: 700

You're running out of memory during the build. Add more swap.

Hu · Administrator Joined: 06 Mar 2007 Posts: 22782

The "We've already been run in this tree" warning appears even if the build succeeds. It is probably not a good sign to have that, given that it explicitly tells you to file a bug.

javeree · Guru Joined: 29 Jan 2006 Posts: 453

@Aquous

Yes, adding swap helped. What made it so clear to you that swap was the culprit ? I have had previously builds going wrong without clear indication of the problem because my workspace on disk was growing too small, but that was one of the things I had checked.

Was it a guess, was it because you had the same problem and are sharing experience, or is there something one can learn from the way the build dies ?

@Hu
You suggest a bug with the gentoo team. Shouldn't that be a bug upstream ? Or is it customary that build problems are first examined by gentoo team and then if they think it is needed sent upstream ?

Hu · Administrator Joined: 06 Mar 2007 Posts: 22782

Aquous · l33t Joined: 08 Jan 2011 Posts: 700

javeree · Guru Joined: 29 Jan 2006 Posts: 453

Thanks for the enlightment. You deserve your 'Guru' status.
It's good to know what kind of info is hidden behind the 'signal' info.

Gentree · Posted: Sat Nov 26, 2011 8:05 am Post subject:

Nice detective work Aquous.

Javeree you should probably file a gentoo bug since that original output about being out if it's tree is amazingly unhelpful and confusing.

Clearly the error trapping needs to be improved in this area. It seems to be catching any error at this stage and attibuting it to a specific cause which is not necessarily the correct one.

That thunderbird triggered this is probably mainly coincidence. I would imagine from the diagnostic that any build of a similar size would trigger the same false error message, hence it is a broader problem in portage that should probably get fixed.
_________________
Linux, because I'd rather own a free OS than steal one that's not worth paying for.
Gentoo because I'm a masochist
AthlonXP-M on A7N8X. Portage ~x86

raygun · n00b Joined: 03 Sep 2011 Posts: 24

twalter · Posted: Wed Nov 30, 2011 4:50 pm Post subject: Not just swap related

FWIW, I have 6Gb allocated to swap and 0% was in use when emerging libsoup-gnome so it's definitely not just OOM killer. There was a circular dependency with libsoup and libsoup-gnome that couldn't resolve itself; I had to emerge it explicitly which never ends well with libraries.

* Should also add I've never seen this message before until recently so I'm wondering if the latest version of portage is the culprit.

JohnLM · n00b Joined: 20 Apr 2009 Posts: 71 Location: LATVIA

I'm also having this "bug" message on quite a lot of ebuilds