Re: Please test gub

[Jahrme Risner]

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Monday, January 28, 2019 4:53 AM, Knut Petersen <address@hidden> wrote:

> Please report success / fails with os / version / cpu info.

Knut, thank you for your coordination of efforts on GUB.

After getting everything downloaded, `time make lilypond` ran for just under 
3h30m.
For reference, I was running Kubuntu 18.04 on a quad-core Intel i5-6500 @ 
3.20GHz.

In addition, my system gcc/g++ version was 7.3.0, and GUB was run using Python 
2.7.15.
In order to get everything working, I performed the following setup:
- Ran `dpkg --add-architecture i386` to enable installing 32-bit libraries 
using apt.
- Installed (using apt):
  - libc-dev:i386
  - libstdc++-dev:i386
  - build-essential
  - python-dev
  - texlive-full

In terms of disk usage, upon completion the `gub/` directory clocked in at 53G, 
namely:
- 669M - downloads/
- 3.7G - regtests/ (included all 2.18 and 2.19 test-output archives currently 
on the website)
- 1.8 - uploads/ (~1.5G of which is documentation)
- 47G - target/ (2.6G for tools, 11G for host platform, ~4-6G for each other 
platform)
A note about this, I added `--keep` to the GUB flags which retains the 
intermediary build directories for inspection.

Also, I have been exploring adding 64-bit macOS (Darwin) targets and I am 
planning on sharing my findings thus far as soon as I have finished writing 
them up.

- Jahrme Risner