Problem found.
I put the Visual C++ paths in my Environment variables. Thus the compiler
was visible even in my normal Windows prompt. I needed to hide my compiler!
----- Original Message -----
From: "Alan Stewart" <astewart1@xxxxxxx>
To: "the.noonings" <the.noonings@xxxxxxxxxxx>; <par@xxxxxxxx>
Sent: Monday, July 05, 2004 1:10 PM
Subject: Re: Trouble installing PAR 0.85 on Windows XP
> On 5 Jul 2004 at 12:08, the.noonings wrote:
>
> > Actually, I am not trying to compile at all. I am in the normal windows
> > command prompt.
> >
> > I believe the directions to install are
> > . Download the PAR.tar.gz file to some temp directory
> > . Unzip and untar the PAR.tar.gz file
> > . Download the prebuilt binary, in this case
> > PAR-0.85-MSWin32-x86-multi-thread-5.8.4.par
> > into the same directory as the Makefile.PL file.
> > . unzip the prebuilt binary
> > . perl Makefile.PL
> > . nmake
> > . nmake test
> > . nmake install
> >
> > It was my understanding that nmake would not try to recompile from
scratch
> > if the prebuilt binary was present.
>
> According to the readme, regarding pre-built binaries:
>
> "This process is completely automatic -- no
> actions are required on your part."
>
> because the binary should download and unzip automatically, if no C
compiler is
> present. If you download manually, the unzip of the binary is still
automatic.
>
> The readme doesn't really say that having a C compiler overrides having
the pre-built.
> We probably need an install query if both are present. Autrijus??
>
> Alan Stewart
>
|
