[gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Dale]

Howdy,

Doing some updates and ran into this.  Anyone else having this problem? 
I can post more info if needed but thought this would get it off to a
start. 



/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/API/JSValueRef.o:
In function `JSValueToNumber':
JSValueRef.cpp:(.text+0x3fe2): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x411b): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x425c): undefined reference to `pthread_setspecific'
JSValueRef.cpp:(.text+0x4288): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x42c0): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x4305): undefined reference to `pthread_setspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/API/JSValueRef.o:
In function `JSValueToObject':
JSValueRef.cpp:(.text+0x43c1): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x44e1): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x4604): undefined reference to `pthread_setspecific'
JSValueRef.cpp:(.text+0x4644): undefined reference to `pthread_setspecific'
JSValueRef.cpp:(.text+0x4678): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x46b0): undefined reference to `pthread_key_create'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/API/JSValueRef.o:
In function `JSValueProtect':
JSValueRef.cpp:(.text+0x475d): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x47f0): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x4908): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x494e): undefined reference to `pthread_setspecific'
JSValueRef.cpp:(.text+0x4978): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x49b4): undefined reference to `pthread_setspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/API/JSValueRef.o:
In function `JSValueUnprotect':
JSValueRef.cpp:(.text+0x4a74): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x4b16): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x4c14): undefined reference to `pthread_setspecific'
JSValueRef.cpp:(.text+0x4c40): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x4c5f): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x4ca6): undefined reference to `pthread_setspecific'
JSValueRef.cpp:(.text+0x4cd0): undefined reference to `pthread_key_create'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/API/JSValueRef.o:
In function `JSValueCreateJSONString':
JSValueRef.cpp:(.text+0x4d86): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x4ebe): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x5000): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x504d): undefined reference to `pthread_setspecific'
JSValueRef.cpp:(.text+0x5080): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x50c4): undefined reference to `pthread_setspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/API/JSValueRef.o:
In function `JSValueToStringCopy':
JSValueRef.cpp:(.text+0x5183): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x52a0): undefined reference to `pthread_getspecific'
JSValueRef.cpp:(.text+0x5410): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x545c): undefined reference to `pthread_setspecific'
JSValueRef.cpp:(.text+0x5490): undefined reference to `pthread_key_create'
JSValueRef.cpp:(.text+0x54d5): undefined reference to `pthread_setspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/heap/HeapTimer.o:
In function `JSC::HeapTimer::timerEvent(QTimerEvent*)':
HeapTimer.cpp:(.text+0xf9): undefined reference to `pthread_getspecific'
HeapTimer.cpp:(.text+0x18c): undefined reference to `pthread_getspecific'
HeapTimer.cpp:(.text+0x215): undefined reference to `pthread_setspecific'
HeapTimer.cpp:(.text+0x23e): undefined reference to `pthread_key_create'
HeapTimer.cpp:(.text+0x285): undefined reference to `pthread_setspecific'
HeapTimer.cpp:(.text+0x2ae): undefined reference to `pthread_key_create'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/runtime/Completion.o:
In function `JSC::checkSyntax(JSC::ExecState*, JSC::SourceCode const&,
JSC::JSValue*)':
Completion.cpp:(.text+0x5c): undefined reference to `pthread_getspecific'
Completion.cpp:(.text+0x140): undefined reference to `pthread_key_create'
Completion.cpp:(.text+0x154): undefined reference to `pthread_getspecific'
Completion.cpp:(.text+0x18d): undefined reference to `pthread_setspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/runtime/Completion.o:
In function `JSC::evaluate(JSC::ExecState*, JSC::SourceCode const&,
JSC::JSValue, JSC::JSValue*)':
Completion.cpp:(.text+0x242): undefined reference to `pthread_getspecific'
Completion.cpp:(.text+0x4c8): undefined reference to `pthread_key_create'
Completion.cpp:(.text+0x4de): undefined reference to `pthread_getspecific'
Completion.cpp:(.text+0x526): undefined reference to `pthread_setspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/JavaScriptCore//.obj/runtime/Completion.o:
In function `JSC::checkSyntax(JSC::VM&, JSC::SourceCode const&,
JSC::ParserError&)':
Completion.cpp:(.text+0x629): undefined reference to `pthread_getspecific'
Completion.cpp:(.text+0x710): undefined reference to `pthread_key_create'
Completion.cpp:(.text+0x726): undefined reference to `pthread_getspecific'
Completion.cpp:(.text+0x766): undefined reference to `pthread_setspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/WTF//.obj/wtf/DataLog.o:
In function `WTF::dataFile()':
DataLog.cpp:(.text+0x73): undefined reference to `pthread_once'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/WTF//.obj/wtf/StackBounds.o:
In function `WTF::StackBounds::initialize()':
StackBounds.cpp:(.text+0x48): undefined reference to `pthread_getattr_np'
StackBounds.cpp:(.text+0x58): undefined reference to `pthread_attr_getstack'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/WTF//.obj/wtf/text/StringImpl.o:
In function `WTF::StringImpl::~StringImpl()':
StringImpl.cpp:(.text+0x6587): undefined reference to `pthread_getspecific'
StringImpl.cpp:(.text+0x6780): undefined reference to `pthread_key_create'
StringImpl.cpp:(.text+0x67bc): undefined reference to `pthread_setspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/WTF//.obj/wtf/ThreadIdentifierDataPthreads.o:
In function `WTF::ThreadIdentifierData::initializeOnce()':
ThreadIdentifierDataPthreads.cpp:(.text+0x73): undefined reference to
`pthread_key_create'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/WTF//.obj/wtf/ThreadIdentifierDataPthreads.o:
In function `WTF::ThreadIdentifierData::identifier()':
ThreadIdentifierDataPthreads.cpp:(.text+0xab): undefined reference to
`pthread_getspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/WTF//.obj/wtf/ThreadIdentifierDataPthreads.o:
In function `WTF::ThreadIdentifierData::destruct(void*)':
ThreadIdentifierDataPthreads.cpp:(.text+0x2e): undefined reference to
`pthread_setspecific'
/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source/WTF//.obj/wtf/ThreadIdentifierDataPthreads.o:
In function `WTF::ThreadIdentifierData::initialize(unsigned int)':
ThreadIdentifierDataPthreads.cpp:(.text+0xfe): undefined reference to
`pthread_setspecific'
collect2: error: ld returned 1 exit status
Makefile.api:94: recipe for target '../lib/libQt5WebKit.so.5.6.0' failed
make[2]: *** [../lib/libQt5WebKit.so.5.6.0] Error 1
make[2]: Leaving directory
'/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source'
Makefile.QtWebKit:44: recipe for target 'sub-api-pri-make_first-ordered'
failed
make[1]: *** [sub-api-pri-make_first-ordered] Error 2
make[1]: Leaving directory
'/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0/Source'
Makefile:307: recipe for target
'sub-Source-QtWebKit-pro-make_first-ordered' failed
make: *** [sub-Source-QtWebKit-pro-make_first-ordered] Error 2
 * ERROR: dev-qt/qtwebkit-5.6.0::gentoo failed (compile phase):
 *   emake failed
 *
 * If you need support, post the output of `emerge --info
