public inbox for gentoo-osx@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nimish Pachapurkar <npac@spikesource.com>
To: gentoo-osx@lists.gentoo.org, patrick@gentoo.org
Subject: Re: [gentoo-osx] PREFIX on Cygwin
Date: Tue, 13 Jun 2006 11:47:35 -0700	[thread overview]
Message-ID: <448F0847.4010403@spikesource.com> (raw)
In-Reply-To: <20060613182014.GY24221@gentoo.org>

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



  reply	other threads:[~2006-06-13 18:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-13 18:08 [gentoo-osx] PREFIX on Cygwin Nimish Pachapurkar
2006-06-13 18:20 ` Grobian
2006-06-13 18:47   ` Nimish Pachapurkar [this message]
2006-06-13 18:56     ` Grobian
2006-06-13 19:14       ` Nimish Pachapurkar
2006-07-05 22:12         ` Nimish Pachapurkar
2006-07-07  8:47           ` Grobian
2006-07-11 22:19           ` exg
2006-07-22  0:08             ` Nimish Pachapurkar
2006-06-14  8:15   ` Michael Haubenwallner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=448F0847.4010403@spikesource.com \
    --to=npac@spikesource.com \
    --cc=gentoo-osx@lists.gentoo.org \
    --cc=patrick@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox