Okay, it turns out it's not very hard at all to use the opensuse build service, fork the package that's causing trouble, and revert it back to the last working state. See https://build.opensuse.org/package/show/home:kelman/mingw64-tk
You can use this by doing the following: using WinRPM push!(WinRPM.sources, "http://download.opensuse.org/repositories/home:kelman/openSUSE_13.1";) WinRPM.update() WinRPM.install("tk") Then I think things should work again for you. Please let me know if not. On Sunday, October 26, 2014 6:56:53 PM UTC-7, Tony Kelman wrote: > > Sorry about this Miguel. We use a build service from OpenSUSE to download > WinRPM binaries for many packages on Windows. Unfortunately it's not a very > stable repository, the maintainers frequently change the names around or do > massive reformatting on the build scripts which cause our package > installation to break. In this case, Tk is broken, see > https://build.opensuse.org/project/monitor/windows:mingw:win64?arch_x86_64=1&defaults=0&failed=1&repo_openSUSE_13_1=1 > > - I don't quite understand why, there are some undefined references in the > build log. If anyone is familiar with cross-compiling Tk and wants to help > submit a request to fix this, please let me know (or just do it). > > Unusually, it looks like Tk.jl actually has Windows compile-from-source > instructions in deps/build.jl that are written for MSVC. So it might be > feasible to build Tk from source by installing Visual Studio Express, if > you're in a hurry. Normally we don't require users on Windows to worry > about compilers, but we haven't found a way yet to mirror the OpenSUSE > package repository so it stays more stable. We'll try to figure out how to > do so. > > > On Sunday, October 26, 2014 12:27:30 PM UTC-7, Miguel Belbut Gaspar wrote: >> >> Hi, >> >> I recently updated to julia 0.3.2, and now I have problems with some >> packages. I removed the .julia directory, and reinstalled, but the problems >> appeared again (some packages had build errors). >> I don't remember exactly which packages it was, but the first error I >> noticed was: >> >> configure: error: no acceptable C compiler found in $PATH >> >> From there on, several packages also had build problems. >> I did a fresh install of julia 0.3.2, and tried to install Tk.jl, and it >> gave the following errors: >> >> [...] >>> INFO: Building WinRPM >>> WARNING: skipping repodata/repomd.xml, not in cache -- call >>> WinRPM.update() to download >>> WARNING: skipping repodata/repomd.xml, not in cache -- call >>> WinRPM.update() to download >>> [...] >>> =================================[ ERROR: Tk >>> ]================================== >>> >>> >>> None of the selected providers can install dependency tk. >>> Use BinDeps.debug(package_name) to see available providers >>> >>> while loading C:\Users\Miguel\.julia\v0.3\Tk\deps\build.jl, in >>> expression starting on line 54 >>> >>> >>> ================================================================================ >>> >>> >>> ================================[ BUILD ERRORS >>> ]================================ >>> >>> >>> WARNING: Tk had build errors. >>> >>> - packages with build errors remain installed in >>> C:\Users\Miguel\.julia\v0.3 >>> - build a package and all its dependencies with `Pkg.build(pkg)` >>> - build a single package by running its `deps/build.jl` script >>> >>> >>> ================================================================================ >>> >> >> After removing Tk.jl, (Pkg.rm("Tk")), and tying to install VideoIO, got >> this error: >> >>> INFO: Changing Directory to >>> C:\Users\Miguel\.julia\v0.3\Tk\deps\src\tk8.6.0/win >>> =================================[ ERROR: Tk >>> ]================================== >>> >>> >>> could not spawn `nmake -f Makefile.vc >>> 'TCLDIR=C:\Users\Miguel\.julia\v0.3\Tk\dep >>> s\src\tcl8.6.0'`: no such file or directory (ENOENT) >>> while loading C:\Users\Miguel\.julia\v0.3\Tk\deps\build.jl, in >>> expression starti >>> ng on line 54 >>> >>> >>> ================================================================================ >>> >> >> >> Has anyone been having similar issues? >> Any sugestion on how to fix it? >> >> Miguel >> >
