When i tried to merge hwsetup for building a livecd in a chroot it failed when applying the dyn_blacklist patch. Reproducible: Always Steps to Reproduce: emerge hwsetup Actual Results: merging stops
Created attachment 150398 [details] patch results * Applying 1.2-3-dyn_blacklist.patch ... * Failed Patch: 1.2-3-dyn_blacklist.patch ! * ( /usr/portage/sys-apps/hwsetup/files/1.2-3-dyn_blacklist.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/sys-apps/hwsetup-1.2/temp/1.2-3-dyn_blacklist.patch-5025.out * * ERROR: sys-apps/hwsetup-1.2 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2401: Called epatch 'src_unpack' 'src_unpack' '/usr/portage/sys-apps/hwsetup/files/1.2-3-dyn_blacklist.patch' * environment, line 1106: Called epatch '/usr/portage/sys-apps/hwsetup/files/1.2-3-fastprobe.patch' * environment, line 1234: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: 1.2-3-dyn_blacklist.patch! * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-apps/hwsetup-1.2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/hwsetup-1.2/temp/environment'. * localhost x86
Comment on attachment 150398 [details] patch results This did happend me in catalyst building minimal cd x86 stage1.
i did test hwsetup-1.2.-r1 since i did wanted an new install cd quickly. this version is still ~x86 but looks like working. it is atleast installing testing results will be added later today. >>> Emerging (74 of 76) sys-apps/hwsetup-1.2-r1 to / --10:13:53-- http://distfiles.gentoo.org/distfiles/hwsetup_1.2-7.tar.gz => `/usr/portage/distfiles/hwsetup_1.2-7.tar.gz' Resolving distfiles.gentoo.org... 64.50.238.52, 156.56.247.195, 216.165.129.135, ... Connecting to distfiles.gentoo.org|64.50.238.52|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 10,706 (10K) [application/x-gzip] 100%[======================================================================================================================================>] 10,706 22.22K/s 10:13:54 (22.15 KB/s) - `/usr/portage/distfiles/hwsetup_1.2-7.tar.gz' saved [10706/10706] * Applying 1.2-7-dyn_blacklist.patch ... [ ok ] * Applying 1.2-3-fastprobe.patch ... [ ok ] * Applying 1.2-7-gentoo.patch ... [ ok ] i486-pc-linux-gnu-gcc -I/usr/include/kudzu -DBLACKLIST -Wall -fPIC -O2 -mtune=i686 -pipe -s -o hwsetup hwsetup.c -lkudzu -lpci hwsetup.c:55: warning: missing braces around initializer hwsetup.c:55: warning: (near initialization for 'blacklist[0]') hwsetup.c: In function 'gen_blacklist': hwsetup.c:80: warning: passing argument 1 of 'strcpy' from incompatible pointer type hwsetup.c: In function 'load_mod': hwsetup.c:580: warning: passing argument 1 of 'modcmp' from incompatible pointer type [ -d /var/tmp/portage/sys-apps/hwsetup-1.2-r1/image/usr/sbin ] || mkdir -p /var/tmp/portage/sys-apps/hwsetup-1.2-r1/image/usr/sbin install -m 755 hwsetup /var/tmp/portage/sys-apps/hwsetup-1.2-r1/image/usr/sbin/hwsetup * This package is intended for usage on the Gentoo release media. If * you are not building a CD, remove this package. It will not work * properly on a running system, as Gentoo does not use any of the * Knoppix-style detection except for CD builds. >>> Recording sys-apps/hwsetup in "world" favorites file...
* Messages for package sys-apps/hwsetup-1.2-r1: * * ERROR: sys-apps/hwsetup-1.2-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 2328: Called die * The specific snippet of code: * emake LDFLAGS="${LDFLAGS}" OPT="${CFLAGS}" CC="$(tc-getCC)" || die "emake failed" * The die message: * emake failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/var/tmp/portage/sys-apps/hwsetup-1.2-r1/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/sys-apps/hwsetup-1.2-r1/temp/environment'.
OK, I just fixed this. I'm not sure how the patch ended up getting copied incorrectly, but it did. My apologies.
