Knut, I'm testing your patch on Fedora 28.

When building glibc (during the `make bootstrap` step), 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 -p1` and 
committed to this branch:
https://github.com/fedelibre/gub/tree/5384-knut-patch

~~~~
$ target/tools/root/usr/bin/make --version
GNU Make 3.81

$ make --version
GNU Make 4.2.1
~~~~

These lines are taken from `target/linux-64/build/glibc-core-2.3/config.log` 
(full file attached):

~~~~
configure:4112: checking for gmake
configure:4128: found /usr/bin/gmake
configure:4138: result: gmake
configure:4152: checking version of gmake
configure:4162: result: 4.2.1, bad
...
configure:4261: result: makeinfo
configure:4275: checking version of makeinfo
configure:4285: result: 6.1, bad
...
*** These critical programs are missing or too old: make
*** Check the INSTALL file for required versions.
...
MAKE='gmake'
MAKEINFO=':'
~~~~

And this is the tail of `make bootstrap`:

~~~~
building package: linux-64::cross/gcc-core
 *** Stage: download (cross/gcc-core, linux-64)
 *** Stage: untar (cross/gcc-core, linux-64)
 *** Stage: patch (cross/gcc-core, linux-64)
 *** Stage: autoupdate (cross/gcc-core, linux-64)
 *** Stage: configure (cross/gcc-core, linux-64)
 *** Stage: compile (cross/gcc-core, linux-64)
 *** Stage: install (cross/gcc-core, linux-64)
 *** Stage: package (cross/gcc-core, linux-64)
 *** Stage: clean (cross/gcc-core, linux-64)
 *** Stage: pkg_install (cross/gcc-core, linux-64)

This compile has previously been interrupted.
To ensure a repeatable build, this will not be packaged.

Run with

    --fresh # or issue
              rm 
/home/fede/src/gub/target/linux-64/status/glibc-core-2.3-glibc-2.3-20070416

to force a full package rebuild, or

    --force-package

to skip this check and risk a defective build.
building package: linux-64::glibc-core
 *** Stage: download (glibc-core, linux-64)
 *** Stage: configure (glibc-core, linux-64)
Command barfed: cd /home/fede/src/gub/target/linux-64/build/glibc-core-2.3 && 
chmod +x /home/fede/src/gub/target/linux-64/src/glibc-core-2.3/configure && 
BUILD_CC=gcc  sh 
/home/fede/src/gub/target/linux-64/src/glibc-core-2.3/configure --prefix=/usr 
--cache-file=config.cache --enable-shared --disable-static 
--disable-silent-rules --build=x86_64-linux --host=x86_64-linux 
--target=x86_64-linux --prefix=/usr --sysconfdir=/usr/etc 
--includedir=/usr/include --infodir=/usr/share/info --mandir=/usr/share/man 
--libdir=/usr/lib  --disable-profile --disable-debug --without-cvs --without-gd 
--with-headers=/home/fede/src/gub/target/linux-64/root/usr/include  
--enable-add-ons=linuxthreads --without-tls --without-__thread 

Tail of target/linux-64/log/glibc-core.log >>>>>>>>
    configure: error:
    *** These critical programs are missing or too old: make
    *** Check the INSTALL file for required versions.
    Command barfed: cd /home/fede/src/gub/target/linux-64/build/glibc-core-2.3 
&& chmod +x /home/fede/src/gub/target/linux-64/src/glibc-core-2.3/configure && 
BUILD_CC=gcc  sh 
/home/fede/src/gub/target/linux-64/src/glibc-core-2.3/configure --prefix=/usr 
--cache-file=config.cache --enable-shared --disable-static 
--disable-silent-rules --build=x86_64-linux --host=x86_64-linux 
--target=x86_64-linux --prefix=/usr --sysconfdir=/usr/etc 
--includedir=/usr/include --infodir=/usr/share/info --mandir=/usr/share/man 
--libdir=/usr/lib  --disable-profile --disable-debug --without-cvs --without-gd 
--with-headers=/home/fede/src/gub/target/linux-64/root/usr/include  
--enable-add-ons=linuxthreads --without-tls --without-__thread
<<<<<<<< Tail of target/linux-64/log/glibc-core.log

*** Failed target: linux-64::glibc-core
make: *** [compilers.make:44: cross-compilers] Error 1
~~~~

The `patches/glibc-allow-make4.patch` file seems to be applied. I've checked 
the relevant lines in this file:

~~~~
nano +4154 src/glibc-core-2.3/configure
~~~~


Attachments:

- 
[config.log](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/0002dd45/f4ce/attachment/config.log)
 (34.4 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:** Mon Aug 27, 2018 03:41 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
  • [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