I try to build a kernel mode driver in windows 7 x64.I already disable the patch guard.whenever i open the x64 checked build environment command prompt i get this error
"WARNING: x64 Native compiling isn't supported. Using cross compilers".Please help me to solve this error.
That is not an error. It's perfectly normal and you can ignore it. It's just telling you that the x64 compiler is actually a 32-bit compiler that generates 64-bit code. Hence the term "cross compilers."
Related
I've been trying to use emscripten to build C into WASM and Javascript. Emscripten requires clang so I installed it but then it says "emcc: error: llc executable not found at C:\Program Files\LLVM\bin\llc.exe" when running emcc and em++. Is there a reason that LLC.exe is missing in the windows version? If so how do I get it.
llc is a developer tool. If you want it, build it from llvm-project source. This is/will not included in the release binary.
I have installed WDK and SDK on my Pc.. I can see them on my system.. But I am not able to get "x64 checked build environment command prompt"..My OS is windows 8.1 .. If anyone has a solution to the problem please do let me know
If you open a VS developer prompt, you should have access to MSBUILD and from there, you need to use MSBuild command line parameters to build for x64 chk project. These variables would be /p:platform=x64 and /p:configuration=Win7 Debug. WDK will pick the right cross arch compiler and build for the respective configuration.
I built clang using VS2013 and then ran it from the command line with a -v option (clang -v testfile.c). Among the things it reported was:
#include <...> search starts here:
C:\Program Files (stand-alone)\LLVM\bin..\lib\clang\3.7.0\include
C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\include
I don't understand why it is even looking at the Microsoft headers in the first place. I do not have an environment variable named INCLUDE. I verified this by doing "set INCLUDE" from the command line getting a message saying there was no such environment variable. So, where and why is clang getting this information and how do I stop it? During the compile several warnings (not errors) occur regarding some of the things in Microsoft header files too.
The version it reports is:
clang -cc1 version 3.7.0 based upon LLVM 3.7.0svn default target i686-pc-windows-msvc
I understand the i686-pc-windows part, but why the msvc part? If that means it was built with msvc then that makes sense, but if it means that clang was built to run with msvc support, I don't understand why.
I want to run an .NET executable that needs more than 4G RAM on OSX 10.9. I had Xamarin Studio installed but AFAIKT Xamarin doesn't come with a 64-bit mono build, so I decided to make a custom 64-bit mono with "with-large-heap=yes" configuration, and install it in a different location.
git clone https://github.com/mono/mono
cd mono
./configure --prefix=<my-local-dir> --enable-nls=no --with-large-heap=yes
make
make install
(I also built a 64-bit F# and installed in my-local-dir, following "Option 3" in this page.)
However, when I use the 64-bit mono to run the executable (an F# program built with the canonical "fsharpc" in Xamarin), it still crashes with System.OuOtfMemory exception. I tried this:
export PATH=$PATH:<my-local-dir>/bin
MONO_GC_PARAMS=max-heap-size=5g <my-local-dir>/bin/mono <my-executable>
And it gives a warning
Warning: In environment variable `MONO_GC_PARAMS': `max-heap-size` must be an integer.
(this error message is a bit misleading, I think it really means 5g is too large and not supported, because it doesn't complain if I put a "3g" there). And the program still crash with the same exception at the point when it exceeds the memory.
Did I miss any thing important? How do I configure mono to have more than 4G heap size?
You are still running the 32 bit version of mono (check your PATH env var). This also explains the parsing of 5g for max-heap-size (it will work correctly with 64 bit mono).
The default as with your configure command above is to install in /usr/local/bin, so just run your programs with /usr/local/bin/mono program.exe.
Has anyone succeeded to compile a Win32 GUI app with the command line dcc32.exe compiler, under 64-bit Windows Vista, without installing Delphi 2009? On our system it fails, with a message that the DFM files contain unknown 16-bit resources. This is usually an indication that the DFM files cannot be read. It works perfectly on all 32-bit Vista and Windows XPs, that we tried.
I am asking, because we want to ensure that we can rebuild our current exe files later, if needed, so even if we all switch to 64-bit OSes in the future, we want to be able to rebuild the old 2009 versions.
With Delphi 2009 you should use msbuild to commandline compile your projects (msbuild YourProject.dproj). Be sure to do this from the RAD Studio commandprompt. This ensures some environment variables are set. Does this solve your problem?
Adding lnkdfm120.dll solved the problem.
Yes, we are performing console builds via dcc32 through nant in both Vista 64-bit and Windows 2008 64-bit. You may have to deal with some path issues the (X86) if you installed to the default location (we do not to remove these types of dependencies).