From: Steven Trogdon <strogdon@d.umn.edu>
To: gentoo-alt@lists.gentoo.org
Subject: Re: [gentoo-alt] problems with bootstrapping in Gentoo-prefix
Date: Fri, 1 Feb 2013 11:47:45 -0600 [thread overview]
Message-ID: <20130201114745.4b8cde05@ledaig.d.umn.edu> (raw)
In-Reply-To: <CAL_rV8Wm8JycH6Z-eh4t1dtR30nc+aNYyBAb=zquKSMWiAaFEw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]
On Fri, 1 Feb 2013 01:57:09 -0500
Linpeng Tang <chnttlp@gmail.com> wrote:
> Hi,
>
> I am trying to install gentoo-prefix on another CentOS 5 server. I followed
> heroxbd's previous advice but ran into some new problems. The installation
> fails at gcc-config-1.8, and the build log says
>
> >>> Compiling source in
> /state/partition1/linpengt/gentoo/var/tmp/portage/sys-devel/gcc-config-1.8-r00.1/work/gcc-config-1.8
> ...
> make -j5 EPREFIX=/state/partition1/linpengt/gentoo
> CC=x86_64-pc-linux-gnu-gcc
> make: *** No rule to make target `wrapper.c.in', needed by `wrapper.c'.
> Stop.
> emake failed
> * ERROR: sys-devel/gcc-config-1.8-r00.1 failed (compile phase):
> * (no error message)
> *
> * Call stack:
> * ebuild.sh, line 85: Called call-ebuildshell 'src_compile'
> * environment, line 441: Called src_compile
> * environment, line 2223: Called die
> * The specific snippet of code:
> * emake EPREFIX="${EPREFIX}" CC="$(tc-getCC)" || die
>
> Does anyone has any idea what's causing the problem?
>
> Best regards.
>
Hi Linpeng,
Yes I encountered this issue on a fresh install of prefix. For some reason at
this point in building stage3 these lines
rename from wrapper.c
rename to wrapper.c.in
--- a/wrapper.c
+++ b/wrapper.c.in
in 'gcc-config-prefix-1.8-r221.patch' don't appear to be doing what's
intended. If you modify 'gcc-config-1.8-r00.1.ebuild' to read:
src_prepare() {
epatch "${FILESDIR}"/${PN}-prefix-${PV}-r${PREFIXREV}.patch
epatch "${FILESDIR}"/${P}-copy-gcc-libs.patch
mv wrapper.c wrapper.c.in
}
and then regenerate the manifest (from a shell where EPREFIX and PATH have been
exported), i.e.
ebuild <path-to-gcc-config-1.8-r00.1.ebuild> manifest
then you should be able to continue with building stage3. This worked for me. It
is not a solution, just a band-aid.
Steve
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-01 17:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-19 22:12 [gentoo-alt] problems with bootstrapping in Gentoo-prefix Linpeng Tang
2013-01-19 22:28 ` [gentoo-alt] " Linpeng Tang
2013-01-21 7:35 ` heroxbd
2013-01-21 8:31 ` [gentoo-alt] " Christopher Schwan
2013-01-21 15:18 ` Linpeng Tang
2013-01-22 3:12 ` Linpeng Tang
2013-01-22 7:19 ` heroxbd
2013-01-22 22:19 ` Fabian Groffen
2013-01-23 14:32 ` Linpeng Tang
2013-01-24 0:51 ` Linpeng Tang
2013-01-24 4:41 ` heroxbd
2013-01-25 8:39 ` heroxbd
2013-01-26 6:25 ` Linpeng Tang
2013-01-26 11:29 ` heroxbd
2013-02-01 6:57 ` Linpeng Tang
2013-02-01 17:47 ` Steven Trogdon [this message]
2013-02-02 12:37 ` Fabian Groffen
2013-02-02 14:41 ` Linpeng Tang
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=20130201114745.4b8cde05@ledaig.d.umn.edu \
--to=strogdon@d.umn.edu \
--cc=gentoo-alt@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