Success for linux-64 target in GUB! Thank you very much, Dan. I did not
test the other targets yet, however.
It produces a usable lilypond installer which compiled a test example fine.
Am 11.01.2020 um 00:14 schrieb Dan Eble:
On Jan 10, 2020, at 16:21, Dan Eble mailto:d...@faithful.be>> wrote:
On Jan 10, 2020, at 16:21, Dan Eble wrote:
>
> It seems that this implementation of the standard library declares ::isinf
> when is included. The three solutions I can think of are (a)
> finish issue 4550, (b) require a version of the library that does not do
> this, or (c) investigate wheth
On Jan 10, 2020, at 15:52, Michael Käppler wrote:
>
> Hi Dan,
> GUB still fails to build lilypond in offset.cc. See attached log.
> Anyone out here using LilyDev1, who can build current master through GUB?
> Now testing, if I can build release/unstable.
>
> What I would like to understand is why
Hi Dan,
GUB still fails to build lilypond in offset.cc. See attached log.
Anyone out here using LilyDev1, who can build current master through GUB?
Now testing, if I can build release/unstable.
What I would like to understand is why this issue does arise only within
GUB and
not for a normal build
Hi Dan,
will test it, thank you very much!
Am 09.01.2020 um 22:49 schrieb Dan Eble:
On Jan 9, 2020, at 10:09, Dan Eble wrote:
On Jan 9, 2020, at 07:32, Michael Käppler wrote:
/home/dev/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/flower/offset.cc:132:23:
error: call o
On Jan 9, 2020, at 10:09, Dan Eble wrote:
>
> On Jan 9, 2020, at 07:32, Michael Käppler wrote:
>>
>> /home/dev/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/flower/offset.cc:132:23:
>> error: call of overloaded 'isinf(Real&)' is ambiguous
>> if (isinf (d[X_AXIS]))
>
>
On Jan 9, 2020, at 07:32, Michael Käppler wrote:
>
> /home/dev/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/flower/offset.cc:132:23:
> error: call of overloaded 'isinf(Real&)' is ambiguous
>if (isinf (d[X_AXIS]))
Maybe it's time to take another shot at issue 4550, "Av
Sorry, I did not look carefully enough. It does fail when trying
to build flower/offset.cc
The error is:
/home/dev/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/flower/offset.cc:132:23:
error: call of overloaded 'isinf(Real&)' is ambiguous
if (isinf (d[X_AXIS]))
Now tryi
Hi all,
I'm trying to build a lilypond installer with GUB, up to now with no
success.
It does fail when trying to build python.
My setup:
LilyDev 1 (the current release), running in VirtualBox with Win10 as
host system.
What I did was:
/home/dev/setup.sh
cd /home/dev/gub
bin/gub lilypond-installe
> On 22 Dec 2016, at 18:20, Hans Aikema wrote:
>
>
>
> Retrying a CentOS build alongside trial-and-error builds with minimal Ubuntu
> environment
CentOS-7 builds won’t fly for now due to outdated metapost in its repo….
ERROR: Please install required programs: mpost (due to a bug in metapos
> On 22 Dec 2016, at 18:20, Hans Aikema wrote:
>
>
>> On 22 Dec 2016, at 14:05, Masamichi Hosoda wrote:
>>
>> In my environments, autoconf does not raise such error.
>> Do you set the "set -u" or "set -o nounset" somewhere?
>> If so, would you remove the setting?
> The set -u
> On 22 Dec 2016, at 14:05, Masamichi Hosoda wrote:
>
> In my environments, autoconf does not raise such error.
> Do you set the "set -u" or "set -o nounset" somewhere?
> If so, would you remove the setting?
The set -u (or to be complete set -ux) I discovered inside
/
In my environments, autoconf does not raise such error.
Do you set the "set -u" or "set -o nounset" somewhere?
If so, would you remove the setting?
>>> The set -u (or to be complete set -ux) I discovered inside
>>>
>>> /home/gub/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--li
- Original Message -
From: "Masamichi Hosoda"
To:
Cc:
Sent: Saturday, December 17, 2016 3:14 PM
Subject: Re: linux-ppc harfbuzz GUB build error
I've updated my GUB environment and the build fails. Please see the
attached zipped logfile.
Perhaps gcc has upgraded
> I've updated my GUB environment and the build fails. Please see the
> attached zipped logfile.
Perhaps gcc has upgraded but libtool has not been updated.
Does the folowing command
$ /home/gub/NewGub/gub/target/mingw/root/usr/cross/bin/i686-mingw32-gcc
--version
show 4.9.4?
And, does the foll
>>> In my environments, autoconf does not raise such error.
>>> Do you set the "set -u" or "set -o nounset" somewhere?
>>> If so, would you remove the setting?
>> The set -u (or to be complete set -ux) I discovered inside
>>
>> /home/gub/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--lilypond
>>> Maybe the issue is to use ICU of CentOS system.
>>>
>>> I've created a patch.
>>> https://github.com/trueroad/gub/commit/081cc91f698186795dca45e8d6db8af6616826d4
>>>
>>> If this patch solves the issue, I will send the pull request.
>>
>> New gub bootstrapped from you repo; running a trialbui
>> In my environments, autoconf does not raise such error.
>> Do you set the "set -u" or "set -o nounset" somewhere?
>> If so, would you remove the setting?
> The set -u (or to be complete set -ux) I discovered inside
>
> /home/gub/gub/target/freebsd-x86/src/lilypond-git.sv.gnu.org--lilypond.git-m
> On 14 Dec 2016, at 18:22, Hans Aikema wrote:
>
>
>> On 14 Dec 2016, at 14:56, Hans Aikema wrote:
>>
>>
>>> On 14 Dec 2016, at 14:30, Masamichi Hosoda wrote:
>>>
>>
> <..>
> will do some more digging inside autoconf to see if I can spot any reason why
> CONFIG_SHELL would not be set
> On 14 Dec 2016, at 14:56, Hans Aikema wrote:
>
>
>> On 14 Dec 2016, at 14:30, Masamichi Hosoda wrote:
>>
> New build from Masamichi’s branch passed the linux ppc harfbuzz, so the
> ICU patch worked. Now looking into a breaking freebsd-x86 lilypond error:
Would you show
> On 14 Dec 2016, at 14:30, Masamichi Hosoda wrote:
>
New build from Masamichi’s branch passed the linux ppc harfbuzz, so the
ICU patch worked. Now looking into a breaking freebsd-x86 lilypond error:
>>>
>>> Would you show me the whole log file?
>> Went into a bit of experimentation
>>> New build from Masamichi’s branch passed the linux ppc harfbuzz, so the ICU
>>> patch worked. Now looking into a breaking freebsd-x86 lilypond error:
>>
>> Would you show me the whole log file?
> Went into a bit of experimentation afterwards, still failed attempts only,
> after discovering
> On 14 Dec 2016, at 12:28, Masamichi Hosoda wrote:
>
>> New build from Masamichi’s branch passed the linux ppc harfbuzz, so the ICU
>> patch worked. Now looking into a breaking freebsd-x86 lilypond error:
>
> Would you show me the whole log file?
Went into a bit of experimentation afterwards
> New build from Masamichi’s branch passed the linux ppc harfbuzz, so the ICU
> patch worked. Now looking into a breaking freebsd-x86 lilypond error:
Would you show me the whole log file?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://l
> On 13 Dec 2016, at 01:20, Hans Aikema wrote:
>
> On 12 Dec 2016, at 15:41, Masamichi Hosoda wrote:
>>
>> <…>
>> Maybe the issue is to use ICU of CentOS system.
>>
>> I've created a patch.
>> https://github.com/trueroad/gub/commit/081cc91f698186795dca45e8d6db8af6616826d4
>>
>> If this patch
On 12 Dec 2016, at 15:41, Masamichi Hosoda wrote:
>
>> 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.
> 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 m
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 environ
> 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
>> librestri
> 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
> /d
> 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 :)
>
31 matches
Mail list logo
