Sep 20, 2010, 3:39 PM
Post #4 of 8
(3014 views)
Permalink
On Monday, September 20, 2010 17:08:56 Joakim Tjernlund wrote:
> Mike Frysinger wrote on 2010/09/20 22:00:25:
> > 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.
>
> OK, I was mainly after some decent mem*() functions as the ones provided
> usually perform badly for embedded CPUs
>
> > 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/).
>
> hmm, maybe I could make up my own dummy ports pkg for my cpu. That way
> I could probably make glibc accept my cpu conf too.
drepper already voiced his opinion -- these embedded cpu optimizations werent
going to be added to the main glibc tree. but he has no problem with them
being "dumped" into the glibc-ports tree and because of the way things are
structured, that should work for you.
so if you have some per-cpu trees to overlay, e-mail them to the glibc-ports
list so they can get merged.
-mike