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