Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 359665 - dev-libs/libgdata-0.8.0 fails to emerge: compile failure
Summary: dev-libs/libgdata-0.8.0 fails to emerge: compile failure
Status: RESOLVED DUPLICATE of bug 358625
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Development (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-20 21:09 UTC by Dave Bender
Modified: 2011-03-21 15:10 UTC (History)
0 users

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


Attachments
temp/environment file (environment,115.48 KB, text/plain)
2011-03-20 21:09 UTC, Dave Bender
Details
emerge --info file (libgdata-info,5.05 KB, text/plain)
2011-03-20 21:10 UTC, Dave Bender
Details
build log (build.log,151.03 KB, text/plain)
2011-03-20 21:11 UTC, Dave Bender
Details
config log (config.log,48.25 KB, text/plain)
2011-03-21 12:14 UTC, Dave Bender
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dave Bender 2011-03-20 21:09:03 UTC
Encounter tons of compile errors when attempting to emerge. Currently have 0.6.0 installed just fine, but portage wants to upgrade to 0.8.0

Reproducible: Always

Steps to Reproduce:
1. emerge -1 libgdata
2.
3.
Actual Results:  
Please see attached output.
Comment 1 Dave Bender 2011-03-20 21:09:46 UTC
Created attachment 266641 [details]
temp/environment file
Comment 2 Dave Bender 2011-03-20 21:10:35 UTC
Created attachment 266643 [details]
emerge --info file
Comment 3 Dave Bender 2011-03-20 21:11:19 UTC
Created attachment 266645 [details]
build log
Comment 4 Rafał Mużyło 2011-03-20 21:23:43 UTC
What does 'pkg-config glib-2.0 --cflags' print ?
If that works correctly, check your config.log for the package where it fails.
Comment 5 Dave Bender 2011-03-21 01:36:02 UTC
This is my pkg-config output:

-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include

Excerpt from build.log:

checking how to hardcode library paths into programs... immediate
checking for x86_64-pc-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config

I do not see any failures in the build log.
Any other pointers?

Thanks
Comment 6 Rafał Mużyło 2011-03-21 03:06:12 UTC
That was meant to be read: "check config.log and if *you* don't see anything obvious, attach it".
Comment 7 Pacho Ramos gentoo-dev 2011-03-21 10:19:20 UTC

*** This bug has been marked as a duplicate of bug 354951 ***
Comment 8 Dave Bender 2011-03-21 12:14:33 UTC
Created attachment 266707 [details]
config log
Comment 9 Dave Bender 2011-03-21 12:21:50 UTC
Please explain why you believe this bug is resolved. In bug 354951 the user's pkg-config call did not work at all, whereas mine did. Further traversing the duplicate chain shows an unrelated bug. Reopening.
Comment 10 Rafał Mużyło 2011-03-21 14:00:09 UTC
That's cause it most likely is a dupe - though it's probably libsoup, not gl, related.
Let's try a longer line:
pkg-config glib-2.0 libxml-2.0 gthread-2.0 gio-2.0 libsoup-2.4 --cflags
Comment 11 Dave Bender 2011-03-21 14:11:51 UTC
Result of:
pkg-config glib-2.0 libxml-2.0 gthread-2.0 gio-2.0 libsoup-2.4 --cflags

Package zlib was not found in the pkg-config search path.
Perhaps you should add the directory containing `zlib.pc'
to the PKG_CONFIG_PATH environment variable
Package 'zlib', required by 'GnuTLS', not found

A find over my root for zlib.pc turned up nothing, so I don't have the file at all.

I have libsoup.pc at


./usr/lib64/pkgconfig/libsoup-2.4.pc
./usr/lib64/pkgconfig/libsoup-gnome-2.4.pc


Do I need to rebuild my entire system to get these missing .pc files back?
Comment 12 Rafał Mużyło 2011-03-21 14:51:17 UTC
Nah, in this case, it's bug 358625.
While mixing, be really careful.

It's still INVALID though.
Comment 13 Dave Bender 2011-03-21 15:10:33 UTC
I checked my package.keywords and gnutls was ~amd64 but zlib was not. I just removed the gnutls entry and I am chugging along again.

Thank you Rafał for your insight and mapping this bug to the correct duplicate. I should have noticed this earlier but the title of the bug did not include gdata...

*** This bug has been marked as a duplicate of bug 358625 ***