| 1 |
Okay, I have Portage working reasonably well on Cygwin now. The changes |
| 2 |
I made mostly involve fixing places where root has been hard-coded to |
| 3 |
"/". There are a couple of other fixes also. I would like to submit the |
| 4 |
patch. |
| 5 |
|
| 6 |
Where can I find a current version of Portage so that I can create a |
| 7 |
patch against it? Also, has the location for hosting the prefix tree |
| 8 |
already decided? |
| 9 |
|
| 10 |
Thanks, |
| 11 |
- Nimish |
| 12 |
|
| 13 |
Nimish Pachapurkar wrote: |
| 14 |
> Grobian wrote: |
| 15 |
>> On 13-06-2006 11:47:35 -0700, Nimish Pachapurkar wrote: |
| 16 |
>>> Thanks for offering help. Here are some of my problems: |
| 17 |
>>> |
| 18 |
>>> 1. First of all under cygwin, any path that has two slashes at the |
| 19 |
>>> beginning is treated as a network path. So the seemingly harmless |
| 20 |
>>> "root + portage_consts.EPREFIX" thingy fails with error message "No |
| 21 |
>>> such hostname or network path: //opt/cyg-prefix". I worked around that |
| 22 |
>>> by changing root from "/" to "/cygdrive/c/cygwin_root". |
| 23 |
>> |
| 24 |
>> I think that workaround is reasonable. However double slashes should |
| 25 |
>> have been tackled already sometime... ? Anyone know anything about |
| 26 |
>> that? |
| 27 |
>> |
| 28 |
>>> 2. Secondly, emerge is not able to generate dependency cache for the |
| 29 |
>>> system. I have two overlays in my tree and all I can see under |
| 30 |
>>> var/cache/edb is those two empty directories (plus the normal base |
| 31 |
>>> portage one). When I run emerge with --debug and --regen options, I |
| 32 |
>>> get this error for each ebuild file in the tree: |
| 33 |
>>> aug_get(): (0) Error in sys-devel/gcc-config-1.3.12-r4.ebuild (1) |
| 34 |
>>> Check for syntax error or corruption in the ebuild |
| 35 |
>> |
| 36 |
>> What trees do you use? I'm not entirely sure, but I think this error |
| 37 |
>> can mean that you don't have EAPI="prefix" in your ebuild. But I may |
| 38 |
>> be very well mistaken. I've seen the error myself before, that's for |
| 39 |
>> sure. |
| 40 |
>> |
| 41 |
> |
| 42 |
> The ebuild tree is one I have been building on Linux for quiet some time |
| 43 |
> now. And it does have EAPI set to prefix for all ebuilds (at lease the |
| 44 |
> ones that are supposed to build). |
| 45 |
> |
| 46 |
> - Nimish |
| 47 |
-- |
| 48 |
gentoo-osx@g.o mailing list |
Archives