Cezary Sliwa wrote:
> I tried to build Lapack 3.1.1 using cygwin. Compilation works fine, but
> testing reports failures.
I often build lapack 3.1.1 with G77, GFortran and G95, and I do not
observe any failure in testing.
To build with G77 (3.4.4-3) I simply copy make.inc.example to make.inc an
On Thu, Aug 02, 2007 at 12:46:16AM +0200, Cezary Sliwa wrote:
>
> Hello,
>
> I tried to build Lapack 3.1.1 using cygwin. Compilation works fine, but
> testing reports failures. The g77 flags were -O3 -funroll-all-loops.
>
> For gcc 3.3.3 failures are reported by CEV, CVX, CGV, DGV, SGV, ZGV.
>
On Tuesday 01 April 2003 19:04, Underwood, Jonathan wrote:
> Hi
>
> Apologies if this is a little off topic.
Probably more than a little. Failing to follow instructions for non-cygwin
applications is likely to make you a target for such accusations.
>However i run into trouble
> when compiling
Erin Catto wrote:
> That worked. Is it usually necessary to modifiy make
> files for Cygwin?
Only when they haven't been written carefully to begin with.
> Are there any other common problems?
Silly question - of course there aren't one or two problems that nearly
everybody runs into. If there w
That worked. Is it usually necessary to modifiy make
files for Cygwin? Are there any other common problems?
Thanks,
Erin
--- Max Bowsher <[EMAIL PROTECTED]> wrote:
> Short answer: Add ".PHONY: install" to the makefile
>
> Long answer: make sees the INSTALL directory, and
> concludes that it is
Erin Catto wrote:
> I'm having trouble building LAPACK. I downloaded
> lapack.tgz from www.netlib.org/lapack. I'm using
> make.inc.LINUX for make.inc. I type
>
> make install
>
> and make says that install is up to date but it is
> not! I have done the same operation on Linux and it
> works.
>
> He
6 matches
Mail list logo