From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1ScHZj-00069x-K1 for garchives@archives.gentoo.org; Wed, 06 Jun 2012 14:51:07 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7FE78E06FE; Wed, 6 Jun 2012 14:50:50 +0000 (UTC) Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by pigeon.gentoo.org (Postfix) with ESMTP id E63E1E044C for ; Wed, 6 Jun 2012 14:49:22 +0000 (UTC) Received: by yhp26 with SMTP id 26so5507814yhp.40 for ; Wed, 06 Jun 2012 07:49:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=+BM+6nRstOALKDFOyV+GblJIqdPSxDf/WHUC1Jnvwos=; b=UuRVA8UsPpruYnXy6GwnxjAjX9Cp48CFFzEYicrSVntPi8FHPd2iYy8G/Xum13J0t6 V/Q/hjoPPY+38u7RXcOyvwDJY82EUoQdqAvWjDT4jgPtDGI4cUm5UUthacEnl2op6Nmr Dbi9V410Zl/GReG2oMCiFAXuK5VpAq5xt2vI0SgI6kDfv0H8O+ZuHh6Nswh/Rwd+XT6z qd3fVoYEDsJHu1SlqtfkMotbIihp8NX5qFhvQYfYJm9Ij+PZ1/+HRwbCmcDOpfSmOt/3 3hgfsCmzyslziUGxlxiK9FTAPnAKLSwML4eSgNYLi5hvuVmnaS0UN6XWMySe+mf7faDi D51A== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Received: by 10.50.197.200 with SMTP id iw8mr6944033igc.46.1338994162106; Wed, 06 Jun 2012 07:49:22 -0700 (PDT) Received: by 10.64.81.196 with HTTP; Wed, 6 Jun 2012 07:49:22 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 Jun 2012 22:49:22 +0800 Message-ID: Subject: Re: [gentoo-user]Problem when upgrate to grub2 From: =?GB2312?B?1dS80erN?= To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=14dae9340715637fc004c1cedf91 X-Archives-Salt: c0b38c21-b44c-46b0-bce6-8fb892f999e1 X-Archives-Hash: 3b83c08df62616486d9d601f362c990c --14dae9340715637fc004c1cedf91 Content-Type: text/plain; charset=GB2312 Content-Transfer-Encoding: quoted-printable 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 > hi, see here > > 2012/6/6 =D5=D4=BC=D1=EA=CD > >> Hello, everyone. I want upgrade grub to grub2 , so i follow the doc<= http://dev.gentoo.org/~scarabeus/grub-2-guide.xml>and >> wiki . 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 >> =3Dsys-boot/grub-9999', >> * the complete build log and the output of 'emerge -pqv >> =3Dsys-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 >> =3Dsys-boot/grub-9999', >> * the complete build log and the output of 'emerge -pqv >> =3Dsys-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 ? >> >> -- >> =BA=C3=BA=C3=D1=A7=CF=B0=A3=AC=CC=EC=CC=EC=CF=F2=C9=CF=A3=A1=A3=A1=A3=A1 >> > > --=20 =BA=C3=BA=C3=D1=A7=CF=B0=A3=AC=CC=EC=CC=EC=CF=F2=C9=CF=A3=A1=A3=A1=A3=A1 --14dae9340715637fc004c1cedf91 Content-Type: text/html; charset=GB2312 Content-Transfer-Encoding: quoted-printable 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 <salvo2789@gmail.com><= /span>
hi= , see here

2012/6/6 =D5=D4=BC=D1=EA=CD <jiahui.tar.gz@gmail.com>
    Hello, everyone. I want upgrad= e grub to grub2 , so i follow the doc and wiki . But when= i use the command: "= emerge -av sys-boot/grub:2"
it comes error :  
 * Running autopoint --force ... &nb= sp;                     &= nbsp;                 [ !! ]
 * Failed Running autopoint !
 * 
 * Include in your bugreport the= contents of:
 * 
 *   /var/tmp/portage/sys-boot/grub-= 9999/temp/autopoint.out

 * ERROR: sys-boot/gr= ub-9999 failed (prepare phase):
 *   Failed Running aut= opoint !
 * 
 * Call stack:
 *     ebuild.sh, line   = 85:  Called src_prepare
 *   environment, line 316= 4:  Called source './autogen.sh'
 *   &nbs= p;autogen.sh, line   70:  Called eautoreconf '-vi'
 *   environment, line 1021:  Called eautopoint '--= force'
 *   environment, line  990:  Call= ed 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 'emerg= e --info =3Dsys-boot/grub-9999',
 * the complete build log and the output of 'emerge -pqv =3Dsys-bo= ot/grub-9999'.
 * The complete build log is located at '/var/tmp/portage/sys= -boot/grub-9999/temp/build.log'.
 * The ebuild environme= nt file is located at '/var/tmp/portage/sys-boot/grub-9999/temp/environ= ment'.
 * S: '/var/tmp/portage/sys-boot/grub-9999/work/grub-9999'= ;

>>> Failed to emerge sys-boot/grub-9999= , Log file:

>>>  '/var/tmp/porta= ge/sys-boot/grub-9999/temp/build.log'

 * Messages for package sys-boot/grub-9999:
<= div>
 * Failed Running autopoint !
 *&nbs= p;
 * Include in your bugreport the contents of:
&= nbsp;* 
 *   /var/tmp/portage/sys-boot/grub-9999/t= emp/autopoint.out
 * ERROR: sys-boot/grub-9999 failed (prepare phase):
&n= bsp;*   Failed Running autopoint !
 * 
&= nbsp;* Call stack:
 *     ebuild.sh, line   8= 5:  Called src_prepare
 *   environment, line 3164= :  Called source './autogen.sh'
 *    autogen.sh, line   70:  Called eautorec= onf '-vi'
 *   environment, line 1021:  Ca= lled eautopoint '--force'
 *   environment, lin= e  990:  Called autotools_run_tool 'autopoint' '--for= ce'
 *   environment, line  665:  Called die
 * The specific snippet of code:
 *     &nbs= p;     die "Failed Running $1 !";
 *&nbs= p;
 * If you need support, post the output of 'emerge --= info =3Dsys-boot/grub-9999',
 * the complete build log and the output of 'emerge -pqv =3Ds= ys-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/sy= s-boot/grub-9999/temp/environment'.
 * S: '/var/tmp/portage/sys-boot/grub-9999/work/grub-9999'= ;

Did anyone know how did this happen ?  

--
=BA=C3=BA=C3=D1=A7=CF= =B0=A3=AC=CC=EC=CC=EC=CF=F2=C9=CF=A3=A1=A3=A1=A3=A1




--
= =BA=C3=BA=C3=D1=A7=CF=B0=A3=AC=CC=EC=CC=EC=CF=F2=C9=CF=A3=A1=A3=A1=A3=A1 --14dae9340715637fc004c1cedf91--