Bug 265033

Summary:	dev-libs/glib-2.18.4-r1 fails to emerge on a 'current' stage3 due to a missing libglib-2 on x86_64
Product:	Gentoo Linux	Reporter:	Olliver Schinagl <oliver>
Component:	New packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED NEEDINFO
Severity:	minor
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Olliver Schinagl 2009-04-05 23:07:47 UTC

When emerging syslog-ng glib-2 gets pulled in. gobject builds a .glib-marshal that is linked against libglib-2.0.so. lib(64)/libglib-2.0.so however isn't contained int he x86_64 stage3 tarball, it only comes with lib32/libglib-2.0.so which gobject doesn't really care to look for. Since the handbook only mentions to emerge syslog-ng, this isn't accounted for.

I copied a libglib-2.0 from a diff x86_64 box to satisfy the emerge.

It's mindboggling how glib2 can depend on itself anyway. How would this work out on a ... LFS box where you build glib for the first time?

Reproducible: Always

Steps to Reproduce:

Comment 1 Peter Alfredsen (RETIRED) gentoo-dev

2009-04-07 21:50:11 UTC

We need a failing build.log to figure out what's going on.