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
Subject: Re: [gentoo-osx] PREFIX on Cygwin
Date: Wed, 05 Jul 2006 15:12:35 -0700	[thread overview]
Message-ID: <44AC3953.3030508@spikesource.com> (raw)
In-Reply-To: <448F0EA3.8070405@spikesource.com>

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



  reply	other threads:[~2006-07-05 22:13 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
2006-06-13 18:56     ` Grobian
2006-06-13 19:14       ` Nimish Pachapurkar
2006-07-05 22:12         ` Nimish Pachapurkar [this message]
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=44AC3953.3030508@spikesource.com \
    --to=npac@spikesource.com \
    --cc=gentoo-osx@lists.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