Re: [gentoo-embedded] e300c3/c3 cpu support for glibc ports

[Joakim Tjernlund <joakim.tjernlund@transmode.se>]

Mike Frysinger <vapier@gentoo.org> wrote on 2010/09/28 04:33:38:

> From: Mike Frysinger <vapier@gentoo.org>
> To: Joakim Tjernlund <joakim.tjernlund@transmode.se>
> Cc: gentoo-embedded@lists.gentoo.org
> Date: 2010/09/28 05:00
> Subject: Re: [gentoo-embedded] e300c3/c3 cpu support for glibc ports
>
> 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.

 Jocke