Skip to content
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

Julia 0.6.1: make install is trying to build documentation again #24432

Closed
ronisbr opened this issue Nov 1, 2017 · 4 comments · Fixed by #24496
Closed

Julia 0.6.1: make install is trying to build documentation again #24432

ronisbr opened this issue Nov 1, 2017 · 4 comments · Fixed by #24496

Comments

@ronisbr
Copy link
Member

ronisbr commented Nov 1, 2017

Hi guys,

I am trying to pack julia 0.6.1 to openSUSE. However, in the build process (make install), I am seeing this error:

[  497s] make[2]: Entering directory '/home/abuild/rpmbuild/BUILD/julia'
[  497s] Warning: git information unavailable; versioning information limited
[  497s] make[2]: '/home/abuild/rpmbuild/BUILD/julia/usr/lib/julia/sys.so' is up to date.
[  497s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/julia'
[  497s] make[2]: Entering directory '/home/abuild/rpmbuild/BUILD/julia/doc'
[  497s] Warning: git information unavailable; versioning information limited
[  497s] /home/abuild/rpmbuild/BUILD/julia/deps/tools/jldownload http://www.unicode.org/Public/9.0.0/ucd/UnicodeData.txt
[  497s] Could not find working curl, wget, or fetch.
[  497s] You need to install one of these to download dependencies.
[  497s] make[2]: *** [Makefile:22: UnicodeData.txt] Error 1
[  497s] make[2]: Leaving directory '/home/abuild/rpmbuild/BUILD/julia/doc'
[  497s] make[1]: *** [Makefile:119: docs] Error 2
[  497s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/julia'
[  497s] make: *** [Makefile:59: /home/abuild/rpmbuild/BUILD/julia/doc/_build/html/en/index.html] Error 2
[  497s] error: Bad exit status from /var/tmp/rpm-tmp.DCcxzr (%install)
[  497s] 
[  497s] 
[  497s] RPM build errors:
[  497s]     Bad exit status from /var/tmp/rpm-tmp.DCcxzr (%install)

This is really strange, because the file /home/abuild/rpmbuild/BUILD/julia/doc/_build/html/en/index.html exists. Furthermore, I had no problem with julia v0.6.0 and nothing seems to have changed between v0.6.0 and v0.6.1 with respect to the Makefiles.

@ronisbr
Copy link
Member Author

ronisbr commented Nov 1, 2017

I am using the following patch as a workaround:

Index: julia/Makefile
===================================================================
--- julia.orig/Makefile
+++ julia/Makefile
@@ -332,7 +332,7 @@ define stringreplace
 	$(build_depsbindir)/stringreplace $$(strings -t x - $1 | grep '$2' | awk '{print $$1;}') '$3' 255 "$(call cygpath_w,$1)"
 endef
 
-install: $(build_depsbindir)/stringreplace $(BUILDROOT)/doc/_build/html/en/index.html
+install: $(build_depsbindir)/stringreplace
 	@$(MAKE) $(QUIET_MAKE) all
 	@for subdir in $(bindir) $(datarootdir)/julia/site/$(VERSDIR) $(docdir) $(man1dir) $(includedir)/julia $(libdir) $(private_libdir) $(sysconfdir); do \
 		mkdir -p $(DESTDIR)$$subdir; \

@nalimilan
Copy link
Member

I have bumped into the same problem when trying to build Fedora RPMs. In fact I had introduced this code in #19705 precisely for this reason.

I think the problem has to do with timestamps. In the 0.6.0 tarball, doc/_build/html/en/index.html had the most recent timestamp of all files. In the 0.6.1, some files under src are slightly more recent than it, like src/version_git.jl.

@ararslan Any idea what could have triggered an update of version_git.jl after the docs where built when preparing the tarball? Ideally one would just need to call make release-candidate, but maybe some steps are still manual?

@ararslan
Copy link
Member

ararslan commented Nov 5, 2017

I have no idea.

@nalimilan
Copy link
Member

I think I have a fix at #24496. I have no idea why this used to work, since version_git.jl has been introduced before #19705, but excluding it from dependencies seems to fix the problem here. Nevertheless, we should definitely check that it works before uploading the tarballs for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants