From: "Walter Dnes" <waltdnes@waltdnes.org>
To: Gentoo Users List <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] crossdev setup questions for distcc usage
Date: Thu, 19 Mar 2015 19:35:29 -0400 [thread overview]
Message-ID: <20150319233529.GA19024@waltdnes.org> (raw)
In-Reply-To: <20150319213108.GA11283@waltdnes.org>
[-- Attachment #1: Type: text/plain, Size: 304 bytes --]
Next step was "crossdev -t -S i686-pc-linux-gnu". One thing I'm
worried about; the default is stage 4, but the output mentions...
"Emerging cross-gcc-stage2". Is this a problem? See attached file
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
[-- Attachment #2: x.txt --]
[-- Type: text/plain, Size: 1929 bytes --]
[d531][root][~] crossdev -t -S i686-pc-linux-gnu
--------------------------------------------------------------------------------
* crossdev version: 20140917
* Host Portage ARCH: amd64
* Target Portage ARCH: x86
* Target System: i686-pc-linux-gnu
* Stage: 4 (C/C++ compiler)
* ABIs: default
* binutils: binutils-[latest]
* gcc: gcc-[latest]
* headers: linux-headers-[latest]
* libc: glibc-[latest]
* CROSSDEV_OVERLAY: /usr/local/portage
* PORT_LOGDIR: /var/log/portage
* PORTAGE_CONFIGROOT:
* Portage flags:
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ -
* leaving metadata/layout.conf alone in /usr/local/portage
_ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ -
* Log: /var/log/portage/cross-i686-pc-linux-gnu-binutils.log
* Emerging cross-binutils ... [ ok ]
* Log: /var/log/portage/cross-i686-pc-linux-gnu-linux-headers-quick.log
* Emerging cross-linux-headers-quick ... [ ok ]
* Log: /var/log/portage/cross-i686-pc-linux-gnu-glibc-headers.log
* Emerging cross-glibc-headers ... [ ok ]
* Log: /var/log/portage/cross-i686-pc-linux-gnu-gcc-stage1.log
* Emerging cross-gcc-stage1 ... [ ok ]
* Log: /var/log/portage/cross-i686-pc-linux-gnu-linux-headers.log
* Emerging cross-linux-headers ... [ ok ]
* Log: /var/log/portage/cross-i686-pc-linux-gnu-glibc.log
* Emerging cross-glibc ... [ ok ]
* Log: /var/log/portage/cross-i686-pc-linux-gnu-gcc-stage2.log
* Emerging cross-gcc-stage2 ... [ ok ]
[d531][root][~]
next prev parent reply other threads:[~2015-03-19 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 21:31 [gentoo-user] crossdev setup questions for distcc usage Walter Dnes
2015-03-19 23:35 ` Walter Dnes [this message]
2015-03-20 14:02 ` [gentoo-user] " James
2015-03-21 10:13 ` Walter Dnes
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=20150319233529.GA19024@waltdnes.org \
--to=waltdnes@waltdnes.org \
--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