public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrew DeFaria <Andrew@DeFaria.com>
To: cygwin@cygwin.com
Subject: Re: Error when Perl calling shell scipt using Cygwin >>> c:\cygwin\bin\sh.exe: *** fatal error - couldn't allocate heap, Win32 error 487
Date: Mon, 30 May 2011 13:57:00 -0000	[thread overview]
Message-ID: <is07n3$jc4$1@dough.gmane.org> (raw)
In-Reply-To: <31733309.post@talk.nabble.com>



On 05/30/2011 06:26 AM, Gaurav Chhabra wrote:
>> I have Perl separately installed at c:\Perl. I am not sure how to run this.
>>>> This will not work.
>>>> perlrebase works only for cygwin perls, not for strawberry or
>>>> activestate perls.
> That's what I was thinking. I was sure that I am doing something wrong, and
> it must have something to do with Perl for Cygwin :) Thanks for the info!
>
>> I just copied the prelrebase script and kept it in the Cygwin's bin
>> directory. Then I had to set the 'perl' variable in prelrebase script to
>> 'perl=../../Perl/bin/perl$suff.exe' because my Cygwin is at c:\Cygwin. Now
>> when I ran the script with argument '5.6.1', I get the following error:
>>>> Do you really want to rebase your activestate perl 5.6.1?
>>>> I told you to run perlrebase, not perlrebase 5.6.1
> As you have said below that my Perl will have a different forking mechanism,
> I will/should not go for perlrebase.
>
>> --------------------------------------------------
>> user@machine: /cygdrive/c/cygwin/bin
>> $ ./perlrebase.sh 5.6.1
>> no archlib found for ../../Perl/bin/perl5.6.1.exe
>> --------------------------------------------------
>> I am not sure what this archlib is? I could not find it defined anywhere
>> in
>> the perlrebase script. Can you please help me with this?
>>>> See perl -V:archlib
> Thanks!
>
> My 5.6.1 *cygwin* perl has:
> $ perl5.6.1 -V:archlib
> archlib='/usr/lib/perl5/5.6.1/cygwin-debug';
>
> My ActiveState perl has
>> perl -V:archlib
> archlib='C:\Perl\lib';
>
>>>> But this should not be rebased by cygwin as it has a different fork
> strategy than cygwin.
>
> So now the question is what should I do to resolve the issue I am facing?
> Since we use a separate Perl (Active State), your perlrbase will not work. I
> am stuck. :( Any suggestions?
>
>
> Regards,
> Gaurav
How about contacting ActiveState, the makers of the Perl you are using?

Either that or ditch the ActiveState and use Cygwin's Perl.
-- 
Andrew DeFaria <http://defaria.com>
What's another word for synonym?


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

  reply	other threads:[~2011-05-30 13:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27  6:24 Gaurav Chhabra
2011-05-30  9:02 ` Reini Urban
2011-05-30  9:48   ` Gaurav Chhabra
2011-05-30 12:13     ` Reini Urban
2011-05-30 13:26       ` Gaurav Chhabra
2011-05-30 13:57         ` Andrew DeFaria [this message]
2011-07-15 14:02           ` Gaurav Chhabra
2011-07-15 14:04             ` Gaurav Chhabra
2011-07-18 16:30               ` Reini Urban
2011-07-20 14:04                 ` Gaurav Chhabra

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='is07n3$jc4$1@dough.gmane.org' \
    --to=andrew@defaria.com \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).