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