While trying to emerge glib-2.8.2 I ran into the following problem Calculating dependencies ...done! >>> emerge (1 of 1) dev-libs/glib-2.8.2 to / >>> md5 files ;-) glib-1.2.10-r5.ebuild >>> md5 files ;-) glib-2.6.5.ebuild >>> md5 files ;-) glib-2.8.2.ebuild >>> md5 files ;-) files/digest-glib-1.2.10-r5 >>> md5 files ;-) files/digest-glib-2.6.5 >>> md5 files ;-) files/digest-glib-2.8.2 >>> md5 files ;-) files/glib-1.2.10-gcc34-fix.patch >>> md5 files ;-) files/glib-1.2.10-m4.patch >>> md5 files ;-) files/glib-2-macos.patch >>> md5 files ;-) files/glib-2.6.3-testglib-ssp.patch >>> md5 src_uri ;-) glib-2.8.2.tar.bz2 >>> Unpacking source... >>> Unpacking glib-2.8.2.tar.bz2 to /var/tmp/portage/glib-2.8.2/work * Applying glib-2-macos.patch ... * Failed Patch: glib-2-macos.patch ! * ( /usr/portage/dev-libs/glib/files/glib-2-macos.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/glib-2.8.2/temp/glib-2-macos.patch-11450.out I attach this file Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51.22-r3 (default-darwin/macos/10.4, gcc-4.0.0, libsystem-7.1-r0, 8.2.0 Power Macintosh) =============================================================== == System uname: 8.2.0 Power Macintosh powerpc macos-20041118 distcc 2.0.1-zeroconf powerpc-apple-darwin7.0 (protocol 1) (default port 3632) [disabled] dev-lang/python: [Not Present] sys-apps/sandbox: [Not Present] sys-devel/autoconf: [Not Present] sys-devel/automake: [Not Present] sys-devel/binutils: [Not Present] sys-devel/libtool: [Not Present] virtual/os-headers: 7.1 ACCEPT_KEYWORDS="ppc-macos" AUTOCLEAN="yes" CBUILD="powerpc-apple-darwin8" CFLAGS="-O2 -pipe" CHOST="powerpc-apple-darwin8" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /var/ qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig collision-protect distlocks sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/ gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="ppc aalib emboss gdbm gif imagemagick libwww nls ogg opengl png ppc-macos qt sdl slang tiff vorbis userland_Darwin kernel_Darwin elibc_Darwin" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
Created attachment 70784 [details] log file containing the root problem of the failed emerge
Created attachment 70790 [details, diff] Patch that makes ppc-macos patches version-dependent. The patch in the files dir is specific to an apparently unsupported glib version 2.4.8. This patch renames the current patch to specify that and changed the two 2.x ebuilds so that epatch can handle it and die appropriately if needed. This patch *does not* solve the bug because the way it is now, it seems the configure script in every version would need to be edited separately. :-\
Created attachment 70791 [details, diff] Patch for the 2.8.2 ebuild that uses sed instead of [e]patch Apparently the patch only statically replaced every -$flag in configure with $flag. Hey, we can do that dynamically too with sed. Disclaimer: I haven't tested the patched ebuild.
On another note, why doesn't the 2.8.2 ebuild have a SRC_URI?
I believe the gnome people don't need to be bothered with this. The SRC_URI comes from the gnome.org eclass.
(In reply to comment #5) > I believe the gnome people don't need to be bothered with this. You tell me. :) > The SRC_URI comes from the gnome.org eclass. In that case the Ebuild HOWTO [1] might need some TLC, as it lists SRC_URI as one of the "variables you must always set" in "every ebuild file". [1] http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml? part=2&chap=1#doc_chap2
uhm... did someone consider removing the patch? It [1] just compiles for me when I remove the patch from the ebuild... [1] dev-libs/glib-2.8.2 -debug (-doc) (-hardened) 2,502 kB
(In reply to comment #6) > > The SRC_URI comes from the gnome.org eclass. > > In that case the Ebuild HOWTO [1] might need some TLC, as it lists SRC_URI as > one of the "variables you must always set" in "every ebuild file". The power of the Human Brain(tm) is to 'reason'. It might be obfuscated, but if you think of how eclasses work the ebuild has a SRC_URI. It has no use to spank someone for things that are simply not to obvious, IMHO.
(In reply to comment #8) > It might be obfuscated, but if you think of how eclasses work the ebuild has a > SRC_URI. It has no use to spank someone for things that are simply not to > obvious, IMHO. I wasn't trying to spank anyone. I merely asked a straightforward question. Thanks for the anwser. I learn something everyday, like always to check what eclasses are inherited. :)
Remember that one books more success using a proper amount of politeness. It also helps to research a bit before you actually come up with a 'straight' question. I'd be surpriced if someone from the gnome herd would have nicely answered you, if any at all.
