public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0
Date: Wed, 27 Apr 2016 17:52:07 -0500	[thread overview]
Message-ID: <57214297.2070303@gmail.com> (raw)
In-Reply-To: <57213E8D.3080508@iinet.net.au>

Bill Kenworthy wrote:
> On 28/04/16 01:33, Dale wrote:
>> Michael Mol wrote:
>>> I have my system automatically update nightly, and check the build results in 
>>> the morning. If there's a persistent build error for a couple days, I file a 
>>> bug report. That's my threshold, anyway.
>>>
>>
>> This started on Sunday.  So it has met that part anyway.  Since I run a
>> mix of stable and unstable, it has been known to cause issues that are
>> weird.  I just don't want to file a bug report and take up a devs time
>> if it is some weird one off thing that affects no one else.  It's not
>> like they don't have enough stuff to deal with already.  Then again,
>> they do want info on failures so that it doesn't affect others.  Where's
>> my coin to flip?  lol 
>>
>> I plan to sync again and if it persists, Raid comes out.  :/
>>
>> Thanks.
>>
>> Dale
>>
>> :-)  :-)
>>
> I have a couple of background "things" happening at the moment:
>
> prelink and glibc: odd failures that make no sense - unprelink the
> system and everything works fine (at some point you get a failure to
> fork.)  I hit it when trying to build multiple lxc instances ... it
> builds two and then the server becomes "toast" :(  There is a bug on bgo ...
>
> btrfs and kernels 4.4.6 and 4.4.7: fails to convert/balance a raid 10
> (system hard lock, no errors) and maybe some file system related build
> errors (which might also be glibc related, though it might not ...)
> 4.4.8 works fine (includes a number of btrfs fixes)
>
> Either of those fit?
>
> BillK
>
>
>


Oddly, I had some google hits to that effect.  I can't recall exactly
what I was searching for but on one of them, I did see glibc mentioned
as the issue.  I just figured it would fail on other packages as well if
it was the problem so thought it unrelated.  Well, maybe it is after
all.  I dunno.  Good question. 

I seem to recall glibc being one of those packages that you can't
downgrade.  Sort of chicken to upgrade, just in case the problem gets
even worse.  Here's a little more info on my system.


root@fireball / # uname -r
3.18.7-gentoo
root@fireball / # equery list -p glibc
 * Searching for glibc ...
[-P-] [  ] sys-libs/glibc-2.17:2.2
[-P-] [ ~] sys-libs/glibc-2.18-r1:2.2
[-P-] [  ] sys-libs/glibc-2.19-r1:2.2
[-P-] [  ] sys-libs/glibc-2.20-r2:2.2
[-P-] [  ] sys-libs/glibc-2.21-r2:2.2
[IP-] [  ] sys-libs/glibc-2.22-r4:2.2
[-P-] [ ~] sys-libs/glibc-2.23-r1:2.2
[-P-] [ ~] sys-libs/glibc-2.23-r2:2.2
[-P-] [ -] sys-libs/glibc-9999:2.2
root@fireball / #


Yea, I'm using a old kernel.  I haven't rebooted in a while now.  I just
wonder what that glibc 2.23-r2 would be like??  Anyone here took a drive
around the block with that version? 

I just synced again.  Going to see if anything changes or not but I
doubt it will.  I didn't see any changes to the qtwebkit ebuild.  

Dale

:-)  :-)



  reply	other threads:[~2016-04-27 22:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-25 18:15 [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0 Dale
2016-04-26 23:50 ` Dale
2016-04-27  9:52   ` Peter Humphrey
2016-04-27 13:11     ` Dale
2016-04-27 14:17       ` Michael Mol
2016-04-27 14:31         ` Andrés Becerra Sandoval
2016-04-27 17:28           ` Dale
2016-04-27 17:33         ` Dale
2016-04-27 17:47           ` Michael Mol
2016-04-27 22:34           ` Bill Kenworthy
2016-04-27 22:52             ` Dale [this message]
2016-04-28  9:44               ` Peter Humphrey
2016-04-28 20:53                 ` waltdnes
2016-04-29  8:34                   ` Peter Humphrey
2016-04-29  2:48   ` [gentoo-user] " walt
2016-04-29  3:11     ` Dale
2016-04-30  2:06 ` [gentoo-user] " Dale
2016-05-01  6:25 ` Dale

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=57214297.2070303@gmail.com \
    --to=rdalek1967@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