Re: linux-ppc harfbuzz GUB build error

[Graham Percival]

On Sun, Dec 11, 2016 at 04:44:40PM +0100, Hans Aikema wrote:
> 
> The official requirements for building:
> INSTALLING
> 
> * You need
>   - about 9 GB of free space (for all platforms)
>   - standard unix shell utilities: cat, cp, install, mv, rm, sed, ...
>   - a standard unix development environment with GCC and G++
>   - Python 2.4 or newer (2.5, 2.6, 3.0 are known to work)
> 
> are rather vague (on points 2 and 3) and in a Dockerized linux env you 
> usually have the bare minimum available and all else needs to be added. Hence 
> the /usr/bin/file was missing on my system. On a regular CentOS I assume it 
> would’ve been present.

Yes, absolutely.  I've begun expanding the definition of "standard
unix development environment" in the README; please make a branch
and add to that list as you discover more missing items.  We seem
to have more interest in GUB these days, so making it easier to
get started would be great.  :)

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: linux-ppc harfbuzz GUB build error

[Hans Aikema]

> On 11 Dec 2016, at 15:54, Masamichi Hosoda  wrote:
> 
>> I hope someone can shed a light on what I’m doing wrong here.
>> 
>> librestrict:error:/home/gub/gub/target/linux-ppc/root/usr/cross/libexec/gcc/powerpc-linux/4.9.4/cc1plus:
>>  tried to open () file /usr/include/stdc-predef.h
>> librestrict:allowed:
>>  /home/gub/gub/target/linux-ppc
>>  /tmp
>>  /dev/null
>>  /dev/urandom
>>  /proc/self
>> :0:0: internal compiler error: Aborted
>> 
>> 
>> Full harfbuzz.log attached
> 
> My GUB environments are Ubuntu 14.04 LTS 64 bit and Ubuntu 16.04 LTS 64bit.
> I have never used GUB on CentOS.
> But, your log file has the following line.
> 
> /home/gub/gub/target/linux-ppc/src/harfbuzz-1.3.0/configure: line 7264: 
> /usr/bin/file: No such file or directory
> 
> Does your system have /usr/bin/file ?
> My system has it and my log file does not have that line.
Masamichi, 

/usr/bin/file was indeed not yet present on my system. Added it to the mix and 
retrying a build.

Meanwhile took a look on the rest of the logfile and spotted a bunch of 
“checking <….>… no”… any of those a concern in your experience?

checking for powerpc-linux-dlltool... no
checking for dlltool... no
checking for sysroot... no
checking for powerpc-linux-mt... no
checking for mt... no
checking if : is a manifest tool... no
checking if powerpc-linux-gcc  supports -fno-rtti -fno-exceptions... no
checking whether -lc should be explicitly linked in... no
checking whether to build static libraries... no
checking for gtk-doc... no
checking for gtkdoc-check... no
checking for gtkdoc-check... no
checking for gtkdoc-rebase... no
checking for gtkdoc-mkpdf... no
checking whether to build gtk-doc documentation... no
checking for native Win32... no
checking for the pthreads library -lpthreads... no
checking whether pthreads work without any flags... no
checking whether pthreads work with -Kthread... no
checking whether pthreads work with -kthread... no
checking for the pthreads library -llthread... no
checking if more special flags are required for pthreads... no
checking for PTHREAD_PRIO_INHERIT... no
checking for FONTCONFIG... no
checking for ICU... no
checking for powerpc-linux-icu-config... no


 

The official requirements for building:
INSTALLING

* You need
  - about 9 GB of free space (for all platforms)
  - standard unix shell utilities: cat, cp, install, mv, rm, sed, ...
  - a standard unix development environment with GCC and G++
  - Python 2.4 or newer (2.5, 2.6, 3.0 are known to work)

are rather vague (on points 2 and 3) and in a Dockerized linux env you usually 
have the bare minimum available and all else needs to be added. Hence the 
/usr/bin/file was missing on my system. On a regular CentOS I assume it 
would’ve been present.

Thanks for looking into it…. will keep trying (and will look closer to 
log-files before errors start appearing when I run into trouble as there might 
be more obvious items missing that are present in a regular base linux install)

regards,
Hans
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: linux-ppc harfbuzz GUB build error

[Masamichi Hosoda]

