Mailing List Archive

Hi!

Interesting to see some works along the windows way. We never tried
anything alike, but of course we would be very happy if it would work
somehow in the end.

Could you give any error messages you get? Maybe they look familiar or
does somebody here know what they mean exactly.

Regards


On 13-06-2006 11:08:56 -0700, Nimish Pachapurkar wrote:
> Hello All,
>
> I was trying to get PREFIX portage to work on Cygwin on Windows (XP). I am
> facing some issues in the process. Has anyone tried this before with Prefix
> Portage? I found that there is a project specifically for this purpose at
> http://gentoocygwin.sourceforge.net but that does not seem to support Prefix
> version of portage.
>
> Any pointers in this regard would be appreciated.
>
> Specifically today, I am facing a problem while emerging anything. I get an
> error saying that I am trying to emerge a package with a syntax error or
> corrupt ebuild file (which is definitely not the case). Also, emerge refuses to
> proceed with any dependency analysis whatsoever.
>
> Thanks,
> Nimish

--
Fabian Groffen
Gentoo for Mac OS X Project
--
gentoo-osx@gentoo.org mailing list

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".

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

3. Same error is raised when I try to run "ebuild" command on any of the
ebuilds with any option. At present, I am trying to trace through the
ebuild/emerge code to see what is going wrong. I have a feeling that
somewhere the root is getting set back to "/" or something like that.

If any of these error messages mean anything to you, please throw some
light.

Thanks,
- Nimish

Grobian wrote:
> Hi!
>
> Interesting to see some works along the windows way. We never tried
> anything alike, but of course we would be very happy if it would work
> somehow in the end.
>
> Could you give any error messages you get? Maybe they look familiar or
> does somebody here know what they mean exactly.
>
> Regards
>
>
> On 13-06-2006 11:08:56 -0700, Nimish Pachapurkar wrote:
>> Hello All,
>>
>> I was trying to get PREFIX portage to work on Cygwin on Windows (XP). I am
>> facing some issues in the process. Has anyone tried this before with Prefix
>> Portage? I found that there is a project specifically for this purpose at
>> http://gentoocygwin.sourceforge.net but that does not seem to support Prefix
>> version of portage.
>>
>> Any pointers in this regard would be appreciated.
>>
>> Specifically today, I am facing a problem while emerging anything. I get an
>> error saying that I am trying to emerge a package with a syntax error or
>> corrupt ebuild file (which is definitely not the case). Also, emerge refuses to
>> proceed with any dependency analysis whatsoever.
>>
>> Thanks,
>> Nimish
>
--
gentoo-osx@gentoo.org mailing list

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.

--
Fabian Groffen
Gentoo for Mac OS X Project
--
gentoo-osx@gentoo.org mailing list

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

Hi,

I'm wondering that cygwin has fixed the hyperthreading-related bug[1],
only occurring on Windows >= XP, not until Win2000.
Well, there are some more recent posts on the list with some patches to
the cygwin-dll, but did not really find it fixed.

Well, facing this problem, and some others which seems that M$
implements things to prevent cygwin working on newer Windows-versions,
we have switched to Interix now - planning to use portage on Interix,
with wgcc[2] as 'cross-compiler' to produce native win32 executables.

[1] http://www.cygwin.com/ml/cygwin/2004-10/msg00610.html
[2] http://sourceforge.net/projects/interix-wgcc

-- haubi

On Tue, 2006-06-13 at 20:20 +0200, Grobian wrote:
> Hi!
>
> Interesting to see some works along the windows way. We never tried
> anything alike, but of course we would be very happy if it would work
> somehow in the end.
>
> Could you give any error messages you get? Maybe they look familiar or
> does somebody here know what they mean exactly.
>
> Regards
>
>
> On 13-06-2006 11:08:56 -0700, Nimish Pachapurkar wrote:
> > Hello All,
> >
> > I was trying to get PREFIX portage to work on Cygwin on Windows (XP). I am
> > facing some issues in the process. Has anyone tried this before with Prefix
> > Portage? I found that there is a project specifically for this purpose at
> > http://gentoocygwin.sourceforge.net but that does not seem to support Prefix
> > version of portage.
> >
> > Any pointers in this regard would be appreciated.
> >
> > Specifically today, I am facing a problem while emerging anything. I get an
> > error saying that I am trying to emerge a package with a syntax error or
> > corrupt ebuild file (which is definitely not the case). Also, emerge refuses to
> > proceed with any dependency analysis whatsoever.
> >
> > Thanks,
> > Nimish
>
> --
> Fabian Groffen
> Gentoo for Mac OS X Project
--
Michael Haubenwallner SALOMON Automation GmbH
Forschung & Entwicklung A-8114 Friesach bei Graz
mailto:michael.haubenwallner@salomon.at http://www.salomon.at
No HTML/MIME please, see http://expita.com/nomime.html

--
gentoo-osx@gentoo.org mailing list

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

On 05-07-2006 15:12:35 -0700, Nimish Pachapurkar wrote:
> 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.

Please do. Can it be posted to this list (reasonable size?)

> 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?

The repo location is still an issue. I've been thinking about a git
writable mirror or something that is back propagated to the Gentoo SVN
repo. Kind of ugly all.
I don't know exactly where to get the latest sources for portage. I
hope someone else on this list can answer this (exg?).

--
Fabian Groffen
Gentoo for Mac OS X Project
--
gentoo-osx@gentoo.org mailing list

> 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.

The latest snapshot is

http://dev.gentoo.org/~kito/distfiles/portage-prefix-2.1.14.tar.bz2

Even if it is a bit old, I should have no problem in porting the changes
to svn.

--
Emanuele
--
gentoo-osx@gentoo.org mailing list

exg@gentoo.org wrote:
>> 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.
>
> The latest snapshot is
>
> http://dev.gentoo.org/~kito/distfiles/portage-prefix-2.1.14.tar.bz2
>
> Even if it is a bit old, I should have no problem in porting the changes
> to svn.
>

Thank you for the snapshot link.

I am attaching the cygwin patch here. Please let me know if there are
any comments or questions about any specific fixes.

Some notes:
1. I have disabled the install_qa_checks on Cygwin for now, since that
takes forever to complete even for very small packages.
2. Also, the unlocking for tuples almost invariably fails on Windows.
However, that does not create any trouble in most cases. I have changed
the code so that such failures are silently ignored. Otherwise, it is
very annoying to see the builds failing for no apparent reason.
3. Move cannot be performed on windows if the target file exists. I
have ignored such rename attempts.

Thanks,
- Nimish