Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
dev-php/roadsend-php-2.9.6 fails on bigloo-3.1a-configsupport.patch with following error: >>> Unpacking roadsend-php-2.9.6.tar.bz2 to /var/tmp/portage/dev-php/roadsend-php-2.9.6/work * Applying bigloo-3.1a-configsupport.patch ... * Failed Patch: bigloo-3.1a-configsupport.patch ! * ( /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch ) * * Include in your bugreport the contents of: * * /var/tmp/portage/dev-php/roadsend-php-2.9.6/temp/bigloo-3.1a-configsupport.patch-13524.out * * ERROR: dev-php/roadsend-php-2.9.6 failed. * Call stack: * ebuild.sh, line 49: Called src_unpack * environment, line 2068: Called epatch 'src_unpack' * environment, line 1129: Called die * The specific snippet of code: * die "Failed Patch: ${patchname}!"; * The die message: * Failed Patch: bigloo-3.1a-configsupport.patch! Reproducible: Always /var/tmp/portage/dev-php/roadsend-php-2.9.6/temp/bigloo-3.1a-configsupport.patch-13524.out: ***** bigloo-3.1a-configsupport.patch ***** =========================================== PATCH COMMAND: patch -p0 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch =========================================== can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: /trunk/pcc/configure |=================================================================== |--- /trunk/pcc/configure (revision 495) |+++ /trunk/pcc/configure (revision 504) -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 23 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: /trunk/pcc/configure.in |=================================================================== |--- /trunk/pcc/configure.in (revision 495) |+++ /trunk/pcc/configure.in (revision 504) -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored =========================================== PATCH COMMAND: patch -p1 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch =========================================== can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: /trunk/pcc/configure |=================================================================== |--- /trunk/pcc/configure (revision 495) |+++ /trunk/pcc/configure (revision 504) -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 23 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: /trunk/pcc/configure.in |=================================================================== |--- /trunk/pcc/configure.in (revision 495) |+++ /trunk/pcc/configure.in (revision 504) -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored =========================================== PATCH COMMAND: patch -p2 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch =========================================== can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: /trunk/pcc/configure |=================================================================== |--- /trunk/pcc/configure (revision 495) |+++ /trunk/pcc/configure (revision 504) -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored can't find file to patch at input line 23 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: /trunk/pcc/configure.in |=================================================================== |--- /trunk/pcc/configure.in (revision 495) |+++ /trunk/pcc/configure.in (revision 504) -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored =========================================== PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch =========================================== patching file configure Hunk #1 FAILED at 3122. Hunk #2 FAILED at 3192. 2 out of 2 hunks FAILED -- saving rejects to file configure.rej patching file configure.in Hunk #1 FAILED at 27. Hunk #2 FAILED at 50. 2 out of 2 hunks FAILED -- saving rejects to file configure.in.rej =========================================== PATCH COMMAND: patch -p4 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch =========================================== missing header for unified diff at line 5 of patch can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: /trunk/pcc/configure |=================================================================== |--- /trunk/pcc/configure (revision 495) |+++ /trunk/pcc/configure (revision 504) -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored missing header for unified diff at line 23 of patch can't find file to patch at input line 23 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -------------------------- |Index: /trunk/pcc/configure.in |=================================================================== |--- /trunk/pcc/configure.in (revision 495) |+++ /trunk/pcc/configure.in (revision 504) -------------------------- No file to patch. Skipping patch. 2 out of 2 hunks ignored
I can't reproduce. Please add emerge --info and any other infos that may be relevant.
Created an attachment (id=151291) [edit] emerge --info
bigloo -v ------------------------------------------------------------------------------ Bigloo (3.0c) ,--^, `a practical Scheme compiler' _ ___/ /|/ Tue Dec 11 11:07:30 CET 2007 ,;'( )__, ) ' Inria -- Sophia Antipolis ;; // L__. email: bigloo@sophia.inria.fr ' \ / ' url: http://www.inria.fr/mimosa/fp/Bigloo ^ ^ ------------------------------------------------------------------------------ Welcome to the interpreter 1:=> ------------------------------------------------------------------------------ eclass-debug.log inherit: eutils -> /usr/portage/eclass/eutils.eclass *** Multiple Inheritence (Level: 2) inherit: multilib -> /usr/portage/eclass/multilib.eclass *** Multiple Inheritence (Level: 3) inherit: toolchain-funcs -> /usr/portage/eclass/toolchain-funcs.eclass inherit: portability -> /usr/portage/eclass/portability.eclass ----------------------------------------------------------------------------- structure of /var/tmp/portage/dev-php/roadsend-php-2.9.6/work/roadsend-php-2.9.6 Makefile.config.in README bigloo-rules.mk config.guess configure.in install-runtime.sh packages sa-tests tools Makefile.in acinclude.m4 bugs config.sub doc install.sh php-macros.scm tests webconnect Makefile.mingw benchmarks compiler configure dotest.scm libs runtime tidbits zend-tests PATCH LOOKING FOR /trunk/pcc/configure? I am not sure if that is the reason but it appears so?
No, somehow the patch is failing for you: PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch =========================================== patching file configure Hunk #1 FAILED at 3122. Hunk #2 FAILED at 3192. 2 out of 2 hunks FAILED -- saving rejects to file configure.rej patching file configure.in Hunk #1 FAILED at 27. Hunk #2 FAILED at 50. 2 out of 2 hunks FAILED -- saving rejects to file configure.in.rej Can you attach one of those files?
I do not find the rejects configure.rej configure.in.rej Sorry I have limited experience with this type of issue. I am going to compile this on another machine and will report my result shortly. Thanks. (In reply to comment #4) > No, somehow the patch is failing for you: > > PATCH COMMAND: patch -p3 -g0 -E --no-backup-if-mismatch < > /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch > > =========================================== > patching file configure > Hunk #1 FAILED at 3122. > Hunk #2 FAILED at 3192. > 2 out of 2 hunks FAILED -- saving rejects to file configure.rej > patching file configure.in > Hunk #1 FAILED at 27. > Hunk #2 FAILED at 50. > 2 out of 2 hunks FAILED -- saving rejects to file configure.in.rej > > Can you attach one of those files? >
Ok same result on another machine. Again I am sorry for my limited knowledge but it appears that the patch is not right: cat /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch Index: /trunk/pcc/configure =================================================================== --- /trunk/pcc/configure (revision 495) +++ /trunk/pcc/configure (revision 504) @@ -3122,5 +3122,5 @@ # can't figure out how to get this into AC_CHECK_PROG_VER below? # have to change it there too -want_bigloo="3.0c, 3.0d" +want_bigloo="3.0c, 3.0d, 3.1a" want_curl=7.15.1 @@ -3192,5 +3192,5 @@ case $ac_prog_version in '') ac_prog_version_m="v. ?.??, bad"; ac_verc_fail=yes;; - 3.0c | 3.0d) + 3.0c | 3.0d | 3.1a) ac_prog_version_m="$ac_prog_version, ok"; ac_verc_fail=no;; *) ac_prog_version_m="$ac_prog_version, bad"; ac_verc_fail=yes;; Index: /trunk/pcc/configure.in =================================================================== --- /trunk/pcc/configure.in (revision 495) +++ /trunk/pcc/configure.in (revision 504) @@ -27,5 +27,5 @@ # can't figure out how to get this into AC_CHECK_PROG_VER below? # have to change it there too -want_bigloo="3.0c, 3.0d" +want_bigloo="3.0c, 3.0d, 3.1a" want_curl=7.15.1 @@ -50,5 +50,5 @@ -revision, [\([2-9].[0-9][a-z]\)], - [3.0c | 3.0d], + [3.0c | 3.0d | 3.1a], AC_MSG_FAILURE([Bigloo version $want_bigloo required in the system path])) The directory structure in /var/tmp/portage/dev-php/roadsend-php-2.9.6/work/roadsend-php-2.9.6 Does not have /trunk/pcc/. The ebuild has defined this as noted in the enviorment file (I will attach): declare -x S="/var/tmp/portage/dev-php/roadsend-php-2.9.6/work/roadsend-php-2.9.6"
Created an attachment (id=151344) [edit] build enviorment
(In reply to comment #6) > Ok same result on another machine. Again I am sorry for my limited knowledge > but it appears that the patch is not right: > [...] > The directory structure in > /var/tmp/portage/dev-php/roadsend-php-2.9.6/work/roadsend-php-2.9.6 > > Does not have > /trunk/pcc/. And it doesn't have to, that's what the patch -p<N> option is for (strip parts of the hardcoded path). We really need the mentioned .rej files so that we can debug it properly.
I thought that the .rej should be in /var/tmp/portage/dev-php/roadsend-php-2.9.6/work/roadsend-php-2.9.6 But I do not find them: roadsend-php-2.9.6 # ls -lha total 354K drwxr-xr-x 15 root root 840 Apr 24 14:09 . drwx------ 3 root root 88 Apr 29 10:13 .. -rw-r--r-- 1 root root 3.6K Apr 2 12:27 Makefile.config.in -rw-r--r-- 1 root root 5.5K Feb 25 07:21 Makefile.in -rw-r--r-- 1 root root 5.3K May 24 2007 Makefile.mingw -rw-r--r-- 1 root root 171 Jan 13 2007 README -rw-r--r-- 1 root root 7.2K Aug 7 2007 acinclude.m4 drwxr-xr-x 5 root root 152 Apr 24 14:09 benchmarks -rw-r--r-- 1 root root 2.5K Feb 19 12:23 bigloo-rules.mk drwxr-xr-x 3 root root 128 Apr 24 14:09 bugs drwxr-xr-x 2 root root 808 Apr 24 14:09 compiler -rwxr-xr-x 1 root root 44K Jun 23 2007 config.guess -rwxr-xr-x 1 root root 32K Jun 23 2007 config.sub -rwxr-xr-x 1 root root 185K Apr 16 10:08 configure -rw-r--r-- 1 root root 14K Apr 16 10:08 configure.in drwxr-xr-x 8 root root 360 Apr 24 14:09 doc -rw-r--r-- 1 root root 15K Jan 23 06:03 dotest.scm -rwxr-xr-x 1 root root 1.9K May 23 2007 install-runtime.sh -rwxr-xr-x 1 root root 1.7K May 23 2007 install.sh drwxr-xr-x 2 root root 48 Apr 24 14:09 libs drwxr-xr-x 7 root root 248 Apr 24 14:09 packages -rw-r--r-- 1 root root 7.9K Apr 3 10:15 php-macros.scm drwxr-xr-x 4 root root 1.3K Apr 24 14:09 runtime drwxr-xr-x 5 root root 208 Apr 24 14:09 sa-tests drwxr-xr-x 2 root root 4.3K Apr 24 14:09 tests drwxr-xr-x 4 root root 144 Apr 24 14:09 tidbits drwxr-xr-x 7 root root 216 Apr 24 14:09 tools drwxr-xr-x 8 root root 312 Apr 24 14:09 webconnect drwxr-xr-x 3 root root 184 Apr 24 14:09 zend-tests Sorry, please let me know where I can find them if I am off base...
ok. Manually going to the directory and typing: patch -p3 -g0 -E --no-backup-if-mismatch < /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch Still fails, but I got the rejects and will attach...
Created an attachment (id=151349) [edit] configure.rej
Created an attachment (id=151350) [edit] configure.in.rej
Just wondering if anyone has any idea why this is happening? I can't see why the patch is failing as everything appears good in the source file as well as the patch as shown in the .rej file. Thanks.
Zach, I'm sorry to say I still have no idea why it fails. Perhaps you should just disable the patch for now. It's only there so that roadsend-php doesn't break when I add new bigloo release (which I'm using already).
Zach, if you still want to get it solved, it might help us if you could attach configure and configure.in (/var/tmp/portage/dev-php/roadsend-php-2.9.6/work/roadsend-php-2.9.6/). I'm really curious what the problem is in this case. It's also a bit strange that above mentioned directory does not contain the *.rej files. BTW: If you're on IRC (Freenode) it might be easier for both you and us to work it out. Both hkBst and me are usually there (#gentoo-php). hkBst, I guess it would be more appropriate to only patch configure.in and run aclocal afterwards -- but I guess you chose not do so because of "performance" reasons (i.e. running autotools for such a minor change)?
Created an attachment (id=152029) [edit] configure ok here is the configure file.
Created an attachment (id=152031) [edit] configure.in and configure.in I will try to get on irc tonight. Anything I can do to help. It isn't a popular package but someone else may run in to this issue I am sure down the road... Thanks.
It fails for me too with the exactly same error. First of all it's -p3 and not -p1 for the patch that's why it says file not found, and there are not .rej/.orig files created. Second, even with -p3 it still fails. # patch -p3 < /usr/portage/dev-php/roadsend-php/files/bigloo-3.1a-configsupport.patch patching file configure Hunk #1 FAILED at 3122. Hunk #2 FAILED at 3192. 2 out of 2 hunks FAILED -- saving rejects to file configure.rej patching file configure.in Hunk #1 FAILED at 27. Hunk #2 FAILED at 50. 2 out of 2 hunks FAILED -- saving rejects to file configure.in.rej # more configure.rej *************** *** 3122,3126 **** # can't figure out how to get this into AC_CHECK_PROG_VER below? # have to change it there too - want_bigloo="3.0c, 3.0d" want_curl=7.15.1 --- 3122,3126 ---- # can't figure out how to get this into AC_CHECK_PROG_VER below? # have to change it there too + want_bigloo="3.0c, 3.0d, 3.1a" want_curl=7.15.1 *************** *** 3192,3196 **** case $ac_prog_version in '') ac_prog_version_m="v. ?.??, bad"; ac_verc_fail=yes;; - 3.0c | 3.0d) ac_prog_version_m="$ac_prog_version, ok"; ac_verc_fail=no;; *) ac_prog_version_m="$ac_prog_version, bad"; ac_verc_fail=yes;; --- 3192,3196 ---- case $ac_prog_version in '') ac_prog_version_m="v. ?.??, bad"; ac_verc_fail=yes;; + 3.0c | 3.0d | 3.1a) ac_prog_version_m="$ac_prog_version, ok"; ac_verc_fail=no;; *) ac_prog_version_m="$ac_prog_version, bad"; ac_verc_fail=yes;; # more configure.in.rej *************** *** 27,31 **** # can't figure out how to get this into AC_CHECK_PROG_VER below? # have to change it there too - want_bigloo="3.0c, 3.0d" want_curl=7.15.1 --- 27,31 ---- # can't figure out how to get this into AC_CHECK_PROG_VER below? # have to change it there too + want_bigloo="3.0c, 3.0d, 3.1a" want_curl=7.15.1 *************** *** 50,54 **** -revision, [\([2-9].[0-9][a-z]\)], - [3.0c | 3.0d], AC_MSG_FAILURE([Bigloo version $want_bigloo required in the system path])) --- 50,54 ---- -revision, [\([2-9].[0-9][a-z]\)], + [3.0c | 3.0d | 3.1a], AC_MSG_FAILURE([Bigloo version $want_bigloo required in the system path]))
(In reply to comment #18) > It fails for me too with the exactly same error. > > First of all it's -p3 and not -p1 for the patch that's why it says file not > found, and there are not .rej/.orig files created. > > Second, even with -p3 it still fails. > > # patch -p3 < > emerge --info please. Panagiotis
Ok, finally you were right. There is an issue with dos line ending and sys-devel/patch-2.5.9. We updated the patch, and repoman commit -m "Updating bigloo's versioning config/support patch, cause of issues with dos line ending and sys-devel/patch-2.5.9, fixes bug 219624" Fixed in cvs.
