| 1 |
On Thursday, January 30, 2014 21:49:24 Joakim Tjernlund wrote: |
| 2 |
> Mike Frysinger <vapier@g.o> wrote on 2014/01/30 20:12:54: |
| 3 |
> > On Wednesday, January 29, 2014 17:58:46 Joakim Tjernlund wrote: |
| 4 |
> > > As both ARCH and ELIBC are PROFILE_ONLY vars one cannot |
| 5 |
> > > define these in make.conf. |
| 6 |
> > > Move these to etc/portage/profile/make.defaults which is part |
| 7 |
> > > of the profile. |
| 8 |
> > |
| 9 |
> > i've been thinking we should stop using the embedded profile entirely. |
| 10 |
> > instead, scan profiles.desc and pick the first one there that matches |
| 11 |
> > ARCH. |
| 12 |
> |
| 13 |
> That would pull in a lot of pkgs into the embedded space, would it not? |
| 14 |
|
| 15 |
it would to a degree. i really really don't want crossdev to get into the |
| 16 |
business of generating profiles. |
| 17 |
|
| 18 |
the other aspect is that the embedded profile does not import all the arch- |
| 19 |
specific details that profiles/arch/$ARCH/ contain (which is why crossdev has |
| 20 |
this ARCH hack in the first place). or all the profiles/default/linux/ stuff |
| 21 |
(for linux targets). |
| 22 |
|
| 23 |
what CTARGET do you normally use ? |
| 24 |
-mike |
Archives