Summary: | pkgconfig-0.26 circular depends on glib:2 making bootstrap extremely hard | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | Benda Xu <heroxbd> |
Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
Status: | RESOLVED DUPLICATE | ||
Severity: | blocker | CC: | freedesktop-bugs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Benda Xu
2011-11-26 21:52:45 UTC
pkg-config comes from gx86, so we can't really restore 0.25, unfortunately. Freedesktop people, what do you think? glib can be built without pkgconfig, look at this in src_configure inside glib ebuild: # Avoid circular depend with dev-util/pkgconfig if ! has_version dev-util/pkgconfig; then if has_version sys-apps/dbus; then export DBUS1_CFLAGS="-I/usr/include/dbus-1.0 -I/usr/$(get_libdir)/dbus-1.0/include" export DBUS1_LIBS="-ldbus-1" fi export LIBFFI_CFLAGS="-I$(echo /usr/$(get_libdir)/libffi-*/include)" export LIBFFI_LIBS="-lffi" fi I synced glib now, so that fix should be available, but I'm not sure if that fixes anything, since glib is a hefty dependency for a bootstrap indeed. We'll have to find out. (In reply to comment #3) > I synced glib now, so that fix should be available, but I'm not sure if that > fixes anything, since glib is a hefty dependency for a bootstrap indeed. We'll > have to find out. FYI, the reason that pkgconfig-0.25 and earlier did not depend on glib is because it contained a bundled copy of glib-1. For 0.26, pkgconfig developers rightly decided to remove the bundled library and rely on system's glib-2 instead. (In reply to comment #3) > I synced glib now, so that fix should be available, but I'm not sure if that > fixes anything, since glib is a hefty dependency for a bootstrap indeed. We'll > have to find out. Fixes went also to libgamin and gam-server related to this. Also, I'm not sure if the code block is missing ${EPREFIX} in the -I paths... bootstrapping succeed with todays snapshot, so this is luckily not a problem *** This bug has been marked as a duplicate of bug 385561 *** |