1 |
> |
2 |
> > |
3 |
> > |
4 |
> > $ CBUILD=i586-pc-winnt PREFIX=/opt/gentoo.winnt emerge -v parity |
5 |
> > |
6 |
|
7 |
Small update: no CHOST/CBUILD stuff has to be set on the command line. It is enough to set EPREFIX only, the rest is done from the |
8 |
profiles. |
9 |
|
10 |
Cheers, Markus |
11 |
|
12 |
> |
13 |
> I have one big problem left, where I need some help thinking about it: inside the windows prefix I can |
14 |
> only emerge some special |
15 |
> stuff (so no coreutils or such things), so I really have a dependency to the interix prefix where all |
16 |
> the command line stuff needs |
17 |
> to be taken from, that I can't build for winnt. |
18 |
> |
19 |
> But how can I deal with such dependencies in ebuilds? If, for example, some package had a dependency |
20 |
> on libtool, which right now |
21 |
> should be taken from the interix prefix, not the winnt one, then how does portage realize, that |
22 |
> libtool is installed in the other |
23 |
> prefix? I could use package.provided , but that would require some manual work... I would prefer an |
24 |
> automated solution. |
25 |
> |
26 |
> The next problem: if the winnt prefix would be aware of packages in the interix prefix, then what |
27 |
> about packages providing |
28 |
> libraries, which I may need to link? This won't work, if the libs aren't emerged in the winnt prefix |
29 |
> again, since otherwise they'd |
30 |
> have the wrong format... |
31 |
> |
32 |
> Another Problem: lets stick with libtool. It provides some stuff, that belongs to the interix prefix, |
33 |
> since it has nothing to do |
34 |
> with winnt, but libtool also provides libltdl, which would be required as winnt build if it is needed |
35 |
> by some package... how could I |
36 |
> differentiate if the DEPEND means the libtool facilities used while bootstrapping, or the library? |
37 |
> |
38 |
> Any thoughts? Cheers, Markus |
39 |
> |
40 |
> -- |
41 |
> gentoo-alt@l.g.o mailing list |
42 |
|
43 |
|
44 |
-- |
45 |
gentoo-alt@l.g.o mailing list |