Summary: | emerge grub-0.95-20040823 fails from automake version mismatch | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Henry Baxter <henry.baxter> |
Component: | [OLD] Core system | Assignee: | Robert Moss (RETIRED) <robmoss> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | blubb, david.de.ridder, fuzzyray, steeeeeveee |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Henry Baxter
2004-12-02 11:31:42 UTC
I'm having this error too. I guess I'm enough of a newbie not to know how to edit the ebuild b/c every time I do and try to emerge grub it changes back to WANT_AUTOMAKE=1.7 ...I'll figure it out. I'm having tons of problems with automake, however, emerging gtk+ deps from emul10k1 (also wanted automake 1.7) and also while emerging fluxbox. I capitulated and installed automake-1.7, but it hasn't helped me with fluxbox, or grub (says "version mismatch. This is Automake 1.7.9, but the definition used by this AM_INIT_AUTOMAKE comes from Automake 1.8.5. You should recreate aclocal.m4 with aclocal and run automake again." I'll go to the forums with help on the details. I'm having this error too. I guess I'm enough of a newbie not to know how to edit the ebuild b/c every time I do and try to emerge grub it changes back to WANT_AUTOMAKE=1.7 ...I'll figure it out. I'm having tons of problems with automake, however, emerging gtk+ deps from emul10k1 (also wanted automake 1.7) and also while emerging fluxbox. I capitulated and installed automake-1.7, but it hasn't helped me with fluxbox, or grub (says "version mismatch. This is Automake 1.7.9, but the definition used by this AM_INIT_AUTOMAKE comes from Automake 1.8.5. You should recreate aclocal.m4 with aclocal and run automake again." I'll go to the forums with help on the details. It appears that ~x86 has just switched to automake-wrapper. This was not well-thought-through, because in many cases, the upgrade would unmerge automake-1.8, breaking many ebuilds. So if you've recently upgraded automake, I advise you to ACCEPT_KEYWORDS=~x86 emerge -av '<automake-1.9' which should emerge the latest version of automake-1.8. Then, you can emerge grub or whatever. Oops, sorry, I meant '<automake-1.8' , which should emerge the latest version of automake-1.7 (I personally was having problems with 1.8 being unmerged...) Copy the ebuild and the patches to your overlay and change WANT_AUTOMAKE=1.7 to WANT_AUTOMAKE=1.8 - that will solve things. If you don't know how to do that, make sure that PORTDIR_OVERLAY is set in your make.conf (edit it and uncomment the corresponding line) then enter the following commands in sequence: source /etc/make.conf mkdir -p ${PORTDIR_OVERLAY}/sys-boot/grub/files sed -e "s:WANT_AUTOMAKE=1.7:WANT_AUTOMAKE=1.8:g" < ${PORTDIR}/sys-boot/grub/grub-0.95.20040823.ebuild > ${PORTDIR_OVERLAY}/sys-boot/grub/grub-0.95.20040823.ebuild cp ${PORTDIR}/sys-boot/grub/files/grub-0.95.20040823-warnings.patch ${PORTDIR_OVERLAY}/sys-boot/grub/files cp ${PORTDIR}/sys-boot/grub/files/splash.xpm.gz ${PORTDIR_OVERLAY}/sys-boot/grub/files sed -e ebuild ${PORTDIR_OVERLAY}/sys-boot/grub/grub-0.95.20040823.ebuild digest That will fix the automake problems and will allow you to emerge grub 0.95 just fine. Argh. Ignore the second sed -e line above. I should doublecheck things before pushing buttons... this is terrible the community is going to hell this bug is verified and has the resolution sitting here instead of in the portage tree. devs need to really step up and start updating the tree so ppl dont have to hunt for fixes I have seen these problems the last few weeks all cause devs are not updating like they need to be I think it is time we find some bug devs to find bugs that should be resolved and add to portage so ppl dont have to hunt down a fix like this in the middle of there installs. Jory A. Pratt: Stop complaining! If you realy want to help, then please request to add you as a Gentoo developer and then help them out with your time and your knowledge to get things faster done. fixed now. reply to comment #7: i'm sure everybody is doing his best, but there are lots of bugs, not only this one. also, many devs have other things to do (family, work, whatever) so please be insightful. and never forget: you didn't pay a single cent, so you can't expect anything. that doesn't mean you're not welcome to give useful information about bugs and/or solutions as steveb said, if you think those stupid devs aren't doing their homework, become one and change your mind ;) |