Is there a clear or easy way to check over the command line if the installed JRE is 64 bit on a Sparc machine?
I am used to seeing this in:
java -version
however it appears that Solaris only says what version and build of java is installed.
Run java -d64 -version. It will complain if a 64 bit JVM isn't installed.
If d ( in lower case) does not work, put D in Upper case.
Related
I am running NetBeans 8.0.2 on a 64-bit Windows 7 PC. I was trying to follow Geertjan Wielenga's instructions for getting up and running with Scala in NetBeans 8.x.
The first instruction starts, "In the Terminal window, ..." so I selected Window > IDE Tools > Terminal. Instead of being a useable terminal window, the tab's content area was completely gray. I noticed that there seemed to be text flashing in the window before it went gray, so I clicked on the "Create New Local Terminal Tab" button multiple times until I was able to read the disappearing text:
Unable to start pty process
Searching for this phrase yielded results for C/C++ projects and the "Run" command, but I'm not doing a C/C++ project. How can I get the terminal window to a state where I can interact with it?
The NetBeans Terminal Emulator requires Cygwin. Importantly, the bitness of NetBeans must match the bitness of Cygwin. If you are using a 64-bit version of NetBeans, then you must use a 64-bit version of Cygwin; likewise 32-bit and 32-bit.
This comment by Andrew Krazny on NetBeans bug 234221 says:
A bitness of jdk/netbeans is important. Possible options are:
32-bit NB and only 32-bit cygwin is installed
32-bit NB and only 64-bit cygwin is installed
32-bit NB and both 32/64-bit cygwin are installed
64-bit NB and only 32-cygwin is installed
64-bit NB and only 64-cygwin is installed
64-bit NB and both 32/64-bit cygwin are installed
Cases 1) and 5) are 'ideal' - in this case everything should work and it is highly recommended that bitness of NB/cygwin match. This means that if one tries to use cygwin64 (s)he should install 64-bit java and run 64-bit version of NetBeans (netbeans64.exe).
Case 2) is almost nonfunctional. It requires cygwin64/bin to be in %Path%; compilation will work, but run is possible in 'External Terminal' only.
Case 3) NB will detect 32-bit cygwin and will use it by default. IF user tries to add cygwin64 as a toolchain and compile his code in 64-mode, run in 'Output Window' will not work. 32-bit toolchain is OK in this case
Case 4) is almost nonfunctional. It requires cygwin/bin to be in %Path%; compilation will work, but run is possible in 'External Terminal' only.
Case 6) 64-bit compilation/run will work, 32-bit run will fail.
In my case, I was using 32-bit Cygwin with 64-bit NetBeans. I installed 64-bit Cygwin, added a CYGWIN_HOME environment variable, and added %CYGWIN_HOME%\bin to the end of my path¹, and now I have a functioning terminal window.
¹which I hate doing because there are command names that overlap
I've installed WinDBG on Windows 7 64-bit, however, I want to install the 32 bit version, not the 64 bit version.
I found this link on the internet:
https://social.msdn.microsoft.com/forums/windowsdesktop/en-us/cd004535-75f1-48ee-9176-574b344ddce1/how-to-install-windbg-32bit-on-64bit-system
Following the accepted answer, I do not have that path on my computer.
I have:
C:\Program Files\Microsoft SDKs\Windows\v7.1\Redist
However, there is no "Debugging Tools for Windows" folder in that direcotry like the answer says, only the VC folder. WinDBG is installed and working.
What can I do? Thanks.
You could download Windows SDK ISO file (https://msdn.microsoft.com/en-us/windows/desktop/bg162891.aspx) and install 32bit version from there. Also you could use !wow64exts.sw command to debug win32 process or dump using x64 version.
Newbie programmer here, I'm getting an error when using Eclipse saying
"G++/GCC not found in path"
So apparently I need a compiler? I need a download link to g++ since I can't find it anywhere on the web.. I went on to GNU collection's website but there is NO download link for G++,
thanks.
The usual resources would be MinGW (32-bits) or MinGW-W64 (64-bits). Start with these links
MinGW-w32 vs. MinGW
MinGW — Minimalist GNU for Windows
MinGW-w64 - for 32 and 64 bit Windows (Since the mingw-w64 project on sourceforge.net is moving to mingw-w64.org i suggest to use mingw-w64.org)
mingw-w64 — GCC for Windows 64 & 32 bits
I'm creating a standalone executable from MATLAB .m file using mcc.
My machine is a 64bit machine and the target machine is 32bit machine, is it possible to create such an application (and to be able to run it on the target machine of course)?
Probably the simplest way to do this is to install the 32 bit version of MATLAB and use the mcc from that installation.
Don't worry about the warnings that you get about installing 32 bit MATLAB on 64 bit Windows. It works just fine. I have lots of different versions of MATLAB installed on my machine for development purposes, both 32 and 64 bit, all happily co-existing side by side.
The documentation also mentions a -win32 option that can be passed to mcc:
-win32 Run in 32-Bit Mode
Use this option to build a 32-bit application on a 64-bit system only
when the following are both true:
You use the same MATLAB installation root (matlabroot) for both 32-bit and 64-bit versions of MATLAB.
You are running from a Windows command line (not a MATLAB command line).
Since you have to install 32 bit MATLAB, no matter what, it seems to me that it's just easier to run the 32 bit mcc directly.
Currently I'm trying to run Eclipse Classic under Windows 7 x64, without success.
First, I've downloaded the JDK from here.
Second, I've downloaded the Eclipse 32 bit Version, which crashes while showing the splashscreen, for a very short time.
The 64 bit version at last, shows an error message, that the jvm.dll can't be loaded (shown path is valid).
What can I do now? Java seems to work, as I can run Netbeans and other Java Applications.
I also have no error log of Eclipse, as no workspace is setup.
Fixed it! For both, 32 & 64 Bit version. I used the posted Eclipse.ini setting from here, edited the paths to fit my environment and bam! It worked. Thanks for your support :)
Make sure you're running a 64 bit JDK, that JAVA_HOME is set properly, and that %JAVA_HOME%\bin is in the front of your path. I also might try running eclipse from the DOS prompt to see if you get any startup error info there.