Re: Perl executable problem...

In that case, Install cygwin (idk if you'll have to select gcc or it's default - either way that's the easiest way I know of to get it on windows). On Mon, Nov 16, 2015 at 3:52 AM, Rui Fernandes wrote: > Good morning Kevin, > > I've installed par as you said. It seeme to

Re: Perl executable problem...

Good morning Kevin, I've installed par as you said. It seeme to run, but it asks for setup the gcc environment... I'm a little bit lost on how to do it... Regards, Miguel On Sun, Nov 15, 2015 at 10:59 PM, Kevin Walzer wrote: > On 11/15/15 5:27 PM, ekimduna...@gmail.com

Re: Perl executable problem...

Hi Brandon, Actually I'm able to run the script from the DOS prompt with "perl script.pl". It might be a permissions problem in Windows 7... But, can you please tell me how to compile the .pl script to .exe in windows, with Strawberry? Which command should I use? I'm not familiar with this

Re: Perl executable problem...

Miguel, This might help http://stackoverflow.com/questions/2948405/how-to-compile-a-perl-script-pl-to-a-windows-executable-exe-with-strawberr Sent from my iPhone. > On Nov 15, 2015, at 3:01 PM, Rui Fernandes wrote: > > Hi Brandon, > > Actually I'm able to run the

Re: Perl executable problem...

On 11/15/15 5:27 PM, ekimduna...@gmail.com wrote: Miguel, This might help http://stackoverflow.com/questions/2948405/how-to-compile-a-perl-script-pl-to-a-windows-executable-exe-with-strawberr PAR/pp, referenced in that thread, is fine if you simply need to distribute a script to end users in

Re: Perl executable problem...

I've never used active state, you might try strawberry perl if you are on windows. --Sam On 11/12/2015 07:53 AM, Rui Fernandes wrote: /Hi, I'm having a problem compiling a perl script to run in my windows 7 32 bits environment. It compiles with Perl Dev Kit from active state, but when I run

Re: Perl executable problem...

Rui: On Thu, Nov 12, 2015 at 8:53 AM, Rui Fernandes wrote: > Hi, Hello: > I'm having a problem compiling a perl script to run in my windows 7 32 bits > environment. It compiles with Perl Dev Kit from active state, but when I run > it (in the command line of dos) it just

Re: Perl executable problem...

Greetings! Could you give us the text of your script, and maybe a screens hot of you running it? One guess is that you aren't providing the script name as expected, so perl is waiting for input. On Nov 12, 2015 08:54, "Rui Fernandes" wrote: > > > > > > > *Hi,I'm having a

Re: Perl executable problem...

Hi Brock, Nice to meet you :) I've tryed the simplier script ever: #!/usr/bin/perl print "Hello World!"; exit; I've tryed to include Class::Load::PP, and other recommended modules also. The script just...frezees. Even if I type something, nothing appears. I didn't defined arguments for input

Re: Perl executable

On Wed, Apr 28, 2010 at 4:27 AM, Vaishak S vaishak...@gmail.com wrote: The reason why I am putting this to executable is the DBI is having the password in the connection string, which we don't want to share with any of other users who log to the system and to protect the code. We are still

Why not to use env (was Re: Perl executable pathname needs to be hardwired?)

Chris == Chris Devers [EMAIL PROTECTED] writes: Chris My understanding is that the Python idiom is to avoid putting the full Chris path, in favor of something like Chris #!/usr/bin/env python This won't work if env is not in /usr/bin (like say, /bin/env). Chris #!env python This

Re: Perl executable pathname needs to be hardwired?

Adriano == Adriano Ferreira [EMAIL PROTECTED] writes: Adriano Ok. I will try to be less lazy. What I was trying to workaround is to Adriano place perl binaries at a place available to my user, using a Adriano distribution which was supposed to be installed by 'root' (which I am Adriano not). The

Re: Why not to use env (was Re: Perl executable pathname needs to be hardwired?)

On Sat, 3 Dec 2005, Randal L. Schwartz wrote: Chris == Chris Devers [EMAIL PROTECTED] writes: Chris My understanding is that the Python idiom is to avoid putting the full Chris path, in favor of something like Chris #!/usr/bin/env python This won't work if env is not in /usr/bin

Re: Perl executable pathname needs to be hardwired?

On Fri, 2 Dec 2005, Adriano Ferreira wrote: What's the rationale for hardwiring the Perl executable pathname into the Perl interpreter? It is some oddity to guarantee Perl can find its library via a relative path? Is it a safety thing? Yeah, basically. Historically, Unix users could depend

Re: Perl executable pathname needs to be hardwired?

On 12/2/05, Chris Devers [EMAIL PROTECTED] wrote: Historically, Unix users could depend on a copy of Perl in /usr/bin from their vendor, and maybe a custom-installed one somewhere like /opt/bin or /usr/local/bin. With that in mind, using one of those paths usually would do something useful.

Re: Perl executable pathname needs to be hardwired?

On Fri, 2 Dec 2005, Adriano Ferreira wrote: I see your point, Chris. What I was thinking about was the trouble to realocate the interpreter if you have a perl binary instead of compiling it from the source. If you use a perl compiled to be in /usr/local/bin in a different path like

Re: Perl executable pathname needs to be hardwired?

On 12/2/05, Chris Devers [EMAIL PROTECTED] wrote: But anyway, yeah. In general, you can't depend on things working consistently if you just start randomly moving around compiled programs and libraries. Sometimes it won't matter, but other times, the results just won't be predictable. Ok. I

Re: Perl executable pathname needs to be hardwired?

On 12/2/05, Chris Devers [EMAIL PROTECTED] wrote: My understanding is that the Python idiom is to avoid putting the full path, in favor of something like #!/usr/bin/env python #!env python on grounds that Python may not be quite as common, but you could depend on the `env` command

Re: Perl executable pathname needs to be hardwired?

Adriano Ferreira wrote: On 12/2/05, Chris Devers [EMAIL PROTECTED] wrote: My understanding is that the Python idiom is to avoid putting the full path, in favor of something like #!/usr/bin/env python #!env python on grounds that Python may not be quite as common, but you could depend on

RE: Perl Executable

Why not just do it from your shell? 'path/to/perl scriptname' works quite nicely, so why not just make an alias for the path to perl? -Original Message- From: Jeffery Malloch [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 10, 2004 11:08 AM To: '[EMAIL PROTECTED]' Subject: Perl

Re: perl executable ?

Not sure about how to do it via perlcc, but you can alternatively try: http://www.perl2exe.com/ On Fri, 2003-02-14 at 08:08, [EMAIL PROTECTED] wrote: hi all, if i want to make a standalone executable of my perl program how do i do that with perlcc ??? or any other way to generate

Re: perl executable ?

From: [EMAIL PROTECTED] if i want to make a standalone executable of my perl program how do i do that with perlcc ??? or any other way to generate machinecoded executable? kindly enlighten me -- regards, KM If you run perldoc perlcc you will get the documentation. Including this

Re: perl executable ?

From: [EMAIL PROTECTED] if i want to make a standalone executable of my perl program how do i do that with perlcc ??? or any other way to generate machinecoded executable? kindly enlighten me -- regards, KM If your standalone is for Win32, then this might do the trick. I used to use it with

Re: perl executable

On Wednesday, April 3, 2002, at 12:27 , Mayank Ahuja wrote: [..] Is there a way in which the whole code can be converged to one executble file so that we do not need to ship all the files to the user? [..] May I recommend that it is often easier to deliver one tarball of many things - with