public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] gentoo cross-emerging for sh4 architecture
Date: Sun, 19 Feb 2006 23:46:12 -0500	[thread overview]
Message-ID: <1140410772.4308.39.camel@localhost> (raw)
In-Reply-To: <200602191907.22206.ladmanj@volny.cz>

emerge does not read make.conf from $ROOT.

You need to wrapper the command.
try a script that does something like.
http://dev.gentoo.org/~spb/tmp/memerge
but replace the mips arch with sh for your case.



On Sun, 2006-02-19 at 19:07 +0100, Jakub Ladman wrote:
> Hello
> I'm trying to make gentoo system on our development board with renesas sh4 
> CPU.
> I allready have created the cross-compiler toolchain using crossdev -t 
> sh4-pc-linux-uclibc
> I have to unpack stage3-sh4-uclibc-2006.0.tar.bz2 from vapiers archive to 
> target directory /home/ladmanj/sh4system.
> But if I try to run ROOT="/home/ladmanj/sh4system" emerge minicom (for an 
> example), it uses not the targets make.conf file 
> (/home/ladmanj/sh4system/etc/make.conf) but the host systems one.
> Please tell me the correct way to cross-emerge ebuilds for my embedded system, 
> or give me links to similar project.
> Thank you.
> Best regards
> Jakub Ladman
> 
> PS: I also tryed 
> ROOT="/home/ladmanj/sh4system" CHOST="sh4-gentoo-linux-uclibc" emerge minicom
> everything looks fine but the output in target directory is i686 executable. 
> Grrrr
> I do not know why.
-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-embedded@gentoo.org mailing list



  reply	other threads:[~2006-02-20  4:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19 18:07 [gentoo-embedded] gentoo cross-emerging for sh4 architecture Jakub Ladman
2006-02-20  4:46 ` Ned Ludd [this message]
2006-02-20 15:47   ` Jakub Ladman
2006-02-20 16:10     ` solar
2006-02-20 16:15       ` Jakub Ladman
2006-02-20 20:17       ` Mike Frysinger

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=1140410772.4308.39.camel@localhost \
    --to=solar@gentoo.org \
    --cc=gentoo-embedded@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