`make bootstrap` completed successfully.

Now `make lilypond` is failing in the compile stage of tools::glib:

~~~~
building package: tools::glib
 *** Stage: download (glib, tools)
 *** Stage: untar (glib, tools)
 *** Stage: patch (glib, tools)
 *** Stage: autoupdate (glib, tools)
 *** Stage: configure (glib, tools)
 *** Stage: compile (glib, tools)
Command barfed: cd /home/fede/src/gub/target/tools/build/glib-2.44.1 && make 
-j8  

Tail of target/tools/log/glib.log >>>>>>>>
    make[1]: *** [all-recursive] Error 1
    make[1]: Leaving directory 
`/home/fede/src/gub/target/tools/build/glib-2.44.1'
    make: *** [all] Error 2
    Command barfed: cd /home/fede/src/gub/target/tools/build/glib-2.44.1 && 
make -j8
<<<<<<<< Tail of target/tools/log/glib.log

*** Failed target: tools::glib
make[1]: *** [gub.make:63: packages] Error 1
make[1]: uscita dalla directory "/home/fede/src/gub"
make: *** [GNUmakefile:26: lilypond] Error 2
~~~~

The last lines of glib.log (full file attached) are:

```
make[4]: Leaving directory 
`/home/fede/src/gub/target/tools/build/glib-2.44.1/glib'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory 
`/home/fede/src/gub/target/tools/build/glib-2.44.1/glib'
make[2]: *** [all] Error 2
make[2]: Leaving directory 
`/home/fede/src/gub/target/tools/build/glib-2.44.1/glib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/fede/src/gub/target/tools/build/glib-2.44.1'
make: *** [all] Error 2
Command barfed: cd /home/fede/src/gub/target/tools/build/glib-2.44.1 && make 
-j8  
Traceback (most recent call last):
  File "bin/gub", line 233, in exceptional_build
    build (settings, options, files)
  File "bin/gub", line 229, in build
    b.build_source_packages (names)
  File "bin/../gub/buildrunner.py", line 334, in build_source_packages
    self.spec_build (spec_name)
  File "bin/../gub/buildrunner.py", line 262, in spec_build
    deferred_runner.execute_deferred_commands ()
  File "bin/../gub/runner.py", line 167, in execute_deferred_commands
    cmd.execute (self.logger)
  File "bin/../gub/commands.py", line 75, in execute
    ignore_errors=self.ignore_errors)
  File "bin/../gub/loggedos.py", line 93, in system
    raise misc.SystemFailed (m)
SystemFailed: Command barfed: cd 
/home/fede/src/gub/target/tools/build/glib-2.44.1 && make -j8 
```



Attachments:

- 
[glib.log](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/0002dd45/6474/attachment/glib.log)
 (266.6 kB; text/x-log)


---

** [issues:#5384] Various fixes to GUB:  - update broken download links  - add 
missing dependencies  - fix building of 'make' on glibc 2.27 systems  - teach 
our ancient glibc that make 4.x exists  - minor fixes**

**Status:** Started
**Labels:** GUB 
**Created:** Mon Jul 16, 2018 04:44 PM UTC by Knut Petersen
**Last Updated:** Wed Sep 12, 2018 04:52 PM UTC
**Owner:** Knut Petersen


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 <[email protected]>

http://codereview.appspot.com/369750043


---

Sent from sourceforge.net because [email protected] is 
subscribed to https://sourceforge.net/p/testlilyissues/issues/

To unsubscribe from further messages, a project admin can change settings at 
https://sourceforge.net/p/testlilyissues/admin/issues/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto
  • [Lilypond-... Auto mailings of changes to Lily Issues via Testlilyissues-auto

Reply via email to