Re: Windows 8

[Sergei Steshenko]

--- On Wed, 10/31/12, Nicholas Jankowski <address@hidden> wrote:

From: Nicholas Jankowski <address@hidden>
Subject: Re: Windows 8
To: "Earl Ebert" <address@hidden>
Cc: "Octave users list" <address@hidden>
Date: Wednesday, October 31, 2012, 10:52 AM

On Tue, Oct 30, 2012 at 10:13 PM, cmoibenlepro <address@hidden> wrote:


Jordi Gutiérrez Hermoso-2 wrote

> It's likely a problem with the BLAS library, which is very tricky to

> compile. Someone would need to recompile it for Windows 8.



I tried to uninstall Octave, and reinstall it using "Generic" parameter

instead of OpenBLAS, but the issue remains.









--

View this message in context: 
http://octave.1599824.n4.nabble.com/Windows-8-tp4645911p4645938.html

Sent from the Octave - General mailing list archive at Nabble.com.

_______________________________________________

Help-octave mailing list

address@hidden

https://mailman.cae.wisc.edu/listinfo/help-octave


Earl, 
Since it's windows, is it safe to assume you weren't compiling from source and 
were using one of the pre-compiled Octave Forge versions? Which one, there are 
"MinGW" and "Visual Studio" versions of Octave 3.6.2.  The MinGW version isn't 
actually an installer, you just unzip (well, un 7Z) to an Octave folder. If 
your problem was with the Visual Studio version, does the MinGW version work?



Also, I've never installed the Visual Studio version, but the MinGW version has 
a readme.txt describing a number of options that can be set for libblas.dll .  
Would any of these changes make a difference under Win8?




Nick J.



-----Inline Attachment Follows-----

_______________________________________________
Help-octave mailing list
address@hidden
https://mailman.cae.wisc.edu/listinfo/help-octave

Again, I am not a Windows guy, but once I tried to compile something for 
Windows using cross-compilation toolchain.

I vaguely remember that Windows console programs need some special 
treatment/setting. Maybe in Windows 8 the setting/treatment is different - I 
was trying to address non-seeing of prompt, and prompt is output to stdout, and 
Windows GUI application most likely have no idea what stdout is.

On crash on whatever error - error messages are output to stderr, so this can 
be yet another time be console application issues. OTOH, errors might involve 
exceptions, and they are related to runtime environment.

I think MSVC builds require certain runtime DLLs to be installed.

I would also try Strawberry Perl (which has nothing to do with Octave) : 
http://strawberryperl.com/ -> http://strawberryperl.com/releases.html , and I 
would try the portable one - it doesn't require traditional Windows 
installation, i.e. can be run from directory into which it got unpacked.

And thus the portable Perl doesn't even require Administrator privileges.


I would then create two one line scripts:

hello_to_stdout.pl :

print STDOUT "Hello\n";

hello_to_stderr.pl :

print STDERR "Hello\n";

- the purpose of the scripts is to check whether basic console output works. If 
it doesn't, there is no sense to run Octave.


Regards,
  Sergei.