Len Jaffe wrote:
Error: PROPFIND request failed on
'/browser/trunk/examples/CatalystAdvent'
The /browser/ URL is only for web access, try to use
http://dev.catalyst.perl.org/repos/Catalyst/trunk/examples/CatalystAdvent/
for checkout.
I think maybe getting out of bed was a bad idea today
Len Jaffe wrote:
I'm trying to gram the advent calendar source code,
and when I try it, via tortoiseSVN or SmartSVN, I get
a PROPFIND failed error:
Error: PROPFIND request failed on
'/browser/trunk/examples/CatalystAdvent'
Error: PROPFIND of
'/browser/trunk/examples/CatalystAdvent': 500
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.
Hugh Lampert wrote:
Carl Franks wrote:
You may want to look into Vanilla / Strawberry perl as an alternative
to ActivePerl.
It includes the mingw (gcc) compiler and nmake, and the perl included
is compiled from scratch with mingw, rather than ms compilers.
Thanks, I will look into this for
On Fri, Jun 30, 2006 at 05:01:19AM -0700, Len Jaffe wrote:
I need some advice on the best place to put static
HTML pages, in the context of a web site that will
have some static content, and some catalyst driven
content.
Furthermore, I want to be able to run under the devel
server, and
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
no ideas on this one?
On 6/28/06, Craig Talbert [EMAIL PROTECTED] wrote:
I saw this questions asked in an archived discussion on the list from
about a year ago, I just wanted to check and see if I was doing
something wrong or if there's still known issues with installing
Catalyst on cygwin?
Craig Talbert wrote:
I saw this questions asked in an archived discussion on the list from
about a year ago, I just wanted to check and see if I was doing
something wrong or if there's still known issues with installing
Catalyst on cygwin?
Install Catalyst first, say no to
11 matches
Mail list logo
