-
Notifications
You must be signed in to change notification settings - Fork 35
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
build fails on Windows on 0.7/1.0 #56
Comments
The root cause seems to be JuliaPackaging/WinRPM.jl#150 |
Is there any solution for this error? |
see JuliaPackaging/WinRPM.jl#157 I still need to create a test for the solution, need to find some time to do so... |
For what it's worth, I'd also be grateful to see a solution to this issue. Thanks! |
please see JuliaPackaging/WinRPM.jl#157
Op wo 17 okt. 2018 om 12:14 schreef Jason Veysey <notifications@github.com>:
… For what it's worth, I'd also be grateful to see a solution to this issue.
Thanks!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#56 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Afj4Kuk3hJRIdGQSd4kOvjyngAgTa1-Aks5ul2WQgaJpZM4VdSsD>
.
|
In order to build Cbc on windows 10, should I install an earlier version of Julia? |
Cbc works on Julia 0.6.x under Windows. |
I found a solution for that. The error is about finding a file in WinRPM package so when you change the file name |
The PR mentioned above does solve that.
…On Sun, Oct 21, 2018 at 11:35 orhanabar ***@***.***> wrote:
I found a solution for that. The error is about finding a file in WinRPM
package so when you change the file name
"mingw64-libstdc++6-8.2.0-2.1.noarch.cpio" to
"mingw64-libstdc%2B%2B6-8.2.0-2.3.noarch.cpio" in
C:\Users<user>.julia\packages\WinRPM\Y9QdZ\cache\2 folder it builds fine.
But we still need a generic solution.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#56 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/Afj4KpOIu4iZ8uMj-r3Jv5tb2NFxA4eeks5unKJbgaJpZM4VdSsD>
.
|
I am new in github and julia. So, what does PR mean and how can I apply? |
A PR is a Pull Request. It is a way to merge code changes and keep track of all the changes. |
I worked around the build issues on Windows (with help from the above - thanks). However, I now get a runtime Access Violation Exception, see error below (tried on two different machines). Is anyone else experiencing this? Error:
|
@Plug11 can you provide a reproducible example? |
Hi, sorry for the delay, the problem seems to be an interaction between Clp and Cbc. If I include ### When we load the Clp package, it causes Cbc to crash
### Comment the following line and the crash does not happen
using Clp
using JuMP
using Cbc
m = Model(solver = CbcSolver())
@variable(m, 0 <= x <= 2 )
@variable(m, 0 <= y <= 30, Int)
@objective(m, Max, 5x + 3*y )
@constraint(m, 1x + 5y <= 3.0 )
print(m)
status = solve(m)
println("Objective value: ", getobjectivevalue(m))
println("x = ", getvalue(x))
println("y = ", getvalue(y)) |
That makes sense. Clp and Cbc both have dependencies in common that are currently provided by different (and possibly conflicting) dlls. The fix is likely to move Cbc to BinaryBuilder. @juan-pablo-vielma has been working on this but ran into technical issues that are blocked by missing functionality in BinaryBuilder. |
The missing BB functionality was just added and the windows bug for Clp seems to be resolved, so it looks like I am back on track with the move to BB 🤞 |
Great, good to hear we have a solution on the way! |
@Plug11 can please try if these versions of Clp/Cbc work on your system |
Hi @juan-pablo-vielma, thanks very much for this! I installed and ran the test script and it now runs through and gets the result without crashing. I did get some warnings which I post below in case they are of interest.
|
seems to be looking for
mingw64-libstdc **%2B%2B**6-7.2.0-3.2.noarch.cpio
in stead of
mingw64-libstdc**++**6-7.2.0-3.2.noarch.cpio
.Encoding issue I presume?
The text was updated successfully, but these errors were encountered: