| 1 |
Mike Frysinger <vapier@g.o> wrote on 2010/09/20 22:00:25: |
| 2 |
> |
| 3 |
> On Monday, September 20, 2010 15:00:25 Joakim Tjernlund wrote: |
| 4 |
> > I am fiddling with crossdev again and I wonder if there a way to |
| 5 |
> > pass different configure options to gcc/binutils vs. glibc? |
| 6 |
> > Doing export EXTRA_ECONF="--with-cpu=e300c2" applies |
| 7 |
> > to all and glibc bombs with subarch not supported error. |
| 8 |
> |
| 9 |
> you'd have to use per-package env manually: |
| 10 |
> /etc/portage/env/$CATEGORY/$PN |
| 11 |
> |
| 12 |
> but crossdev likes to clobber this file for you. so i guess i should extend |
| 13 |
> crossdev with --env-xxx options so people can add their own. |
| 14 |
> |
| 15 |
> > Second, there are not many PowerPC cpus in the ports section |
| 16 |
> > of glibc and not mine embedded one either. Is there any |
| 17 |
> > alternative ports pkg somewhere that supports more PowerPC |
| 18 |
> > cpus? |
| 19 |
> |
| 20 |
> we take what glibc offers via their glibc-ports package. personally, i do 0 |
| 21 |
> embedded powerpc work, so i dont know of any "alternatives" or such. |
| 22 |
|
| 23 |
OK, I was mainly after some decent mem*() functions as the ones provided |
| 24 |
usually perform badly for embedded CPUs |
| 25 |
|
| 26 |
> |
| 27 |
> if they did exist though, the only way currently to get them transparently |
| 28 |
> added would be to make a big patch out of them and then use the user patch |
| 29 |
> interface (put patches into /etc/portage/patches/$CATEGORY/$P/). |
| 30 |
|
| 31 |
hmm, maybe I could make up my own dummy ports pkg for my cpu. That way |
| 32 |
I could probably make glibc accept my cpu conf too. |
Archives