-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Native Windows 8 Build #3153
Comments
Can you post the results of running |
I'm on windows 8, 64-bit. |
As I suspected, the makefile only works on Windows 7. Which is silly, because it was lazy. The detection logic in Make.inc needs to be fixed @karbarcca In Make.user you can add the following to force it to work:
|
Ok, I added the lines to Make.user. It now catches on
I've updated the build log above to the new full output. |
Seems like the above error is a 32/64-bit compatibility issue (from googling). In the openlibm make file, it uses |
It now snags while building LLVM:
I've updated the original build log with as much output as I could get. |
Have you done modifications of LLVM mentioned in Build Errata? |
To make sure I'm doing it right #define HAVE_EHTABLE_SUPPORT 1
#else
#define HAVE_EHTABLE_SUPPORT 0 becomes #define HAVE_EHTABLE_SUPPORT 0
#else
#define HAVE_EHTABLE_SUPPORT 0 |
Seems right. Make sure to run |
You don't need to run make clean after this modification. That change is fine, or you can collapse it into one statement and remove the |
Running
I updated my original build log, but it's mostly failed tests. |
I had the same problem on Windows 7 64-bit since Windows build started using MinGW 4.8. No idea how to resolve this. |
It sounds like this is a different error that should have a separate bug report. |
Try using the MinGW MPFR. As MPFR is one of the GCC deps, you almost never should have to compile it manually, and I think it's possible to build BigFloat on MPFR 2.4.x if you comment out |
So after researching the mpfr bug, it sounds like there are 2 issues. The first is some kind of TLS support issue and is solved by adding the |
Everything then seems to compile fine until the final linking, I get this error (which seems identical to the earlier bug with LLVM JIT)
|
After running
|
Yeah, this is a well-known issue. Unfortunately, this is no known solution to it. I have open issue #2892 almost a month ago. It was a reason why I started working on "native" building system on Windows (NMake + Intel C++ Composer / Microsoft SDK) - there is very difficult to use GDB on Windows and thus I have not able to find out the problem behind this issue. Cross-compiling worked fine for me in the past (before switching MinGW 4.8) and I recommend you to give it a try. In the case of success/failure report here - it will be interesting to know other's experience. |
Actually, setting USE_SYSTEM_MPFR=1 will almost certainly cause the error that you see since mingw does not include libmpfr.dll |
Ah, Github's autocomplete gets in my way too. I just forced a check of my cross-compiled copy of mpfr with wine and it was fine. The printf tests that failed for me were preceded by warnings from wine that it was using unimplemented features of msvcrt. |
My 32-bit Julia REPL is crashing on Windows at unpredictable times with
I'm using a cross-compiled 32-bit version on Windows 7, using build a7c301f-WINNT-i686. The previous version that I used, 3ee9803-WINNT-i686 never gave that problem. |
As an update, I believe I've gotten MPFR to compile correctly (after reaching out to the mpfr team for some help). The adjustments I have to make are adding Unfortunately, though MPFR now compiles and passes tests,
Any ideas on where to look next for solutions? |
@karbarcca I strongly recommend you to try cross-compilation. I have just cross-compiled a fresh version of Julia without any problems. |
@vharavy I'm already cross-compiling my current julia build. I would, however, really like to be able to build natively, so I'm letting that desire and the free-time I currently have to poke around and try to get things working. I think it only benefits everyone if various wrinkles get ironed out, right? |
@karbarcca In this case, feel free to poke around. You can find instructions how to run Julia under debugger at the beginning of discussion of issue #2896. Using GDB on Windows is a little bit tricky and requires a lot of patience, but if you have enough time you may find the problem. |
Today is not a good Julia day South of the equator. We are not managing to compile on Linux (for Linux), because it uses git instructions our system does not have. Our windows cross-compile seems to work, but then REPL crashes as indicated above. I'm having to fall back on a build that is about 2 weeks old. |
@StefanKarpinski @ViralBShah are we using |
I started a draft README of debugging julia on windows to add to the README.windows file. Please help me improve it! |
@bsxfan What version of git are you using? I do not recollect any git related changes in the build. |
@ViralBShah, thanks for the support.
|
I belive we prefer git 1.7. Is it possible to upgrade? |
With regards to the I poked around the deps tests/checks last night and tried to rerun as many as I could find. A few results:
Obviously there can be a ton of different things going on here, but I wasn't sure if anyone has any other input on the status of deps tests for windows. |
Thanks for pushing the fixes @vtjnash, can something be done about openlibm correctly detecting |
Ah, I missed the comment about |
to whom it may concern: gcc on apple reports that its target ARCH is i686. this causes problems if you attempt to do USEGCC=1 |
@bsxfan the 32-bit build should now be fixed |
I think there's growing interest in improving the native windows build process (from comments about wanting 0.2 binaries, etc.). I know I'd personally love to get it working as well. I also know that @vharavy has been doing related work here, so if there's major changes coming along that make improving the mingw/msys build not worth it, just let me know.
Following the windows.readme this morning, my build doesn't get very far before snagging an error on linking
random
. Inspectingusr/lib
, I thought it was interesting thatlibgrisu.so
andlibrandom.so
are.so
files instead of.dll
files. Is the shared library extension not getting set right or is this right?Full build log: https://gist.github.com/karbarcca/5612472
Any help/direction is much appreciated!
The text was updated successfully, but these errors were encountered: