Nilson Santos Figueiredo Junior wrote:
OK, don't mean to sound like a whiner here, and I haven't spent any time
investigating the various GCC packages, but it's making me laugh that
it's been suggested I download a C++ development package just so I can
get my perl modules to install.
Nilson Santos Figueiredo Junior wrote:
On 6/30/06, Hugh Lampert [EMAIL PROTECTED] wrote:
The hassle is that we are a Windows shop and my boss only cares about
results. To roll out an .ASP application is only a matter of using the
resources that are already installed in the development
Nilson Santos Figueiredo Junior wrote:
The problem is that I never managed to get Apache to run mod_perl
properly without crashing. But maybe that's just me, since I've seen
other people reporting the opposite. But it works fine enough for my
current purposes under Apache::Registry.
We've
On 6/30/06, Christopher H. Laco [EMAIL PROTECTED] wrote:
Don't do that. Bad things will happen. Always compiled your modules with
the same compiler used for the perl install itself on Windows. To that
point, you could compile perl in .NET, then do the modules that way too.
FUD.
VS.NET 2003
On 6/30/06, Matt S Trout [EMAIL PROTECTED] wrote:
I think that's the point - that AS has switched to gcc and it's *generally*
preferable to use the same compiler as your perl binary was built with.
There's nothing in the release notes indicating that they've done this
(they've recently switched
