public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
Cc: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] e300c3/c3 cpu support for glibc ports
Date: Mon, 27 Sep 2010 22:33:38 -0400	[thread overview]
Message-ID: <201009272233.39014.vapier@gentoo.org> (raw)
In-Reply-To: <OFDBADDBE0.793E50EA-ONC12577AB.00518BB5-C12577AB.0051FD35@transmode.se>

[-- Attachment #1: Type: Text/Plain, Size: 628 bytes --]

On Monday, September 27, 2010 10:55:32 Joakim Tjernlund wrote:
> Mike Frysinger wrote on 2010/09/25 08:07:15:
> > On Friday, September 24, 2010 12:22:19 Joakim Tjernlund wrote:
> > > This is what I came up with to make glibc support
> > > --with-cpu=e300c2
> > 
> > mail it to libc-ports ?
> 
> Upstream doesn't want it as it only adds --with-cpu= syntax
> and don't change anything else.
> That implies crossdev needs to grow support different configure options
> for glibc/gcc/binutils etc.
> I guess that is the normal way non gentoo devs builds toolchains?

portage already has per-package env support
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2010-09-28  3:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-24 16:22 [gentoo-embedded] e300c3/c3 cpu support for glibc ports Joakim Tjernlund
2010-09-25  6:07 ` Mike Frysinger
2010-09-25 17:17   ` Joakim Tjernlund
2010-09-27 14:55   ` Joakim Tjernlund
2010-09-28  2:33     ` Mike Frysinger [this message]
2010-09-28  6:55       ` Joakim Tjernlund
2010-09-28  8:16         ` Mike Frysinger
2010-09-28 13:00           ` Joakim Tjernlund

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=201009272233.39014.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=gentoo-embedded@lists.gentoo.org \
    --cc=joakim.tjernlund@transmode.se \
    /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