From: 赵佳晖 <jiahui.tar.gz@gmail.com>
To: gentoo-user <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user]Problem when upgrate to grub2
Date: Wed, 6 Jun 2012 21:07:17 +0800 [thread overview]
Message-ID: <CAJf79ng51ab1p+NMJiPYAQ2nLTzDM1EPs9t5YThNR8sO58FgBQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2792 bytes --]
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 ?
--
好好学习,天天向上!!!
[-- Attachment #2: Type: text/html, Size: 4444 bytes --]
next reply other threads:[~2012-06-06 13:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 13:07 赵佳晖 [this message]
2012-06-06 13:22 ` [gentoo-user]Problem when upgrate to grub2 Salvatore Borgia
2012-06-06 14:49 ` 赵佳晖
2012-06-06 15:06 ` Salvatore Borgia
2012-06-06 15:51 ` 赵佳晖
2012-06-06 16:16 ` Salvatore Borgia
2012-06-06 18:00 ` Neil Bothwick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJf79ng51ab1p+NMJiPYAQ2nLTzDM1EPs9t5YThNR8sO58FgBQ@mail.gmail.com \
--to=jiahui.tar.gz@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox