From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] crossdev & ports questions
Date: Mon, 20 Sep 2010 16:00:25 -0400 [thread overview]
Message-ID: <201009201600.25912.vapier@gentoo.org> (raw)
In-Reply-To: <OF7EAFE958.B5D51F4D-ONC12577A4.00684691-C12577A4.0068689B@transmode.se>
[-- Attachment #1: Type: Text/Plain, Size: 1109 bytes --]
On Monday, September 20, 2010 15:00:25 Joakim Tjernlund wrote:
> I am fiddling with crossdev again and I wonder if there a way to
> pass different configure options to gcc/binutils vs. glibc?
> Doing export EXTRA_ECONF="--with-cpu=e300c2" applies
> to all and glibc bombs with subarch not supported error.
you'd have to use per-package env manually:
/etc/portage/env/$CATEGORY/$PN
but crossdev likes to clobber this file for you. so i guess i should extend
crossdev with --env-xxx options so people can add their own.
> Second, there are not many PowerPC cpus in the ports section
> of glibc and not mine embedded one either. Is there any
> alternative ports pkg somewhere that supports more PowerPC
> cpus?
we take what glibc offers via their glibc-ports package. personally, i do 0
embedded powerpc work, so i dont know of any "alternatives" or such.
if they did exist though, the only way currently to get them transparently
added would be to make a big patch out of them and then use the user patch
interface (put patches into /etc/portage/patches/$CATEGORY/$P/).
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-09-20 20:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 19:00 [gentoo-embedded] crossdev & ports questions Joakim Tjernlund
2010-09-20 20:00 ` Mike Frysinger [this message]
2010-09-20 21:08 ` Joakim Tjernlund
2010-09-20 22:39 ` Mike Frysinger
2010-10-08 3:10 ` Mike Frysinger
2010-10-08 6:56 ` Joakim Tjernlund
2010-10-08 7:52 ` Joakim Tjernlund
2010-10-08 8:46 ` 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=201009201600.25912.vapier@gentoo.org \
--to=vapier@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