Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 286950 - qt-core-4.5.2 and 4.5.1 have difficulties with glib
Summary: qt-core-4.5.2 and 4.5.1 have difficulties with glib
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: AMD64 Linux
: High normal
Assignee: Qt Bug Alias
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-29 15:54 UTC by Karl Ernst Brunk
Modified: 2009-10-11 15:17 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Karl Ernst Brunk 2009-09-29 15:54:15 UTC
Todays update made me qt-core. It stoped while checking the installed glib.

qt-core-4.5.2/1
>>>
Glib auto-detection... ()
compiling glib.cpp
glib.cpp: In function »int main(int, char**)«:
glib.cpp:14: Warnung: »pollfd« is used uninitialized in this function
linking glib
/usr/lib64/libgthread-2.0.so: undefined reference to `clock_gettime'
collect2: ld gab 1 als Ende-Status zurück
make: *** [glib] Fehler 1
Glib disabled.
Glib support cannot be enabled due to functionality tests!
<<<<


Reproducible: Always

Steps to Reproduce:
1.emerge qt-core
2.
3.

Actual Results:  
stops compiling

Expected Results:  
complet install

I did a comment to #285586 an also a report for glib #286949
Karl
Comment 1 Ben de Groot (RETIRED) gentoo-dev 2009-10-01 06:46:39 UTC
Please provide emerge --info and glib version
Comment 2 Karl Ernst Brunk 2009-10-11 15:17:38 UTC
Sorry for the time passed by but i had to do some further investigations before pointing at some nonexisting problems.
So at the end i had around 15 packages all stopping compiling at the same point when checking clock_gettime. The intermediate workarround LDFLAGS="-lrt worked till openoffice showed up. No chance.
So i had to look for another solution. After all i had to rebuild gcc and all openmp useing or depending packages. That solved it.
So the conclusion for my system is not to use CFLAG -fopenmp and USE-Flag openmp.
I know that there are some warnings about those Flags but they never accompanied with any info : why not. And in the beginning it did seem to work.
So sorry for the hazzle.
Karl