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