public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <joakim.tjernlund@transmode.se>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] e300c3/c3 cpu support for glibc ports
Date: Tue, 28 Sep 2010 15:00:46 +0200	[thread overview]
Message-ID: <OF9DB37448.AA89FA13-ONC12577AC.002E916C-C12577AC.00477B5E@transmode.se> (raw)
In-Reply-To: <201009280416.59462.vapier@gentoo.org>

Mike Frysinger <vapier@gentoo.org> wrote on 2010/09/28 10:16:58:
>
> On Tuesday, September 28, 2010 02:55:13 Joakim Tjernlund wrote:
> > Mike Frysinger <vapier@gentoo.org> wrote on 2010/09/28 04:33:38:
> > > 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
> >
> > But you said earlier:
> >   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.
> >
> > So currently there is no way to pass in different configure options?
> >
> > I would be happy some extra env var like
> >  CROSS_CC_CONF
> >  CROSS_LIBC_CONF
> > that would be appended to EXTRA_ECONF
> >
> > configure options that gets passed directly to crossdev
> > works too.
>
> yes, per-package env vars arent working optimal today, but my point is that
> that is the only thing i'm going to support.  it isnt worth the hassle of
> designing custom variables & options which ultimately boil down to
> EXTRA_ECONF.  we have EXTRA_ECONF already which means it is left up to the
> user to set them accordingly.

Yes, it is a pity EXTRA_ECONF doesn't work here.

BTW, is there a way to tell crossdev/gcc not to build/install powerpc64-*
tools? I have no need for them and they just get in my way.

          Jocke.

         Jocke




      reply	other threads:[~2010-09-28 13:11 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
2010-09-28  6:55       ` Joakim Tjernlund
2010-09-28  8:16         ` Mike Frysinger
2010-09-28 13:00           ` Joakim Tjernlund [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=OF9DB37448.AA89FA13-ONC12577AC.002E916C-C12577AC.00477B5E@transmode.se \
    --to=joakim.tjernlund@transmode.se \
    --cc=gentoo-embedded@lists.gentoo.org \
    --cc=vapier@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