> I hope someone can shed a light on what I’m doing wrong here.
> 
> librestrict:error:/home/gub/gub/target/linux-ppc/root/usr/cross/libexec/gcc/powerpc-linux/4.9.4/cc1plus:
>  tried to open () file /usr/include/stdc-predef.h
> librestrict:allowed:
>   /home/gub/gub/target/linux-ppc
>   /tmp
>   /dev/null
>   /dev/urandom
>   /proc/self
> :0:0: internal compiler error: Aborted
> 
> 
> Full harfbuzz.log attached

My GUB environments are Ubuntu 14.04 LTS 64 bit and Ubuntu 16.04 LTS 64bit.
I have never used GUB on CentOS.
But, your log file has the following line.

/home/gub/gub/target/linux-ppc/src/harfbuzz-1.3.0/configure: line 7264: 
/usr/bin/file: No such file or directory

Does your system have /usr/bin/file ?
My system has it and my log file does not have that line.
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

linux-ppc harfbuzz GUB build error (was Re: Trialling with GUB & Docker I got stuck trying to bootstrap GUB @darwin-ppc::odcctools)

[Hans Aikema]

> On 10 Dec 2016, at 22:51, Hans Aikema  wrote:
> 
<…>
> glibc.i686 was the last package to get it fixed…. succesfully bootstrapped 
> GUB. Now my Mac is humming on while GUB is running a make lilypond inside the 
> container. From the notes on the webpage I expect this will take some time :)
> 

After installing various other libs (among others unzip) it was chumming nicely 
until it hit the linux-ppc build for harfbuzz. There it hit an error that makes 
me wonder if I maybe installed too much causing it to find local header files 
when it should find GUB based header files…. but then again… I would assume the 
GUB include folders are consulted before the system includes...

I hope someone can shed a light on what I’m doing wrong here.

librestrict:error:/home/gub/gub/target/linux-ppc/root/usr/cross/libexec/gcc/powerpc-linux/4.9.4/cc1plus:
 tried to open () file /usr/include/stdc-predef.h
librestrict:allowed:
  /home/gub/gub/target/linux-ppc
  /tmp
  /dev/null
  /dev/urandom
  /proc/self
:0:0: internal compiler error: Aborted


Full harfbuzz.log attached


harfbuzz.log.gz
Description: GNU Zip compressed data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCHES: Countdown for December 11th

[James Lowe]

Hello,

Here is the current patch countdown list. The next countdown
will be on December 14th.

A quick synopsis of all patches currently in the review process can be
found here:

http://Philholmes.net/lilypond/allura/


__



Push:
5007 Proposed additional info for Contributor's Guide 6.1, Introduction
to website work - Graham Percival
https://sourceforge.net/p/testlilyissues/issues/5007
http://codereview.appspot.com/315130043


5003 unfoldRepeats can be restricted to certain repeat-types - Thomas Morley
https://sourceforge.net/p/testlilyissues/issues/5003
http://codereview.appspot.com/318890043



Countdown: No patches on Countdown at this time.


Review: No Patches in Review at this time.


New:


5009 website fix typo
https://sourceforge.net/p/testlilyissues/issues/5009
http://codereview.appspot.com/318060043


5004 Doc: CG - Add Graham to Bug Squad list - Graham Percival
https://sourceforge.net/p/testlilyissues/issues/5004
http://codereview.appspot.com/313160043



Waiting:


4600 Let notes/rests suppress multi-measure rest grobs - Dan Eble
https://sourceforge.net/p/testlilyissues/issues/4600
http://codereview.appspot.com/265160043



Regards


James

___

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: guile-2.0 and debian

[Dr. Tobias Quathamer]

Am 07.12.2016 um 15:28 schrieb Federico Bruni:

Il giorno mer 7 dic 2016 alle 13:34, Dr. Tobias Quathamer
 ha scritto:

The link points to the obsolete dependencies. You'll want this link
instead:



This has an updated fonts package list as well.


Thanks for the link.

The fonts package list is really updated? I ask because it includes
some dummy transitional packages, e.g. ttf-dejavu, which has been
replaced by fonts-dejavu IIUC.

Yesterday I was building a debian image with live-build, which failed
to install ttf-dejavu. Should I use fonts-dejavu?


Hi,

sorry for the late answer. Yes, please use fonts-dejavu and 
fonts-freefont-ttf instead of ttf-dejavu and ttf-freefont. The link 
above has now been updated with this change as well.


Regards,
Tobias




signature.asc
Description: OpenPGP digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel