perl-5.6.1-2 bug

perl-5.6.1-2 bug

[Ñãzã®78]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 715 bytes --]

Greetings.

Hi there. I've just found this on perl-5.6.1-2.

-- begin test.pl --
#!/usr/bin/perl

print "Hello, World\n\n";

exit;
-- end test.pl --

perlcc -o test.exe test.pl

When try'in to execute test.exe, I got this:

Error Starting the Program>>The TEST.EXE is linked to missing export
LIBPERL5_6_1.DLL:Perl_Gcurinterp_ptr.

Hope this helps.

Thank you.

Regards,
Ñãzã®78 @ nazar@ebizmalay.com
eBizMalay.Com @ http://www.ebizmalay.com
Bringing To You eBiz Solutions Of Tomorrow



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: perl-5.6.1-2 bug

[Gerrit P. Haase]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

Ñãzã®78 schrieb am 2001-08-26, 13:14:
>Hi there. I've just found this on perl-5.6.1-2.
>
>-- begin test.pl --
>#!/usr/bin/perl
>
>print "Hello, World\n\n";
>
>exit;
>-- end test.pl --
>
>perlcc -o test.exe test.pl
>
>When try'in to execute test.exe, I got this:
>
>Error Starting the Program>>The TEST.EXE is linked to missing export
>LIBPERL5_6_1.DLL:Perl_Gcurinterp_ptr.
>
>Hope this helps.

Hi,

You lucky one, how does this trick work?

For me it stackdumps with exactely the same script:

$ ./test
      0 [main] test 292 open_stackdumpfile: Dumping stack trace to test.exe.stackdump
Segmentation fault (core dumped)

perlcc 'should' be able to build standalone executables, but
it is the first time i saw now, that it is really able to do so.
I will have to dig into a little deeper.
Have you some special environment variables set?

Gerrit


--
=^..^=

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: perl-5.6.1-2 bug

[Ñãzã®78]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2452 bytes --]

Hmm...

I only face stackdump results when compiling or running under 10% system
resources and not forgetting my own script errors. That was with
perl-5.6.1-1trial.

>>You lucky one, how does this trick work?
>>For me it stackdumps with exactely the same script:

It's suppose to work with that simple hello world script. Have you tried
perlcc'in on a unix perl? The only failures from my experience was indigo
and active perl. Or a small debugging could help "perl -MO=C,-ofoo.c
foo.pl", open up the c file to find the faults and finally "gcc foo.c
[args+flags+opts]".

>>perlcc 'should' be able to build standalone executables, but
>>it is the first time i saw now, that it is really able to do so.

Even though, it's still links to "CYGWIN1.DLL" and"LIBPERL5_6_1.DLL". Don't
leave your box without them :)

>>Have you some special environment variables set?

Nothing special about my envs and vars. May be almost similar to yours with
just a couple of "CPLUS_INCLUDE_PATH" and "C_INCLUDE_PATH" as addition.

Thank you.

Regards,
Ñãzã®78 @ nazar@ebizmalay.com
eBizMalay.Com @ http://www.ebizmalay.com
Bringing To You eBiz Solutions Of Tomorrow

----- Original Message -----
From: "Gerrit P. Haase" <gp@familiehaase.de>
To: "XXzXX78" <nazar@ebizmalay.com>
Cc: <cygwin@cygwin.com>
Sent: Sunday, August 26, 2001 6:51 PM
Subject: Re: perl-5.6.1-2 bug


Ñãzã®78 schrieb am 2001-08-26, 13:14:
>Hi there. I've just found this on perl-5.6.1-2.
>
>-- begin test.pl --
>#!/usr/bin/perl
>
>print "Hello, World\n\n";
>
>exit;
>-- end test.pl --
>
>perlcc -o test.exe test.pl
>
>When try'in to execute test.exe, I got this:
>
>Error Starting the Program>>The TEST.EXE is linked to missing export
>LIBPERL5_6_1.DLL:Perl_Gcurinterp_ptr.
>
>Hope this helps.

Hi,

You lucky one, how does this trick work?

For me it stackdumps with exactely the same script:

$ ./test
      0 [main] test 292 open_stackdumpfile: Dumping stack trace to
test.exe.stackdump
Segmentation fault (core dumped)

perlcc 'should' be able to build standalone executables, but
it is the first time i saw now, that it is really able to do so.
I will have to dig into a little deeper.
Have you some special environment variables set?

Gerrit


--
=^..^=



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: perl-5.6.1-2 bug

[Gerrit P. Haase]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]

> Ñãzã®78 schrieb am 2001-08-27 15:58:

>Hmm...
>
>I only face stackdump results when compiling or running under 10% system
>resources and not forgetting my own script errors. That was with
>perl-5.6.1-1trial.

That is interesting, all my harddisks have less than 10% free space, but
i have lots of Ram, about 400MB.
At my workstation it is the same problem. More harddisk space here, but
less Ram.

>>>You lucky one, how does this trick work?
>>>For me it stackdumps with exactely the same script:
>
>It's suppose to work with that simple hello world script. Have you tried
>perlcc'in on a unix perl? The only failures from my experience was indigo
>and active perl. Or a small debugging could help "perl -MO=C,-ofoo.c
>foo.pl", open up the c file to find the faults and finally "gcc foo.c
>[args+flags+opts]".

Unfortunately i have no access to a unix box, want to setup a linux box
as router the next time.

>>>perlcc 'should' be able to build standalone executables, but
>>>it is the first time i saw now, that it is really able to do so.
>
>Even though, it's still links to "CYGWIN1.DLL" and"LIBPERL5_6_1.DLL". Don't
>leave your box without them :)
>
>>>Have you some special environment variables set?
>
>Nothing special about my envs and vars. May be almost similar to yours with just
>a couple of "CPLUS_INCLUDE_PATH" and "C_INCLUDE_PATH" as addition.

Thank you,

I will try harder;)

Gerrit


-- 
gerrit.haase@convey.de

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/