Various fixes to GUB:
- update broken download links
- add missing dependencies
- fix 'make' for glibc 2.27 systems
- teach our ancient glibc that make 4.x exists
- fix 'db delete failing' problem on openSuSE Tumbleweed
Status on some selected distributions:
ubuntu-14.04.5 LTS:
'make lilypond LILYPOND_BRANCH=stable/2.20' succeeds
ubuntu-16.04.4 LTS:
'make lilypond LILYPOND_BRANCH=stable/2.20' succeeds
ubuntu-18.04 LTS and openSuSE Tumbleweed
'make bootstrap' succeeds, but crossbuilding guile still fails during 'make lilypond LILYPOND_BRANCH=stable/2.20'
Signed-off-by: Knut Petersen knut_petersen@t-online.de
This allows GUB to be used on an ubuntu 14.04-5 system.
Install ubuntu 14.04-5, boot it, login as root, then execute
To use GUB you have to create a user gub. 'make lilypond' will only succeed if GUB is installed in '/home/gub/NewGub/gub' [Reason: our regtest results are erroneously built with dgs-load-fonts]
Login as gub, then
apply the patch, then
IF none of the download links are broken (checked 2018-07-16) make takes about 160 minutes to finish on my i4790K system.
At the moment building of lilypond master is broken because of Alexander Myltsev's recent patch to musicexp.py that is incompatible to our ancient toolchain.
You may want to use an image of ubuntu with chroot. If the ubuntu system is installed on /dev/sdc2 and you want the image to be located at e.g. /home/knut/sources/ubuntu-14.04-5-server/, you could use something like
immediately after installing ubuntu to /dev/sdc2 and rebooting to you normal system. After that continue with 'apt-get update' etc as described above.
With the discussed patch GUB also succeeds to 'make lilypond ...' on Ubuntu 16.04.4 LTS.
Knut
Diff:
Note: I cannot test this using the usual patch-test scripts. We have no specific procedure in place for GUB patches as it were. So I will set this to review but this can probably bypass the normal patch test countdown and get 'pushed' via comments from Phil/Masamichi et al who 'do' GUB-stuff
Knut, I guess you'd better send a pull request to Github repository so Phil can easily test it and merge it. Or send him the patch file by email.
2nd version of GUB patch set, fix gmake segfaulting on glibc 2.27
http://codereview.appspot.com/369750043
Diff:
Knut sned a pull request please to the GUB github repo.
https://github.com/gperciva/gub
Fix the 'db delete failing' problem. Needed at least for openSuSE Tumbleweed.
http://codereview.appspot.com/369750043
Diff:
Knut,
This has been 'counted down' can you make a pull request to the approrpiate repo please?
You'll have to do this yourself.
James
Knut,
This has been 'counted down' can you make a pull request to the approrpiate repo please?
You'll have to do this yourself.
James
Knut,
Make a pull request please at
https://github.com/gperciva/gub
James
Knut, I'm testing your patch on Fedora 28.
When building glibc (during the
make bootstrapstep), it seems that it's still using my system make (version 4.2.1) instead of the version (3.81) downloaded by gub. This is a problem that was supposed to be fixed by your patch?I've downloaded the 3rd patchset from Rietveld, applied it with
patch -p1and committed to this branch:https://github.com/fedelibre/gub/tree/5384-knut-patch
These lines are taken from
target/linux-64/build/glibc-core-2.3/config.log(full file attached):And this is the tail of
make bootstrap:The
patches/glibc-allow-make4.patchfile seems to be applied. I've checked the relevant lines in this file:Find attached also the file
target/linux-64/log/glibc-core.log.Sorry, actually the patch has not been applied! The 4.x regexp is missing.
Tomorrow I'll try a clean build.
I've edited manually the file
src/glibc-core-2.3/configureand runmake bootstrapagain. This time I've managed to pass the glibc-core build step:even though above lines would suggest that all the files have been downloaded again from scratch and therefore the patch would have been applied.
I'm confused...
Anyway let's see if I manage to complete the bootstrap step and then I'll make a clean build in another directory.
make bootstrapcompleted successfully.Now
make lilypondis failing in the compile stage of tools::glib:The last lines of glib.log (full file attached) are: