From: "Michael Weyershäuser" <thedude0001@gmx.de>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] crossdev x86 to x86_64
Date: Wed, 15 Nov 2006 03:37:15 +0100 [thread overview]
Message-ID: <455A7D5B.80407@gmx.de> (raw)
In-Reply-To: <45546E73.7030305@ilievnet.com>
[-- Attachment #1: Type: text/plain, Size: 2431 bytes --]
Daniel Iliev wrote:
> I tried to use a x86 pc to aid the compiling of packages for amd64 via
> distcc. I followed the official "DistCC Cross-compiling Guide" [1] but I
> had no luck. Is it possible at all, am I doing something wrong or there
> is a bug?
>
> [1] http://www.gentoo.org/doc/en/cross-compiling-distcc.xml
>
I'm running such a setup for about 6 months now and I have never run
into any package not compiling due to the crossdev environment (and I
compile quite a lot of packages as an amd64 AT). So this should in
general work without any trouble or patches.
>
> The i686 pc gives:
>
> localhost ~ # crossdev -t x86_64-pc-linux-gnu
> * You need to set PORTDIR_OVERLAY in your make.conf.
> * A standard setting is /usr/local/portage
> localhost ~ # echo PORTDIR_OVERLAY=/usr/local/portage >> /etc/make.conf
> localhost ~ # crossdev -t x86_64-pc-linux-gnu
> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage'
> !!! Invalid PORTDIR_OVERLAY (not a dir): '/usr/local/portage'
>
> localhost ~ # mkdir /usr/local/portage
> localhost ~ # crossdev -t x86_64-pc-linux-gnu
> --------------------------------------------------------------------------------
> * Host Portage ARCH: x86
> * Target Portage ARCH: amd64
> * Target System: x86_64-pc-linux-gnu
> * Stage: 4 (C/C++ compiler)
>
> * binutils: binutils-[latest]
> * gcc: gcc-[latest]
> * headers: linux-headers-[latest]
> * libc: glibc-[latest]
>
> * PORTDIR_OVERLAY: /usr/local/portage
> * PORT_LOGDIR: /var/log/portage
> * PKGDIR: /usr/portage/packages/cross/x86_64-pc-linux-gnu
> * PORTAGE_TMPDIR: /tmp/cross/x86_64-pc-linux-gnu
> _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~ - _ - ~
> - _ -
> * Forcing the latest versions of binutils-config/gcc-config
> ... [ ok ]
> * Log: /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log
> * Emerging cross-binutils ...
>
> * binutils failed :(
> * If you file a bug, please attach the following logfiles:
> * /var/log/portage/cross-x86_64-pc-linux-gnu-info.log
> * /var/log/portage/cross-x86_64-pc-linux-gnu-binutils.log
If this was a bug I would close it as RESOLVED NEEDINFO right now.
Please attach these two log files if you want anybody to be able to help
you ;)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2006-11-15 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 12:20 [gentoo-amd64] crossdev x86 to x86_64 Daniel Iliev
2006-11-10 12:25 ` Lorenzo Milesi
2006-11-10 13:17 ` Daniel Iliev
2006-11-10 13:31 ` Lorenzo Milesi
2006-11-15 2:37 ` Michael Weyershäuser [this message]
2006-11-16 10:19 ` Daniel Iliev
2006-11-16 10:21 ` Daniel Iliev
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=455A7D5B.80407@gmx.de \
--to=thedude0001@gmx.de \
--cc=gentoo-amd64@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