Date: Tue, 14 Apr 2009 12:20:05 +0200
From: Michael Schroeder <mls@suse.de>
To: "Patrick R. Michaud" <pmichaud@pobox.com>
Cc: Reini Urban <rurban@x-ray.at>, parrot-dev@lists.parrot.org,
   cygwin@cygwin.com
Subject: Re: [PATCH] rakudo Re: Parrot packaging problems
Message-ID: <20090414102005.GA30913@suse.de>
References: <20090408101541.GA6404@suse.de> <49DCEC65.4000400@x-ray.at> <20090409102012.GD1506@suse.de> <49DE45E6.5030508@x-ray.at> <20090409212923.GA10858@pmichaud.com> <6910a60904100209l54b238dbuf56b10251364fc99@mail.gmail.com> <20090410161203.GA6883@pmichaud.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090410161203.GA6883@pmichaud.com>
User-Agent: Mutt/1.5.9i
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Fri, Apr 10, 2009 at 11:12:03AM -0500, Patrick R. Michaud wrote:
> For some reason that doesn't sound quite right to me.  When converting
> rakudo to an executable, the pbc2exe we use should already know 
> if it's being run using an installed parrot or some other parrot 
> (because pbc2exe is itself a parrot application).  So we shouldn't
> have to pass an explicit flag to it -- we should simply get the
> correct perl6 executable based on whatever pbc2exe was run.

Yes, I think the installed pbc2exe should always use the
"installed" config. If you're wondering what the difference between
the two configs is, it's just the "prefix" variable. "prefix" is
set to "/usr" in the installed config, and to the content of
build_dir for the uninstalled one.

Cheers,
  Michael.

-- 
Michael Schroeder                                   mls@suse.de
SUSE LINUX Products GmbH, GF Markus Rex, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/