View previous topic :: View next topic |
Author |
Message |
cynric Guru
Joined: 08 Oct 2004 Posts: 439
|
Posted: Sun Mar 05, 2006 8:44 pm Post subject: [Fixed] openmotif-2.2.3-r9 fails to find patches |
|
|
Code: | * Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /var/portage/x11-libs/openmotif/files/openmotif-2.2.3-CAN-2004-0687-0688.patch.bz2
* ( openmotif-2.2.3-CAN-2004-0687-0688.patch.bz2 )
!!! ERROR: x11-libs/openmotif-2.2.3-r9 failed.
Call stack:
ebuild.sh, line 1933: Called dyn_unpack
ebuild.sh, line 719: Called src_unpack
openmotif-2.2.3-r9.ebuild, line 50: Called epatch 'unpack'
!!! Cannot find $EPATCH_SOURCE!
!!! If you need support, post the topmost build error, and the call stack if relevant. |
Typical run of the mill error. I haven't seen anyone else complain yet which kinda bothers me. Anyway, this patch does exist, but not as a bunzip. I edited the ebuild and rebuilt the manifest. Next it complains about openmotif-2.2.3-CAN-2004-0914-newer.patch.bz2 which doesn't exist at all. A file rename I'm ok with, but when patches flat don't showup, I assume there's a deeper problem. Anyone else see this? Safe to comment out the line from the ebuild? I'd bug it, but wanna make sure that I'm not somehow using a non-corrupt/current ebuild first.
Also, is that "Call stack" portion part of portage's new debugging info to state exactly in what part of the ebuild it failed? Been seeing it a lot lately unfortunately.
Last edited by cynric on Mon Mar 06, 2006 9:55 pm; edited 1 time in total |
|
Back to top |
|
|
frenkel Veteran
Joined: 13 May 2003 Posts: 1034 Location: .nl
|
Posted: Sun Mar 05, 2006 8:59 pm Post subject: |
|
|
Did you try an emerge sync? |
|
Back to top |
|
|
cynric Guru
Joined: 08 Oct 2004 Posts: 439
|
Posted: Sun Mar 05, 2006 9:18 pm Post subject: |
|
|
Aye. I did another just now even though it's my fourth for the day. Same two patches causing problems. |
|
Back to top |
|
|
d_m Guru
Joined: 12 Jun 2003 Posts: 570 Location: Philadelphia, PA, USA
|
Posted: Sun Mar 05, 2006 10:50 pm Post subject: |
|
|
I just saw this today during an "emerge -NDuav world".
I'll try to --sync again tomorrow and see how it goes. _________________ The name that can be named is not the eternal name. |
|
Back to top |
|
|
cynric Guru
Joined: 08 Oct 2004 Posts: 439
|
Posted: Sun Mar 05, 2006 10:59 pm Post subject: |
|
|
Ok, so I'm not the only one. I'll wait until after this movie (another 30mins) and I'll put up a bug. Maybe others will pipe in to confirm. |
|
Back to top |
|
|
Qwertys n00b
Joined: 10 May 2005 Posts: 10
|
Posted: Mon Mar 06, 2006 12:02 am Post subject: |
|
|
got it here too, same error got it when trying to update world. |
|
Back to top |
|
|
cynric Guru
Joined: 08 Oct 2004 Posts: 439
|
|
Back to top |
|
|
SolidSnakex28 Apprentice
Joined: 03 Sep 2005 Posts: 269 Location: New York
|
Posted: Mon Mar 06, 2006 1:10 am Post subject: |
|
|
So how soon might this be fixed? I can't use xorg-x11 until this is fixed. |
|
Back to top |
|
|
cynric Guru
Joined: 08 Oct 2004 Posts: 439
|
Posted: Mon Mar 06, 2006 1:39 am Post subject: |
|
|
After someone finally takes note of it, it'll need some time to propagate throughout the rsync servers. If it is only a simple matter of being able to comment out the 0914 patch, then you won't have to wait for the rsync as you can edit it on your own. However, I highly doubt it'll be that easy. Keep an eye on the bug as that'll be where the most up to date info will be out.
Also, I wouldn't think you'd have to use that particular version. Perhaps simply using a previous version will work. Or even pulling the patch, if it exists, from an older tarball. The only way to know for sure about a surrogate patch is to wait for a dev to reply. But, using an older version should be fine and get you your xorg up and running. |
|
Back to top |
|
|
SolidSnakex28 Apprentice
Joined: 03 Sep 2005 Posts: 269 Location: New York
|
Posted: Mon Mar 06, 2006 2:43 am Post subject: |
|
|
I tried previous versions, but r8 and r7 get the same problem, and any version before that wants xorg-6.8. Where might I be able to find the patch? I'm googleing it now with no luck... |
|
Back to top |
|
|
cynric Guru
Joined: 08 Oct 2004 Posts: 439
|
Posted: Mon Mar 06, 2006 2:56 am Post subject: |
|
|
Ok, so if it's the same problem then that means it's specifically the two patches and not the ebuilds. So, unless you (or someone else) just so happen to have an old tarball laying around, I don't think there is an answer. Well, short of some dev knowing who has a copy or digging around in cvs. Sorry man. Waiting sucks. :( |
|
Back to top |
|
|
bluni n00b
Joined: 27 Jan 2006 Posts: 29
|
Posted: Mon Mar 06, 2006 4:20 am Post subject: |
|
|
I recently did a fresh minimal install of 2006.0 and I receive the error as well trying to emerge modular xorg-x11. Just confirming it happening on a fresh recent install as well.
Brian
P.S. Pentium4 machine as well, I just saw the bug was submitted as a amd64 user, and I didn't think it would matter, but I figured i'd just let everyone know.
emerge --version
Portage 2.1_pre5-r4 (default-linux/x86/2006.0, gcc-3.4.5, glibc-2.3.6-r3, 2.6.15-gentoo-r7 i686) |
|
Back to top |
|
|
cynric Guru
Joined: 08 Oct 2004 Posts: 439
|
Posted: Mon Mar 06, 2006 4:31 am Post subject: |
|
|
The bug shouldn't be taken as amd64 only, but if you ever want to chime in, it's best to do it on the bug itself since many of the people working there don't visit the forums -- and, if they did, they'd be lucky to find a particular thread that related to a bug. |
|
Back to top |
|
|
Manfred n00b
Joined: 27 Apr 2004 Posts: 65
|
Posted: Mon Mar 06, 2006 3:26 pm Post subject: |
|
|
cynric wrote: | Maybe others will pipe in to confirm. |
Yes: Same error here too (x86/2006.0); dto. similarly even with earlier ebuilds ( -r8 ) that had worked before:
____ o ) unzipped *.patch vs. *.patch.bz
____ o ) missing "...newer..."
P.S.: I've added this "dito" to your Bug report. |
|
Back to top |
|
|
Blackdream Tux's lil' helper
Joined: 16 Dec 2004 Posts: 131 Location: Germany,Munich,Unterhaching
|
|
Back to top |
|
|
Manfred n00b
Joined: 27 Apr 2004 Posts: 65
|
Posted: Mon Mar 06, 2006 5:01 pm Post subject: |
|
|
Quote: | P.S.: I've added this "dito" to your Bug report. |
Added a manual workaround into the Bug report:
https://bugs.gentoo.org/show_bug.cgi?id=125149#c4
- it's compiling right now; let's see.
EDIT: P.S.:
>>> x11-libs/openmotif-2.2.3-r9 merged. |
|
Back to top |
|
|
Qwertys n00b
Joined: 10 May 2005 Posts: 10
|
Posted: Mon Mar 06, 2006 5:24 pm Post subject: |
|
|
i downloaded this "newer" patch and followed the instructions on the bug report but i get the same error:
Code: | * Applying openmotif-2.2.3-mwm-configdir.patch ... [ ok ]
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/portage/x11-libs/openmotif/files/openmotif-2.2.3-CAN-2004-0687-0688.patch.bz2
* ( openmotif-2.2.3-CAN-2004-0687-0688.patch.bz2 )
!!! ERROR: x11-libs/openmotif-2.2.3-r9 failed.
!!! Function epatch, Line 207, Exitcode 0
!!! Cannot find $EPATCH_SOURCE!
|
|
|
Back to top |
|
|
Rumzajs n00b
Joined: 04 May 2005 Posts: 33
|
Posted: Mon Mar 06, 2006 6:33 pm Post subject: |
|
|
Qwertys wrote: | i downloaded this "newer" patch and followed the instructions on the bug report but i get the same error:
Code: | * Applying openmotif-2.2.3-mwm-configdir.patch ... [ ok ]
* Cannot find $EPATCH_SOURCE! Value for $EPATCH_SOURCE is:
*
* /usr/portage/x11-libs/openmotif/files/openmotif-2.2.3-CAN-2004-0687-0688.patch.bz2
* ( openmotif-2.2.3-CAN-2004-0687-0688.patch.bz2 )
!!! ERROR: x11-libs/openmotif-2.2.3-r9 failed.
!!! Function epatch, Line 207, Exitcode 0
!!! Cannot find $EPATCH_SOURCE!
|
|
1. Download "http://dev.gentoo.org/~dercorny/openmotif-2.2.3-CAN-2004-0914-newer.patch.bz2" and put it in /usr/portage/x11-libs/openmotif/files
2. Edit the file "/usr/portage/x11-libs/openmotif/openmotif-2.2.3-r9.ebuild"
change the line "epatch ${FILESDIR}/${P}-CAN-2004-0687-0688.patch.bz2" in "epatch ${FILESDIR}/${P}-CAN-2004-0687-0688.patch"
(the .bz2 was wrong)
3. Run : ebuild openmotif-2.2.3-r9.ebuild digest
4. emerge openmotif |
|
Back to top |
|
|
cynric Guru
Joined: 08 Oct 2004 Posts: 439
|
Posted: Mon Mar 06, 2006 9:55 pm Post subject: |
|
|
Ok, the bug was resolved so all new instances should be fixed. For those of you too lazy to check the bug: Simon Stelling wrote: | okay, this sucks. I did some cleanups recently and apparently CVS just sucked
up all my ebuild/Changelog changes and only committed the cvs rms, leaving
everything broken. but then it somehow even deleted my versions of the ebuilds
so that i ended up fixing everything *again*. *grrrr*. anyway, it should be
finally fixed now, sorry for the inconvenience :(( |
Thread status changed to "Fixed". Good luck guys. |
|
Back to top |
|
|
SolidSnakex28 Apprentice
Joined: 03 Sep 2005 Posts: 269 Location: New York
|
Posted: Mon Mar 06, 2006 11:49 pm Post subject: |
|
|
Great! I did emerge --sync && emerge openmotif and it worked. Thanks people! |
|
Back to top |
|
|
^SMOK^ n00b
Joined: 08 May 2005 Posts: 3 Location: Poland
|
Posted: Thu Mar 09, 2006 9:08 pm Post subject: EE New Problem |
|
|
Code: | In file included from XmStrDefs.c:10:
../Xm/Xm.h:59:34: X11/extensions/Print.h: No such file or directory
In file included from XmStrDefs.c:10:
../Xm/Xm.h:827: error: syntax error before "XPContext"
../Xm/Xm.h:827: warning: no semicolon at end of struct or union
../Xm/Xm.h:830: error: syntax error before '}' token
../Xm/Xm.h:830: warning: type defaults to `int' in declaration of `XmPrintShellCallbackStruct'
../Xm/Xm.h:830: warning: data definition has no type or storage class
make[2]: *** [XmStrDefs.lo] Error 1
make[2]: Leaving directory `/var/tmp/portage/openmotif-2.2.3-r9/work/openMotif-2.2.3/lib/Xm'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/openmotif-2.2.3-r9/work/openMotif-2.2.3/lib'
make: *** [all-recursive] Error 1
!!! ERROR: x11-libs/openmotif-2.2.3-r9 failed.
Call stack:
ebuild.sh, line 1933: Called dyn_compile
ebuild.sh, line 971: Called src_compile
!!! make failed, if you have lesstif installed removed it, compile openmotif and recompile lesstif
!!! If you need support, post the topmost build error, and the call stack if relevant.
|
I get this when compiling - ee help.. _________________ Will make gentoo working.. "I holp" |
|
Back to top |
|
|
cynric Guru
Joined: 08 Oct 2004 Posts: 439
|
Posted: Fri Mar 10, 2006 4:15 pm Post subject: |
|
|
That's an unrelated problem, but looks like the problem is easy enough to fix. There appears to be no semi-colon on a line prior to line number 827 of Xm.h. Although you can add this yourself (from my limited debugging experience, that's what I'm getting from the error), it's best to use bugzilla so that we can get this fixed in CVS. |
|
Back to top |
|
|
lloda n00b
Joined: 12 Mar 2006 Posts: 1
|
Posted: Sun Mar 12, 2006 6:45 pm Post subject: |
|
|
I had the same problem.
Try this:
emerge printproto xextproto xbitmaps
emerge libXaw libXmu libXp
emerge openmotif
Please let me know if this fixes the problem for you. |
|
Back to top |
|
|
rthealey n00b
Joined: 08 Apr 2005 Posts: 19 Location: Rochester, NY
|
Posted: Tue Mar 21, 2006 12:24 pm Post subject: |
|
|
lloda,
I was getting the exact same error as ^SMOK^ this morning.
Your sugguestion worked perfectly to fix the error!
Thanks,
Ron _________________ --Toshiba Satellite 5105-S901--
Pentium 4 M 2GHz, Intel 845MP Chipset, 512MB RAM, nVidia GeForce4 440 Go 64MB DDR, DVD/CDRW multi-drive, Integrated 802.11b, Integrated 10/100 LAN, Integrated 56K modem, Integrated Bluetooth, cPad pointing device |
|
Back to top |
|
|
cbx550f Tux's lil' helper
Joined: 11 Jun 2004 Posts: 113 Location: Ontario, Canada
|
Posted: Tue Apr 04, 2006 10:56 pm Post subject: |
|
|
lloda wrote: | I had the same problem.
Try this:
emerge printproto xextproto xbitmaps
emerge libXaw libXmu libXp
emerge openmotif
Please let me know if this fixes the problem for you. |
I just had this problem after completely wiping X and installing xorg-7, I had to:
emerge libXp xbitmaps
(The emerge libxp got be by the "Print.h" bit, but then it was missing the bitmaps)
Thanks for the help!
cbx _________________ I think, therefore I am wrong. |
|
Back to top |
|
|
|