-
Notifications
You must be signed in to change notification settings - Fork 49
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
Reference issues when compiling during Go Get #27
Comments
It seems that |
I'm not terribly familiar with compiling C, but could this be related to my choice of sjlj instead of seh when I installed mingw-64? I only ask because I noticed seh in mentioned in the error log, but I'm not familiar with how you easily determine which exception handling you need to compile something (or if you actually need to match your gcc binary with what the library is using--and if you do, how you switch between them for different projects that require each besides changing your path back and forth a lot). Or does all cgo assume a specific exception handling method? |
It is highly possible that sjlj/seh issue is the reason. I compiled the wx libs using tdm-gcc-64 and by default it uses SEH to handle exceptions. By the way cgo doesn't require any specific exception handling method - exceptions only exist in C++, not in C. |
trying with 7.1.0 gcc seh from mingw-64 gave me...
since the end mentions uuid, I'll try the mingw allow-multiple-definitions fix in case it also applies to mingw-64 as well |
Previously I used 6.2.0 gcc sjlj and now tried 7.1.0. However, the GCC install you linked to from TDM is gcc 5.1.0. Both of the later two tries (using seh) resulted in a 4 hour wait before I killed the process and a 30 minute wait before I killed the
|
I encountered the same issue in Linux with gcc 7.1.1. gcc seemed stucked for quite a long time when called by |
A little update about gcc 7.1 issue: After investigating, I found that during the cgo process, C Compilers (whatever you use) will print tons of error messages. When using clang, the printing is very fast; however, gcc 7.1 is very slow. That's why it seems stuck - it is just printing lots of messages. Actually wxGo will be successfully built finally. |
It's been a while, so I don't remember if I originally cancelled out and just assumed it failed. I appreciate the followup and will try it again with Go 1.9 since I just updated. When you say slow, do you mean 2 minutes? 20 minutes? more? |
It is just a guess, that the bottleneck is the printing - more investigation is needed. I have tested on Linux. It will consume about 30 mins to finish printing. I can't tell how long it will take on Windows, due to different IO performance - maybe much longer. If you are interested in seeing the printing: |
Same here. As I use Windows 32 bit, I can't (as per Readme) compile WXGo, so I grabbed the latest release in binary form (*.a package). |
I tried compiling with mingw-64 7.1.0 on Win 10 via |
I ran
go get github.com/dontpanic92/wxGo/wx
on Windows 10 with 64 bit Go 1.8.1 and GCC version 6.2.0 (x86_64-posix-sjlj-rev1, Built by MinGW-W64 project) which results in the attached error.Error output
The text was updated successfully, but these errors were encountered: