have you tried to add that line to your configure.ac file? 2012/6/6 赵佳晖 <[email protected]>
> of course,the autopoint.out is below: > > ***** autopoint ***** > ***** PWD: /var/tmp/portage/sys-boot/grub-9999/work/grub-9999 > ***** autopoint --force > > autopoint: *** Missing version: please specify in configure.ac through a > line 'AM_GNU_GETTEXT_VERSION(x.yy.zz)' the gettext version the package is > using > autopoint: *** Stop. > > > 2012/6/6 Salvatore Borgia <[email protected]> > >> can you post your autopoint.out please? >> >> 2012/6/6 赵佳晖 <[email protected]> >> >>> I have used the command: emerge sys-devel/gettext ,and i'm also run the >>> command python-update. It seems didn't work for me. >>> >>> >>> 2012/6/6 Salvatore Borgia <[email protected]> >>> >>>> hi, see here<http://forums-web1.gentoo.org/viewtopic-t-924710-start-0.html> >>>> >>>> 2012/6/6 赵佳晖 <[email protected]> >>>> >>>>> Hello, everyone. I want upgrade grub to grub2 , so i follow the >>>>> doc <http://dev.gentoo.org/~scarabeus/grub-2-guide.xml> and >>>>> wiki<http://en.gentoo-wiki.com/wiki/Grub2#Installation>. But when i use >>>>> the command: "emerge >>>>> -av sys-boot/grub:2" >>>>> it comes error : >>>>> * Running autopoint --force ... >>>>> [ !! ] >>>>> >>>>> * Failed Running autopoint ! >>>>> * >>>>> * Include in your bugreport the contents of: >>>>> * >>>>> * /var/tmp/portage/sys-boot/grub-9999/temp/autopoint.out >>>>> >>>>> * ERROR: sys-boot/grub-9999 failed (prepare phase): >>>>> * Failed Running autopoint ! >>>>> * >>>>> * Call stack: >>>>> * ebuild.sh, line 85: Called src_prepare >>>>> * environment, line 3164: Called source './autogen.sh' >>>>> * autogen.sh, line 70: Called eautoreconf '-vi' >>>>> * environment, line 1021: Called eautopoint '--force' >>>>> * environment, line 990: Called autotools_run_tool 'autopoint' >>>>> '--force' >>>>> * environment, line 665: Called die >>>>> * The specific snippet of code: >>>>> * die "Failed Running $1 !"; >>>>> * >>>>> * If you need support, post the output of 'emerge --info >>>>> =sys-boot/grub-9999', >>>>> * the complete build log and the output of 'emerge -pqv >>>>> =sys-boot/grub-9999'. >>>>> * The complete build log is located at >>>>> '/var/tmp/portage/sys-boot/grub-9999/temp/build.log'. >>>>> * The ebuild environment file is located at >>>>> '/var/tmp/portage/sys-boot/grub-9999/temp/environment'. >>>>> * S: '/var/tmp/portage/sys-boot/grub-9999/work/grub-9999' >>>>> >>>>> >>> Failed to emerge sys-boot/grub-9999, Log file: >>>>> >>>>> >>> '/var/tmp/portage/sys-boot/grub-9999/temp/build.log' >>>>> >>>>> * Messages for package sys-boot/grub-9999: >>>>> >>>>> * Failed Running autopoint ! >>>>> * >>>>> * Include in your bugreport the contents of: >>>>> * >>>>> * /var/tmp/portage/sys-boot/grub-9999/temp/autopoint.out >>>>> * ERROR: sys-boot/grub-9999 failed (prepare phase): >>>>> * Failed Running autopoint ! >>>>> * >>>>> * Call stack: >>>>> * ebuild.sh, line 85: Called src_prepare >>>>> * environment, line 3164: Called source './autogen.sh' >>>>> * autogen.sh, line 70: Called eautoreconf '-vi' >>>>> * environment, line 1021: Called eautopoint '--force' >>>>> * environment, line 990: Called autotools_run_tool 'autopoint' >>>>> '--force' >>>>> * environment, line 665: Called die >>>>> * The specific snippet of code: >>>>> * die "Failed Running $1 !"; >>>>> * >>>>> * If you need support, post the output of 'emerge --info >>>>> =sys-boot/grub-9999', >>>>> * the complete build log and the output of 'emerge -pqv >>>>> =sys-boot/grub-9999'. >>>>> * The complete build log is located at >>>>> '/var/tmp/portage/sys-boot/grub-9999/temp/build.log'. >>>>> * The ebuild environment file is located at >>>>> '/var/tmp/portage/sys-boot/grub-9999/temp/environment'. >>>>> * S: '/var/tmp/portage/sys-boot/grub-9999/work/grub-9999' >>>>> >>>>> Did anyone know how did this happen ? >>>>> >>>>> -- >>>>> 好好学习，天天向上！！！ >>>>> >>>> >>>> >>> >>> >>> -- >>> 好好学习，天天向上！！！ >>> >> >> > > > -- > 好好学习，天天向上！！！ >
