| 1 |
I have used the command: emerge sys-devel/gettext ,and i'm also run the |
| 2 |
command python-update. It seems didn't work for me. |
| 3 |
|
| 4 |
2012/6/6 Salvatore Borgia <salvo2789@×××××.com> |
| 5 |
|
| 6 |
> hi, see here<http://forums-web1.gentoo.org/viewtopic-t-924710-start-0.html> |
| 7 |
> |
| 8 |
> 2012/6/6 赵佳晖 <jiahui.tar.gz@×××××.com> |
| 9 |
> |
| 10 |
>> Hello, everyone. I want upgrade grub to grub2 , so i follow the doc<http://dev.gentoo.org/~scarabeus/grub-2-guide.xml>and |
| 11 |
>> wiki <http://en.gentoo-wiki.com/wiki/Grub2#Installation> . But when i |
| 12 |
>> use the command: "emerge -av sys-boot/grub:2" |
| 13 |
>> it comes error : |
| 14 |
>> * Running autopoint --force ... |
| 15 |
>> [ !! ] |
| 16 |
>> |
| 17 |
>> * Failed Running autopoint ! |
| 18 |
>> * |
| 19 |
>> * Include in your bugreport the contents of: |
| 20 |
>> * |
| 21 |
>> * /var/tmp/portage/sys-boot/grub-9999/temp/autopoint.out |
| 22 |
>> |
| 23 |
>> * ERROR: sys-boot/grub-9999 failed (prepare phase): |
| 24 |
>> * Failed Running autopoint ! |
| 25 |
>> * |
| 26 |
>> * Call stack: |
| 27 |
>> * ebuild.sh, line 85: Called src_prepare |
| 28 |
>> * environment, line 3164: Called source './autogen.sh' |
| 29 |
>> * autogen.sh, line 70: Called eautoreconf '-vi' |
| 30 |
>> * environment, line 1021: Called eautopoint '--force' |
| 31 |
>> * environment, line 990: Called autotools_run_tool 'autopoint' |
| 32 |
>> '--force' |
| 33 |
>> * environment, line 665: Called die |
| 34 |
>> * The specific snippet of code: |
| 35 |
>> * die "Failed Running $1 !"; |
| 36 |
>> * |
| 37 |
>> * If you need support, post the output of 'emerge --info |
| 38 |
>> =sys-boot/grub-9999', |
| 39 |
>> * the complete build log and the output of 'emerge -pqv |
| 40 |
>> =sys-boot/grub-9999'. |
| 41 |
>> * The complete build log is located at |
| 42 |
>> '/var/tmp/portage/sys-boot/grub-9999/temp/build.log'. |
| 43 |
>> * The ebuild environment file is located at |
| 44 |
>> '/var/tmp/portage/sys-boot/grub-9999/temp/environment'. |
| 45 |
>> * S: '/var/tmp/portage/sys-boot/grub-9999/work/grub-9999' |
| 46 |
>> |
| 47 |
>> >>> Failed to emerge sys-boot/grub-9999, Log file: |
| 48 |
>> |
| 49 |
>> >>> '/var/tmp/portage/sys-boot/grub-9999/temp/build.log' |
| 50 |
>> |
| 51 |
>> * Messages for package sys-boot/grub-9999: |
| 52 |
>> |
| 53 |
>> * Failed Running autopoint ! |
| 54 |
>> * |
| 55 |
>> * Include in your bugreport the contents of: |
| 56 |
>> * |
| 57 |
>> * /var/tmp/portage/sys-boot/grub-9999/temp/autopoint.out |
| 58 |
>> * ERROR: sys-boot/grub-9999 failed (prepare phase): |
| 59 |
>> * Failed Running autopoint ! |
| 60 |
>> * |
| 61 |
>> * Call stack: |
| 62 |
>> * ebuild.sh, line 85: Called src_prepare |
| 63 |
>> * environment, line 3164: Called source './autogen.sh' |
| 64 |
>> * autogen.sh, line 70: Called eautoreconf '-vi' |
| 65 |
>> * environment, line 1021: Called eautopoint '--force' |
| 66 |
>> * environment, line 990: Called autotools_run_tool 'autopoint' |
| 67 |
>> '--force' |
| 68 |
>> * environment, line 665: Called die |
| 69 |
>> * The specific snippet of code: |
| 70 |
>> * die "Failed Running $1 !"; |
| 71 |
>> * |
| 72 |
>> * If you need support, post the output of 'emerge --info |
| 73 |
>> =sys-boot/grub-9999', |
| 74 |
>> * the complete build log and the output of 'emerge -pqv |
| 75 |
>> =sys-boot/grub-9999'. |
| 76 |
>> * The complete build log is located at |
| 77 |
>> '/var/tmp/portage/sys-boot/grub-9999/temp/build.log'. |
| 78 |
>> * The ebuild environment file is located at |
| 79 |
>> '/var/tmp/portage/sys-boot/grub-9999/temp/environment'. |
| 80 |
>> * S: '/var/tmp/portage/sys-boot/grub-9999/work/grub-9999' |
| 81 |
>> |
| 82 |
>> Did anyone know how did this happen ? |
| 83 |
>> |
| 84 |
>> -- |
| 85 |
>> 好好学习，天天向上！！！ |
| 86 |
>> |
| 87 |
> |
| 88 |
> |
| 89 |
|
| 90 |
|
| 91 |
-- |
| 92 |
好好学习，天天向上！！！ |
Archives