Does Encog C# support 64 bits ?
I can compile in 32 bits with Encog but I can not compile in 64 bits ?
How can we compile in 64 bits with Encog ?
The Encog core DLL can be compiled to either 64 or 32 bits. Unlike the Java Encog version, you have to specifically target one.
Related
I am getting the below error when I try to execute the below line of code in my project. I added a 64 bit JDK to my project properties . I am using Intellij as my IDE
System.loadibrary(smsjavaagentapi)
Fatal Error: Exception from System.loadibrary(smsjavaagentapi) java.lang.unsatisfiedLinkError smsjavaagentapi.dll: Can't load IA 32 bit .dll on an AMD 64-bit platform
I think the problem is that I am using a 64 bit JVM and I am trying to run a 32 bit .dll. I don't have an option to install 32 bit JDK on my machine and add it to my project properties nor I can port the .dll to 64 bit . Is there a work around for this?
There is a limitation at the OS level which prevents a 32-bit shared library being loaded by a 64 bit process, so your options are
modify the OS to allow this (not easy)
migrate the DLL to 64-bit by recompiling it.
install a 32-bit JVM (easier)
download a 32-bit JVM and unpack it without install it. (doesn't require any special permission)
You might find you can get a version of IntelliJ which ships with a 32-bit JVM, or install another program which installs a 32-bit JVM and use just the JVM.
I have a 64 bit version of Solaris with a 32 bit bundled version of Apache. I am trying to load mod_wl.so which is a 64 bit module for the apache-weblogic proxy but I get this error:
mod_wl.so: wrong ELF class: ELFCLASS64
to me this suggests that the 32 bit Apache is not compatable with 64 bit modules. My UNIX admin suggests otherwise, citing the modules-64.load file as enabling the 64 bit modules to work with 32 bit Apache.
I'm not convinced, I think he needs to rebuild Apache to 64 bit.
Am I right?
You are right, that's not going to work.
As succinctly answered by #Leeft, this doesn't work.
The modules-64.load file sits alongside modules-32.load. In httpd.conf a check is done on the bit size to determine which of these files to use, so a 64 bit build reads from modules-64.load so that 'directives contained in it are actually available before they are used'. In other words, this has nothing to do with enabling 64 bit modules to work with a 32 bit build - my UNIX admin appears to not know what he is talking about.
So the answer is 'yes I am right' - we need a 64 bit build of Apache or a 32 bit build of the weblogic module. Being that Oracle owns both Sun (Solaris) and Weblogic you'd think that they'd have figured that a the 32 bit default install of Apache on a 64 bit machine would need a 32 bit module, but apparently not.
How to determine whether library is 32 bit or 64 bit from the library file ? I have installed gstreamer from ossbuild for this I know its 32 bit but suppose if someone else installs a library what is the way to find if it is compatible with 32bit or 64bit . Also are the format of the library similar or they differ?
When you said "Library", I guess you mean "runtime Library" aka. Dynamic-Link Library (DLL), is that correct?
In that case, this might be a duplicate of this question
I'm planning a test environment in several platforms include both 32/64 bits but I'm not sure about the hardware 32 bit could be virtualize through HyperV or not?
SUre it can. Hyper-V simulates a 64 bit environment. You can install a 32 bit operating system on a 64 bit processor, or? ;) I did not see any 32 bit normal processor (outside some low poewer stuff) in the last years.
I want to install mono on an embedded system (arm board) it has no ethernet connection, so i need to do a local installation, (i can transfer data / files to the board with sdcard).
Board Data:
32 Kbytes of Internal ROM
64 Kbyte of Internal SRAM
64 Mbytes of SDRAM memory (32-bit bus width)
256 Mbytes of NAND Flash memory (8-bit bus width)
(edit: OS is a busybox 1.12 buildroot)
(edit2: got now a debian grip chroot)
Any ideas how i can get a mono environment to work on the board?
best regards
You can just use a cross-compiler or do the build on another more powerful ARM development box, then you make install to a, say, /tmp/arm-install directory and then finally transfer the contents of that dir to the ARM box in the final installation dir.