'=dev-qt/qtwebkit-5.6.0::gentoo'`,
 * the complete build log and the output of `emerge -pqv
'=dev-qt/qtwebkit-5.6.0::gentoo'`.
 * The complete build log is located at
'/var/tmp/portage/dev-qt/qtwebkit-5.6.0/temp/build.log'.
 * The ebuild environment file is located at
'/var/tmp/portage/dev-qt/qtwebkit-5.6.0/temp/environment'.
 * Working directory:
'/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0'
 * S:
'/var/tmp/portage/dev-qt/qtwebkit-5.6.0/work/qtwebkit-opensource-src-5.6.0'

>>> Failed to emerge dev-qt/qtwebkit-5.6.0, Log file:

>>>  '/var/tmp/portage/dev-qt/qtwebkit-5.6.0/temp/build.log'
*** Resuming merge...

These are the packages that would be merged, in reverse order:

Calculating dependencies... done!
 * One or more packages are either masked or have missing dependencies:
 *
 *   ~dev-qt/qtcore-5.5.1 pulled in by:
 *     (dev-qt/linguist-tools-5.5.1-r1:5/5::gentoo, installed)
 *
 *   ~dev-qt/qtxml-5.5.1 pulled in by:
 *     (dev-qt/designer-5.5.1-r1:5/5::gentoo, installed)
 *
 *   ~dev-qt/qtwidgets-5.5.1 pulled in by:
 *     (dev-qt/qtwebkit-5.5.1-r1:5/5::gentoo, installed)
 *
 * The resume list contains packages that are either masked or have
 * unsatisfied dependencies. Please restart/continue the operation
 * manually, or use --skipfirst to skip the first package in the list and
 * any other packages that may be masked or have missing dependencies.
 *
 * The following package has failed to build, install, or execute postinst:
 *
 *  (dev-qt/qtwebkit-5.6.0:5/5.6::gentoo, ebuild scheduled for merge),
Log file:
 *   '/var/tmp/portage/dev-qt/qtwebkit-5.6.0/temp/build.log'
 *
root@fireball /home/dale/Desktop #


I did a bit of googling but didn't find anything like this.  I figure it
may be a setting or something.  Here's the USE flags it is trying to
build with.

[ebuild   R   ~] dev-qt/qtwebkit-4.8.7:4::gentoo  USE="exceptions
gstreamer jit (-aqua) -debug -icu -pch" ABI_X86="(64) -32 (-x32)" 0 KiB

I tried -j 1 just for giggles, same thing.  I think it was only building
that package by itself anyway but just to be sure.  ;-) 

Anyone else running into this?  Anything obvious sticking out?

Thanks.

Dale

:-)  :-) 

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Dale]

Dale wrote:
> Howdy,
>
> Doing some updates and ran into this.  Anyone else having this problem? 
> I can post more info if needed but thought this would get it off to a
> start. 
>
>
>
> <<< SNIP >>>
>
> Anyone else running into this?  Anything obvious sticking out?
>
> Thanks.
>
> Dale
>
> :-)  :-) 
>
>


I synced again and was hoping I either caught the tree in the middle of
some change over with the last sync or whatever it is would have a fix
by now.  Well, still the same error as before. 

Anyone have any ideas on the cause of this?  Any tricks that I could
try?  Could this be a bug that I need to report?  I've tried skipfirst
and such but it seems to be a hard stop on this package. 

Thanks. 

Dale

:-)  :-) 

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Peter Humphrey]

On Tuesday 26 Apr 2016 18:50:41 Dale wrote:

--->8

> I synced again and was hoping I either caught the tree in the middle of
> some change over with the last sync or whatever it is would have a fix
> by now.  Well, still the same error as before.
> 
> Anyone have any ideas on the cause of this?  Any tricks that I could
> try?  Could this be a bug that I need to report?  I've tried skipfirst
> and such but it seems to be a hard stop on this package.

After googling for one of those linker errors, it looks to me like a bug in 
the order in which libraries are being called to be linked in. I'm no coder 
any more though (that was 40 years ago).

HTH. HaND.  :)

-- 
Rgds
Peter

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Dale]

Peter Humphrey wrote:
> On Tuesday 26 Apr 2016 18:50:41 Dale wrote:
>
> --->8
>
>> I synced again and was hoping I either caught the tree in the middle of
>> some change over with the last sync or whatever it is would have a fix
>> by now.  Well, still the same error as before.
>>
>> Anyone have any ideas on the cause of this?  Any tricks that I could
>> try?  Could this be a bug that I need to report?  I've tried skipfirst
>> and such but it seems to be a hard stop on this package.
> After googling for one of those linker errors, it looks to me like a bug in 
> the order in which libraries are being called to be linked in. I'm no coder 
> any more though (that was 40 years ago).
>
> HTH. HaND.  :)
>


I been considering a roach report but I hate to since I seem to be the
only one running into it.  I've synced a couple times since it started
so whatever it is, it seems to be sticking around. 

I've done some googling but the only thing I find now, this thread.  I
did try to google some other ways but still found nothing helpful, as in
a solution. 

I'll give it another day or two and if after another sync the problem
remains, I'll file a roach report.

Thanks.

Dale

:-)  :-) 

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Michael Mol]

[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]

On Wednesday, April 27, 2016 08:11:05 AM Dale wrote:
> Peter Humphrey wrote:
> > On Tuesday 26 Apr 2016 18:50:41 Dale wrote:
> > 
> > --->8
> > 
> >> I synced again and was hoping I either caught the tree in the middle of
> >> some change over with the last sync or whatever it is would have a fix
> >> by now.  Well, still the same error as before.
> >> 
> >> Anyone have any ideas on the cause of this?  Any tricks that I could
> >> try?  Could this be a bug that I need to report?  I've tried skipfirst
> >> and such but it seems to be a hard stop on this package.
> > 
> > After googling for one of those linker errors, it looks to me like a bug
> > in
> > the order in which libraries are being called to be linked in. I'm no
> > coder
> > any more though (that was 40 years ago).
> > 
> > HTH. HaND.  :)
> 
> I been considering a roach report but I hate to since I seem to be the
> only one running into it.  I've synced a couple times since it started
> so whatever it is, it seems to be sticking around.
> 
> I've done some googling but the only thing I find now, this thread.  I
> did try to google some other ways but still found nothing helpful, as in
> a solution.
> 
> I'll give it another day or two and if after another sync the problem
> remains, I'll file a roach report.

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.

-- 
:wq

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Andrés Becerra Sandoval]

[-- Attachment #1: Type: text/plain, Size: 1825 bytes --]

2016-04-27 9:17 GMT-05:00 Michael Mol <mikemol@gmail.com>:

> On Wednesday, April 27, 2016 08:11:05 AM Dale wrote:
> > Peter Humphrey wrote:
> > > On Tuesday 26 Apr 2016 18:50:41 Dale wrote:
> > >
> > > --->8
> > >
> > >> I synced again and was hoping I either caught the tree in the middle
> of
> > >> some change over with the last sync or whatever it is would have a fix
> > >> by now.  Well, still the same error as before.
> > >>
> > >> Anyone have any ideas on the cause of this?  Any tricks that I could
> > >> try?  Could this be a bug that I need to report?  I've tried skipfirst
> > >> and such but it seems to be a hard stop on this package.
> > >
> > > After googling for one of those linker errors, it looks to me like a
> bug
> > > in
> > > the order in which libraries are being called to be linked in. I'm no
> > > coder
> > > any more though (that was 40 years ago).
> > >
> > > HTH. HaND.  :)
> >
> > I been considering a roach report but I hate to since I seem to be the
> > only one running into it.  I've synced a couple times since it started
> > so whatever it is, it seems to be sticking around.
> >
> > I've done some googling but the only thing I find now, this thread.  I
> > did try to google some other ways but still found nothing helpful, as in
> > a solution.
> >
> > I'll give it another day or two and if after another sync the problem
> > remains, I'll file a roach report.
>
> 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.
>
> --
> :wq



​Dale,

Do you have debugging activated (ggdb in make.conf) ?

If yes, turn it off for qtwebkit!
​

-- 
  Andrés Becerra Sandoval

[-- Attachment #2: Type: text/html, Size: 3039 bytes --]

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Dale]

[-- Attachment #1: Type: text/plain, Size: 364 bytes --]

Andrés Becerra Sandoval wrote:
>
>
>
>
> ​Dale, 
>
> Do you have debugging activated (ggdb in make.conf) ?
>
> If yes, turn it off for qtwebkit!
> ​
>
> -- 
>   Andrés Becerra Sandoval
>


I didn't recognise that flag but looked to be sure, it's not there.  In
a way, I was hoping it was and I could remove/disable it and carry on. 

Thanks.

Dale

:-)  :-)

[-- Attachment #2: Type: text/html, Size: 1770 bytes --]

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Dale]

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

:-)  :-)

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Michael Mol]

[-- Attachment #1: Type: text/plain, Size: 1302 bytes --]

On Wednesday, April 27, 2016 12:33:43 PM 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.  :/

If the problem started Monday, ad you didn't flip any USE flags or other 
settings, then its a regression or other new issue; at the very least, it 
helps them to have that documented.

At the same time, 5.6.0 lookslike it's hardmasked right now; I only have 
5.5.1-r1 instealled, and that's after pushing plasma-meta and friends up to 
5.6.3. This might be one of those cases where you need to wait until the 
KDE4/5 transition stabilizes a bit more...

-- 
:wq

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Bill Kenworthy]

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

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Dale]

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

:-)  :-)

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Peter Humphrey]

On Wednesday 27 Apr 2016 17:52:07 Dale wrote:

> 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.

You could back your system partitions up first, to have a system to revert to
if necessary. I've had to do that quite a lot while getting this new box
installed.

It helps that I have several partitions, thus:

/dev/nvme0n1p5  /                       ext4    relatime        1 1
/dev/nvme0n1p2  /boot                   vfat    noauto          1 2
/dev/nvme0n1p6  /var                    ext4    relatime        1 2
/dev/nvme0n1p7  /home                   ext4    relatime        1 2
/dev/nvme0n1p8  /home/prh/boinc         ext4    relatime        1 3
/dev/nvme0n1p9  /home/prh/common        ext4    relatime        1 3
/dev/nvme0n1p10 /usr/local              ext4    relatime        1 2
/dev/nvme0n1p11 /usr/portage            ext4    relatime        1 2
/dev/nvme0n1p12 /usr/portage/packages   ext4    relatime        1 3
/dev/nvme0n1p13 /usr/portage/distfiles  ext4    relatime        1 3
/dev/nvme0n1p17 /home/prh/.VirtualBox   ext4    relatime        1 3
/dev/nvme0n1p3  none                    swap    sw              0 0
tmpfs           /var/tmp/portage        tmpfs   noatime,uid=portage,gid=portage,mode=0775  0 0
tmpfs           /tmp                    tmpfs   noatime,nosuid,nodev,noexec,mode=1777   0 0
proc            /proc                   proc    defaults        0 0
shm             /dev/shm                tmpfs   nodev,nosuid    0 0

Not sure about those last two - are they still needed nowadays?

-- 
Rgds
Peter

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[waltdnes]

On Thu, Apr 28, 2016 at 10:44:34AM +0100, Peter Humphrey wrote
> proc            /proc                   proc    defaults        0 0
> shm             /dev/shm                tmpfs   nodev,nosuid    0 0
> 
> Not sure about those last two - are they still needed nowadays?

  I'm running OK without them...

/dev/sda5            /           ext3     noatime,nodiratime,async   0 1
/dev/sda7            /home       ext3     noatime,nodiratime,async   0 1
/home/bindmounts/opt /opt        auto     bind                       0 0
/home/bindmounts/var /var        auto     bind                       0 0
/home/bindmounts/usr /usr        auto     bind                       0 0
/home/bindmounts/tmp /tmp        auto     bind                       0 0
/dev/sda6            none        swap     sw                         0 0
/dev/cdrom           /mnt/cdrom  iso9660  noauto,users,ro            0 0
/dev/sr0             /mnt/dvd    auto     noauto,users,ro            0 0
/dev/sdb1            /mnt/drive1 auto     noauto,users,noatime,async 0 0
/dev/sdc1            /mnt/drive2 auto     noauto,users,noatime,async 0 0
/dev/sdd1            /mnt/drive4 auto     noauto,users,noatime,async 0 0
/dev/sde1            /mnt/drive5 auto     noauto,users,noatime,async 0 0
/dev/sdf1            /mnt/drive6 auto     noauto,users,noatime,async 0 0
/dev/sdg1            /mnt/drive7 auto     noauto,users,noatime,async 0 0
/dev/sdg             /mnt/drive8 auto     noauto,users,noatime,async 0 0

  In the kernel, it's taken care of automatically...

File systems  --->
    Pseudo filesystems  --->
        -*- /proc file system support
        [*]   /proc/kcore support
        -*- Tmpfs virtual memory file system support (former shm fs

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Peter Humphrey]

On Thursday 28 Apr 2016 16:53:43 waltdnes@waltdnes.org wrote:
> On Thu, Apr 28, 2016 at 10:44:34AM +0100, Peter Humphrey wrote
> 
> > proc            /proc                   proc    defaults        0 0
> > shm             /dev/shm                tmpfs   nodev,nosuid    0 0
> > 
> > Not sure about those last two - are they still needed nowadays?
> 
>   I'm running OK without them...

OK - thanks. I'll try deleting them.

-- 
Rgds
Peter

[gentoo-user] Re: Failed to emerge dev-qt/qtwebkit-5.6.0

[walt]

On Tue, 26 Apr 2016 18:50:41 -0500
Dale <rdalek1967@gmail.com> wrote:

> Dale wrote:
> > Howdy,
> >
> > Doing some updates and ran into this.  Anyone else having this
> > problem? I can post more info if needed but thought this would get
> > it off to a start. 
> >
> >
> >
> > <<< SNIP >>>
> >
> > Anyone else running into this?  Anything obvious sticking out?
> >
> > Thanks.
> >
> > Dale
> >
> > :-)  :-) 
> >
> >  
> 
> 
> I synced again and was hoping I either caught the tree in the middle
> of some change over with the last sync or whatever it is would have a
> fix by now.  Well, still the same error as before. 

I'm still on my gcc-5 vs gcc-4 bandwagon.  And what's that thingy that
stands for 'thread too long, didn't read'?

Re: [gentoo-user] Re: Failed to emerge dev-qt/qtwebkit-5.6.0

[Dale]

walt wrote:
> On Tue, 26 Apr 2016 18:50:41 -0500
> Dale <rdalek1967@gmail.com> wrote:
>
>> Dale wrote:
>>> Howdy,
>>>
>>> Doing some updates and ran into this.  Anyone else having this
>>> problem? I can post more info if needed but thought this would get
>>> it off to a start. 
>>>
>>>
>>>
>>> <<< SNIP >>>
>>>
>>> Anyone else running into this?  Anything obvious sticking out?
>>>
>>> Thanks.
>>>
>>> Dale
>>>
>>> :-)  :-) 
>>>
>>>  
>>
>> I synced again and was hoping I either caught the tree in the middle
>> of some change over with the last sync or whatever it is would have a
>> fix by now.  Well, still the same error as before. 
> I'm still on my gcc-5 vs gcc-4 bandwagon.  And what's that thingy that
> stands for 'thread too long, didn't read'?
>
>
>

TL;DR  I think that's it. 

Dale

:-)  :-) 

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Dale]

Dale wrote:
> Howdy,
>
> Doing some updates and ran into this.  Anyone else having this problem? 
> I can post more info if needed but thought this would get it off to a
> start. 
>
> <<<< SNIP >>>>
>
> Thanks.
>
> Dale
>
> :-)  :-) 
>
>


Seems I'm not alone and it is a bug.

https://bugs.gentoo.org/show_bug.cgi?id=581282 

Dale

:-)  :-) 

Re: [gentoo-user] Failed to emerge dev-qt/qtwebkit-5.6.0

[Dale]

[-- Attachment #1: Type: text/plain, Size: 396 bytes --]

If anyone runs into this, here is a patch that works.  Should be
attached.  It worked here at least.  Careful if you do copy and paste
tho.  It seems copy and paste gave me some trouble.  I had to open it
with nano -w to get it to work right.  It seems to lose a indention in
there.  I think it was line 11.  Don't worry, if it ain't right, emerge
will puke it out at you.  lol 

Dale

:-)  :-) 

[-- Attachment #2: fix-libpthread.patch --]
[-- Type: text/x-patch, Size: 598 bytes --]

 Tools/qmake/mkspecs/features/default_post.prf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Tools/qmake/mkspecs/features/default_post.prf 
b/Tools/qmake/mkspecs/features/default_post.prf
index 67276b7..39bb3f7 100644
--- a/Tools/qmake/mkspecs/features/default_post.prf
+++ b/Tools/qmake/mkspecs/features/default_post.prf
@@ -201,6 +201,7 @@ needToLink() {
         
	 linkAgainstLibrary($$library,$$eval(WEBKIT.$${library_identifier}.root_source_dir))
         LIBS += $$eval(WEBKIT.$${library_identifier}.dependent_libs)
     }
+    posix:!darwin: LIBS += -lpthread
 }
 
 creating_module {