public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss03@volumehost.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] OT - I've built my cross-compilation environment; now what?
Date: Thu, 16 Mar 2006 00:13:00 -0600	[thread overview]
Message-ID: <200603160013.00380.bss03@volumehost.net> (raw)
In-Reply-To: <1142448499.13071.4.camel@camille.espersunited.com>

On Wednesday 15 March 2006 12:48, Michael Sullivan 
<michael@espersunited.com> wrote about '[gentoo-user] OT - I've built my 
cross-compilation environment; now what?':
> I've succeeded in building a cross-compilation environment for an i586
> on an i686 via crossdev, but I'm unsure how to use it.  Can anyone help
> me?  There are no docs for crossdev in /usr/share/doc, no man pages for
> it that I can find, and no info pages.  I looked at the log files

Good luck finding solid cross-compilation documentation for /any/ 
environment.  That's black magic only practiced by high-geeks. ;)  Even 
they avoid it when possible because of the high toll on the practitioners 
sanity. ;)

Most of us only use the cross-compilation toolchain for such geek-bishop 
activities as distcc.

> crossdev created when I ran it and I see things like this:
> >>> emerge (1 of 1) cross-i586-gnu-linux/gcc-3.4.5-r1 to /
>
> But when I try to emerge things myself for the environment, emerge
> doesn't know what I'm talking about:
>
> camille ~ # emerge cross-i586-gnu-linux/mysql
> Calculating dependencies
> emerge: there are no ebuilds to satisfy "cross-i586-gnu-linux/mysql".

It's not quite that easy.  You may need to change your make.conf, 
make.profile, and /etc/portage to correct values for the TARGET 
architecture (emerge will still use them and a -march=i686 will ruin the 
packages you build, even if you use i586-pc-linux-gnu-gcc to build them), 
then make sure and run emerge with the ROOT in your environment set to 
where you want the alternate installation rooted.

Check out http://dev.gentoo.org/~vapier/CROSS-COMPILE-HOWTO .  Specifically 
the very bottom (Step 9) where he talks about installing stuff.

WARNING: I've heard some ebuilds don't respect ROOT and/or that ROOT is 
ignored if you try and specify it in make.conf.

NB: The cross-* categories are only for the toolchain.  Other packages 
don't use their category for cross-compiling.

-- 
"If there's one thing we've established over the years,
it's that the vast majority of our users don't have the slightest
clue what's best for them in terms of package stability."
-- Gentoo Developer Ciaran McCreesh
-- 
gentoo-user@gentoo.org mailing list



      reply	other threads:[~2006-03-16  6:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-15 18:48 [gentoo-user] OT - I've built my cross-compilation environment; now what? Michael Sullivan
2006-03-16  6:13 ` Boyd Stephen Smith Jr. [this message]

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=200603160013.00380.bss03@volumehost.net \
    --to=bss03@volumehost.net \
    --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