Re: Today's GUB failure

path -Wl,/home/gub/NewGub/gub/target/tools/root/usr/lib ' -- Phil Holmes - Original Message - From: "Jonas Hahnfeld" To: "Phil Holmes" ; "Devel" Sent: Sunday, April 26, 2020 12:18 PM Subject: Re: Today's GUB failure

Re: Today's GUB failure

Am Sonntag, den 26.04.2020, 11:25 +0100 schrieb Phil Holmes: > Can anyone help? I'm getting this > > /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/mf/gen-emmentaler.fontforge.py > > line: 2 Undefined variable: import > make[1]: *** [out/emmental

Today's GUB failure

Can anyone help? I'm getting this /home/gub/NewGub/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/mf/gen-emmentaler.fontforge.py line: 2 Undefined variable: import make[1]: *** [out/emmentaler-11.svg] Error 1 make[1]: *** Waiting for unfinished jobs Making m

Re: GUB failure

Am Dienstag, den 07.04.2020, 10:36 +0100 schrieb Phil Holmes: > If I type python-gdbm at the terminal I get "command not found". a) is this > the right way to check? b) I'd appreciate guidance on how best to install > it if I don't have it. It's a packet, not a command. The usual $ apt-get in

Re: GUB failure

ot;Phil Holmes" Cc: "David Kastrup" ; "Devel" Sent: Tuesday, April 07, 2020 10:25 AM Subject: Re: GUB failure

Re: GUB failure

d...@gnu.org > >; "Devel" < > lilypond-devel@gnu.org > > > Sent: Monday, April 06, 2020 5:02 PM > Subject: Re: GUB failure > > > > I bit the bullet and started the upgrade to 16.04. I check that's OK then > > consider 18.04 late

Re: GUB failure

- Original Message - From: "Phil Holmes" To: "Thomas Morley" Cc: "David Kastrup" ; "Devel" Sent: Monday, April 06, 2020 5:02 PM Subject: Re: GUB failure I bit the bullet and started the upgrade to 16.04. I check that's OK then consider

Re: GUB failure

Am Di., 7. Apr. 2020 um 10:18 Uhr schrieb Jonas Hahnfeld : > > Am Dienstag, den 07.04.2020, 10:12 +0200 schrieb Thomas Morley: > > Am Di., 7. Apr. 2020 um 09:50 Uhr schrieb David Kastrup < > > d...@gnu.org > > >: > > > Thomas Morley < > > > thomasmorle...@gmail.com > > > > writes: > > > > > > > Am

Re: GUB failure

Am Dienstag, den 07.04.2020, 10:12 +0200 schrieb Thomas Morley: > Am Di., 7. Apr. 2020 um 09:50 Uhr schrieb David Kastrup < > d...@gnu.org > >: > > Thomas Morley < > > thomasmorle...@gmail.com > > > writes: > > > > > Am Mo., 6. Apr. 2020 um 17:18 Uhr schrieb Thomas Morley > > > < > > > thomasmorle

Re: GUB failure

Am Di., 7. Apr. 2020 um 09:50 Uhr schrieb David Kastrup : > > Thomas Morley writes: > > > Am Mo., 6. Apr. 2020 um 17:18 Uhr schrieb Thomas Morley > > : > > > >> I'll test GUB with current master on my Ubuntu 18.04, though results > >> likely tomorrow... > > > > FWIW, on my 64-bit Ubunu 18.04, I tr

Re: GUB failure

Am Dienstag, den 07.04.2020, 09:50 +0200 schrieb David Kastrup: > Thomas Morley < > thomasmorle...@gmail.com > > writes: > > > Am Mo., 6. Apr. 2020 um 17:18 Uhr schrieb Thomas Morley > > < > > thomasmorle...@gmail.com > > >: > > > > > I'll test GUB with current master on my Ubuntu 18.04, though r

Re: GUB failure

Thomas Morley writes: > Am Mo., 6. Apr. 2020 um 17:18 Uhr schrieb Thomas Morley > : > >> I'll test GUB with current master on my Ubuntu 18.04, though results >> likely tomorrow... > > FWIW, on my 64-bit Ubunu 18.04, I tried to gub-build release/unstable > > (1) gubllb /home/hermann/gub/ /home/her

Re: GUB failure

Am Mo., 6. Apr. 2020 um 17:18 Uhr schrieb Thomas Morley : > I'll test GUB with current master on my Ubuntu 18.04, though results > likely tomorrow... FWIW, on my 64-bit Ubunu 18.04, I tried to gub-build release/unstable (1) gubllb /home/hermann/gub/ /home/hermann/lilypond-git/ release/unstable i

Re: GUB failure

l" Sent: Monday, April 06, 2020 4:18 PM Subject: Re: GUB failure Am Mo., 6. Apr. 2020 um 16:52 Uhr schrieb Phil Holmes : As predicted, GUB has failed to build on my system. The error message shows that it's because I have Python 3.4.3 and I need at least 3.5. If anyone know

Re: GUB failure

Am Mo., 6. Apr. 2020 um 16:52 Uhr schrieb Phil Holmes : > > As predicted, GUB has failed to build on my system. The error message shows > that it's because I have Python 3.4.3 and I need at least 3.5. If anyone > knows how to upgrade my Ubuntu 14 machine to the later Python version, > please say.

Re: GUB failure

On Mon, Apr 6, 2020 at 11:52 PM Phil Holmes wrote: > If anyone knows how to upgrade my Ubuntu 14 machine to the later Python > version, > please say. You can use the deadsnakes ppa (fkrull/deadsnakes for pre Ubuntu-16.04, deadsnakes/ppa

Re: GUB failure

"Phil Holmes" writes: > As predicted, GUB has failed to build on my system. The error message > shows that it's because I have Python 3.4.3 and I need at least 3.5. > If anyone knows how to upgrade my Ubuntu 14 machine to the later > Python version, please say. Otherwise I'll have to upgrade to

GUB failure

As predicted, GUB has failed to build on my system. The error message shows that it's because I have Python 3.4.3 and I need at least 3.5. If anyone knows how to upgrade my Ubuntu 14 machine to the later Python version, please say. Otherwise I'll have to upgrade to Ubuntu 16, which I was avo

Re: Gub failure

Il giorno mer 27 lug 2016 alle 16:08, David Kastrup ha scritto: Federico Bruni writes: Current developers using LilyDev can update this way: 1. Add this line to /etc/apt/sources.list: deb http://httpredir.debian.org/debian testing main 2. Add the file /etc/apt/preferences with the fol

Re: Gub failure

Federico Bruni writes: > Current developers using LilyDev can update this way: > > 1. Add this line to /etc/apt/sources.list: > > deb http://httpredir.debian.org/debian testing main > > > 2. Add the file /etc/apt/preferences with the following content: > > Package: texinfo > Pin: release a=testin

Re: Gub failure

Il giorno mer 27 lug 2016 alle 12:41, Phil Holmes ha scritto: Gub is now updated and uploading. I would suggest that it is not necessary to wait for LilyDev to be updated, since I would certainly not download the whole image just to get an updated version of texinfo. Could we not just add t

Re: Gub failure

"Phil Holmes" writes: > - Original Message - > From: "Werner LEMBERG" > To: > Cc: > Sent: Wednesday, July 27, 2016 5:21 AM > Subject: Re: Gub failure > > >> >>>> I should have made it clear that I asked because my build is

Re: Gub failure

- Original Message - From: "Werner LEMBERG" To: Cc: Sent: Wednesday, July 27, 2016 5:21 AM Subject: Re: Gub failure I should have made it clear that I asked because my build is failing. I’ve got makeinfo version 4.13. That's because Werner pushed changes

Re: Gub failure

Federico Bruni writes: > Il giorno mar 26 lug 2016 alle 19:36, Dan Eble ha > scritto: >> I should have made it clear that I asked because my build is failing. >> I’ve got makeinfo version 4.13. > > Are you sure that you are using LilyDev 3? It is based on Debian > stable (Jessie) and texinfo is

Re: Gub failure

Il giorno mar 26 lug 2016 alle 19:36, Dan Eble ha scritto: I should have made it clear that I asked because my build is failing. I’ve got makeinfo version 4.13. Are you sure that you are using LilyDev 3? It is based on Debian stable (Jessie) and texinfo is version 5.2: https://packages.debia

Re: Gub failure

>> I should have made it clear that I asked because my build is >> failing. I’ve got makeinfo version 4.13. > > That's because Werner pushed changes requiring newer Texinfo syntax. > Werner, can you fix this until systems like Gub and LilyDev 3 can > support it? It is not realistic to expect pe

Re: Gub failure

Dan Eble writes: >> On Jul 26, 2016, at 07:57 , David Kastrup wrote: >> >> Dan Eble writes: >> >>> In LilyDev 3, I’ve tried “sudo apt-get install texinfo” and it tells >>> me “texinfo is already the newest version.” Is there any easier path >>> forward than switching to a new VM? Would the

Re: Gub failure

> On Jul 26, 2016, at 07:57 , David Kastrup wrote: > > Dan Eble writes: > >> In LilyDev 3, I’ve tried “sudo apt-get install texinfo” and it tells >> me “texinfo is already the newest version.” Is there any easier path >> forward than switching to a new VM? Would the latest LilyDev be >> suff

Re: Gub failure

> I've accepted the pull requests on GitHub and updated my system as > above. I'm now getting a failure rebuilding Guile. I've attached the > end of the logfile to avoid problems with line wrapping making the > error messages unintelligible. I've created pull request for fixing guile compilation.

Re: Gub failure

- Original Message - From: "Masamichi Hosoda" To: ; ; ; Sent: Monday, July 25, 2016 3:41 PM Subject: Re: Gub failure Please use 5.x – 4.x is no longer supported. Or even better 6.x. I've created pull request for updating texinfo to 6.1. https://github.com/gperc

Re: Gub failure

Dan Eble writes: > On Jul 24, 2016, at 13:32 , David Kastrup wrote: >> >> Note that even "make" builds a basic non-image version of the Info >> files, and of course with a non-image version, the difference is quite >> noticeable. >> >> At any rate, if we were to update Texinfo, it would likely

Re: Gub failure

On Jul 24, 2016, at 13:32 , David Kastrup wrote: > > Note that even "make" builds a basic non-image version of the Info > files, and of course with a non-image version, the difference is quite > noticeable. > > At any rate, if we were to update Texinfo, it would likely make sense to > take the n

Re: Gub failure

>> Please use 5.x – 4.x is no longer supported. > > Or even better 6.x. I've created pull request for updating texinfo to 6.1. https://github.com/gperciva/gub/pull/25 In my GUB environment, the following commands are succeed. $ bin/gub tools::texinfo $ bin/gub linux-64::lilypond $ bin/gub linux

Re: Gub failure

> Please use 5.x – 4.x is no longer supported. Or even better 6.x. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Gub failure

"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: "Werner LEMBERG" > Cc: ; > Sent: Sunday, July 24, 2016 5:57 PM > Subject: Re: Gub failure > > >> Werner LEMBERG writes: >> >>>>

Re: Gub failure

> OK - so it looks like I should update > https://github.com/gperciva/gub/blob/master/gub/sources.py to a later > version of texinfo - possibly 4.13 to move forward but not risk a > breakage with a new major release? Please use 5.x – 4.x is no longer supported. At least on my box I can easily bu

Re: Gub failure

- Original Message - From: "David Kastrup" To: "Werner LEMBERG" Cc: ; Sent: Sunday, July 24, 2016 5:57 PM Subject: Re: Gub failure Werner LEMBERG writes: Maybe gub still contains an older version? Sorry for not having checked that before committing. In

Re: Gub failure

Werner LEMBERG writes: >> Maybe gub still contains an older version? Sorry for not having >> checked that before committing. > > Indeed, I now see that only texinfo 4.11 is required. > > How to proceed? Reverting is easy (commit > 445bf3bb2fbd1f259fe43ade204fb34d68bdd581, the changes in > `macr

Re: Gub failure

- Original Message - From: "Werner LEMBERG" To: Cc: ; Sent: Sunday, July 24, 2016 5:04 PM Subject: Re: Gub failure Maybe gub still contains an older version? Sorry for not having checked that before committing. Indeed, I now see that only texinfo 4.11 is require

Re: Gub failure

> Maybe gub still contains an older version? Sorry for not having > checked that before committing. Indeed, I now see that only texinfo 4.11 is required. How to proceed? Reverting is easy (commit 445bf3bb2fbd1f259fe43ade204fb34d68bdd581, the changes in `macros.itexi'). However, I would prefer

Re: Gub failure

"Phil Holmes" writes: > Looks like this was the problem. I had to edit the file and push it > to release/unstable since Gub always seems to pull its source files > from there, so editing locally doesn't work. My normal course would > be to push this change to staging once I've uploaded the new

Re: Gub failure

> I now got as far as make doc, when the build failed making > notation.makeinfo, with lots of errors similar to this: > > /home/gub/NewGub/gub/target/linux-x86/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/Documentation/out-www//notation/pitches.texi:4417: > Unknown command `ragge

Re: Gub failure

- Original Message - From: "Phil Holmes" To: "David Kastrup" Cc: Sent: Sunday, July 24, 2016 3:53 PM Subject: Re: Gub failure - Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: Sent: Sunday, July 24, 2016 12:15 PM

Re: Gub failure

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: Sent: Sunday, July 24, 2016 12:15 PM Subject: Re: Gub failure Phil Holmes writes: Trying to build Gub today, I get the following failures: /home/gub/NewGub/gub/target/mingw/src/lil

Re: Gub failure

Phil Holmes writes: > Trying to build Gub today, I get the following failures: > > /home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git- > release-unstable/lily/dynamic-performer.cc: In member function 'Real > Dynamic_performer::compute_departure_volume(Direction, Real, Re

Gub failure

Trying to build Gub today, I get the following failures: /home/gub/NewGub/gub/target/mingw/src/lilypond-git.sv.gnu.org--lilypond.git- release-unstable/lily/dynamic-performer.cc: In member function 'Real Dynamic_performer::compute_departure_volume(Direction, Real, Real, Real, Real)': /home/gub/Ne

Re: Gub failure

Phil, >> make[1]: *** No rule to make target >> `/home/gub/NewGub/gub/target/darwin-ppc/root/usr/include/freetype2/freetype/ftxf86.h', >> needed by `out/pango-font.o'. Stop. >> make[1]: *** Waiting for unfinished jobs > > Ouch. It seems that this is an old pango version that calls FreeTyp

Re: Gub failure

> make[1]: *** No rule to make target > `/home/gub/NewGub/gub/target/darwin-ppc/root/usr/include/freetype2/freetype/ftxf86.h', > needed by `out/pango-font.o'. Stop. > make[1]: *** Waiting for unfinished jobs Ouch. It seems that this is an old pango version that calls FreeType header files

Re: Gub failure

"Phil Holmes" writes: > Attached is a compressed log file. I see lots of warnings but no errors. It does not use the text "error" but there is: make[1]: *** No rule to make target `/home/gub/NewGub/gub/target/darwin-ppc/root/usr/include/freetype2/freetype/ftxf86.h', needed by `out/pango-font

Re: Gub failure

Possibly the file is too large to be posted. Uploaded here: http://philholmes.net/lilypond/lilypond.log.tar.gz -- Phil Holmes - Original Message - From: "Phil Holmes" To: Sent: Wednesday, June 08, 2016 2:32 PM Subject: Gub failure I'm having trouble building

Gub failure

I'm having trouble building Gub again - the output from the logfile doesn't make much sense to me, but I can attach it once I've sent an initial message from Gmane - I appear to be unable to start threads from my mail client. ___ lilypond-devel mailing

Re: GUB failure

David Kastrup writes: > "Phil Holmes" writes: > >> OK - thanks. Should have seen that. The error (one of a few similar) is: >> >> /home/gub/NewGub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/offset.cc:43:25: >> error: 'isinf' was not declared in this

Re: GUB failure

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: Sent: Sunday, October 18, 2015 1:15 PM Subject: Re: GUB failure "Phil Holmes" writes: OK - thanks. Should have seen that. The error (one of a few similar) is: /home/gub/NewGub/gub/

Re: GUB failure

"Phil Holmes" writes: > OK - thanks. Should have seen that. The error (one of a few similar) is: > > /home/gub/NewGub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/offset.cc:43:25: > error: 'isinf' was not declared in this scope > if (!isinf (z2[Y_AXIS]

Re: GUB failure

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: Sent: Sunday, October 18, 2015 12:43 PM Subject: Re: GUB failure Phil Holmes writes: I'm getting the following failure running a GUB build: /home/gub/NewGub/gub/target/darwin-ppc/sr

Re: GUB failure

Phil Holmes writes: > I'm getting the following failure running a GUB build: > > /home/gub/NewGub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org-- > lilypond.git-release-unstable/flower/warn.cc:114:49: warning: format '%d' > expects argument of type 'int', but argument 2 has type > 'std::vect

GUB failure

I'm getting the following failure running a GUB build: /home/gub/NewGub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org-- lilypond.git-release-unstable/flower/warn.cc:114:49: warning: format '%d' expects argument of type 'int', but argument 2 has type 'std::vector >::size_type {aka long unsigne

Re: Resending: further GUB failure

[snip all] Thanks. GUB is now built and will be uploaded this evening. -- Phil Holmes ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Resending: further GUB failure

"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: "Phil Holmes" > >> I consider it a bad idea to have those changes in a release without >> having them in master. I think what you want to do here is to back out >> those changes again since they were required a

Re: Resending: further GUB failure

- Original Message - From: "David Kastrup" To: "Phil Holmes" I consider it a bad idea to have those changes in a release without having them in master. I think what you want to do here is to back out those changes again since they were required as a consequence of issue 4550 which ha

Re: Different GUB failure

- Original Message - From: "Masamichi HOSODA" To: Cc: Sent: Tuesday, August 25, 2015 3:39 PM Subject: Re: Different GUB failure You are right. I've found a problem. lilypond.make's doc and test-output uses offline mode. So dependency files are not downloaded

Re: Different GUB failure

The Darwin-PPC compile now proceeds fine following the revert. I'm now getting a failure to build the daja-vu fonts: it looks like the font file has not been downloaded: invoking tar -C /home/gub/NewGub/gub/target/tools/src/fonts-dejavu-2.35 --strip-com

Re: Different GUB failure

- Original Message - From: "Masamichi HOSODA" To: Cc: Sent: Tuesday, August 25, 2015 3:04 PM Subject: Re: Different GUB failure The Darwin-PPC compile now proceeds fine following the revert. I'm now getting a failure to build the daja-vu fonts: it looks like the fo

Re: Different GUB failure

>> The Darwin-PPC compile now proceeds fine following the revert. I'm >> now >> getting a failure to build the daja-vu fonts: it looks like the font >> file >> has not been downloaded: >> >> invoking tar -C >> /home/gub/NewGub/gub/target/tools/src/fonts-dejavu-2.35 >> --strip-component=1 -v -j -xf

Re: Different GUB failure

- Original Message - From: "Phil Holmes" To: Sent: Monday, August 24, 2015 3:10 PM Subject: Different GUB failure The Darwin-PPC compile now proceeds fine following the revert. I'm now getting a failure to build the daja-vu fonts: it looks like the font file has not

Re: Different GUB failure

Masamichi HOSODA sea.plala.or.jp> writes: > > > The Darwin-PPC compile now proceeds fine following the revert. I'm now > > getting a failure to build the daja-vu fonts: it looks like the font file > > has not been downloaded: > > > > invoking tar -C /home/gub/NewGub/gub/target/tools/src/fonts-

Re: Resending: further GUB failure

Phil Holmes writes: > The Darwin-PPC compile now proceeds fine following the revert. I'm now > getting a failure to build the daja-vu fonts: it looks like the font file > has not been downloaded: > > invoking tar -C /home/gub/NewGub/gub/target/tools/src/fonts-dejavu-2.35 > --strip-component=1 -v

Re: Different GUB failure

> The Darwin-PPC compile now proceeds fine following the revert. I'm now > getting a failure to build the daja-vu fonts: it looks like the font file > has not been downloaded: > > invoking tar -C /home/gub/NewGub/gub/target/tools/src/fonts-dejavu-2.35 > --strip-component=1 -v -j -xf /home/gub/New

Resending: further GUB failure

The Darwin-PPC compile now proceeds fine following the revert. I'm now getting a failure to build the daja-vu fonts: it looks like the font file has not been downloaded: invoking tar -C /home/gub/NewGub/gub/target/tools/src/fonts-dejavu-2.35 --strip-component=1 -v -j -xf /home/gub/NewGub/gub/down

Different GUB failure

The Darwin-PPC compile now proceeds fine following the revert. I'm now getting a failure to build the daja-vu fonts: it looks like the font file has not been downloaded: invoking tar -C /home/gub/NewGub/gub/target/tools/src/fonts-dejavu-2.35 --strip-component=1 -v -j -xf /home/gub/NewGub/gub/down

Re: Further GUB failure

Dan Eble writes: > David wrote: >> isinf is supposed to be defined in cmath (without scoping) which is >> included by flower/include/offset.hh. And of course this works on most >> platforms or we'd have gotten complaints already. > > What’s your source? I tried interpreting the last draft C++11

Re: Further GUB failure

David wrote: > isinf is supposed to be defined in cmath (without scoping) which is > included by flower/include/offset.hh. And of course this works on most > platforms or we'd have gotten complaints already. What’s your source? http://en.cppreference.com/w/cpp/numeric/math/isinf shows that the

Re: Further GUB failure

"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: "Phil Holmes" > Cc: > Sent: Sunday, August 23, 2015 4:00 PM > Subject: Re: Further GUB failure > > >> Phil Holmes writes: >> >>> I&#

Re: Further GUB failure

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: Sent: Sunday, August 23, 2015 4:00 PM Subject: Re: Further GUB failure Phil Holmes writes: I'm now getting this error: /home/gub/NewGub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.o

Re: Further GUB failure

Phil Holmes writes: > I'm now getting this error: > > /home/gub/NewGub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org-- > lilypond.git-release-unstable/flower/offset.cc:43:25: error: 'isinf' was not > declared in this scope >if (!isinf (z2[Y_AXIS])) > ^ > > It look

Re: Further GUB failure

> I'm now getting this error: > > /home/gub/NewGub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org-- > lilypond.git-release-unstable/flower/offset.cc:43:25: error: 'isinf' was not > declared in this scope >if (!isinf (z2[Y_AXIS])) > ^ > > It looks like the compiler

Further GUB failure

I'm now getting this error: /home/gub/NewGub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org-- lilypond.git-release-unstable/flower/offset.cc:43:25: error: 'isinf' was not declared in this scope if (!isinf (z2[Y_AXIS])) ^ It looks like the compiler cannot find isinf,

Re: GUB failure

- Original Message - From: "Masamichi HOSODA" To: Cc: Sent: Sunday, August 23, 2015 12:52 PM Subject: Re: GUB failure Following the changes to the fonts, I'm now having GUB fail. The log shows: configure: WARNING: unrecognized options: --enable-shared, -

Re: GUB failure

> Following the changes to the fonts, I'm now having GUB fail. The log shows: > > configure: WARNING: unrecognized options: --enable-shared, --disable-static, > --disable-silent-rules, --with-fonts-dir > > WARNING: Please consider installing optional programs or files: dblatex > > ERROR: Pleas

GUB failure

Following the changes to the fonts, I'm now having GUB fail. The log shows: configure: WARNING: unrecognized options: --enable-shared, --disable-static, --disable-silent-rules, --with-fonts-dir WARNING: Please consider installing optional programs or files: dblatex ERROR: Please install requir

Re: GUB failure in parser.yy

"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: "Phil Holmes" > Cc: "Devel" > Sent: Saturday, September 22, 2012 6:38 PM > Subject: Re: GUB failure in parser.yy > > >> "Phil Ho

Re: GUB failure in parser.yy

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "Devel" Sent: Saturday, September 22, 2012 6:38 PM Subject: Re: GUB failure in parser.yy "Phil Holmes" writes: My preference _right now_ would be to remove the code that'

Re: GUB failure in parser.yy

"Phil Holmes" writes: > My preference _right now_ would be to remove the code that's causing > the old version of Bison a problem. To fix Gub, rebuild Gub and then > rebuild lilypond would take considerable time which I don't have now. > I'd like to get an updated version of lilypond out over th

Re: GUB failure in parser.yy

- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "Devel" Sent: Saturday, September 22, 2012 4:56 PM Subject: Re: GUB failure in parser.yy "Phil Holmes" writes: I'm trying to build 2.17.3. I get this failure: mak

Re: GUB failure in parser.yy

"Phil Holmes" writes: > I'm trying to build 2.17.3. I get this failure: > > make[1]: Entering directory > /home/gub/gub/target/darwin-ppc/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily' > bison -o out/parser-tmp.cc -d > /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.

GUB failure in parser.yy

I'm trying to build 2.17.3. I get this failure: make[1]: Entering directory `/home/gub/gub/target/darwin-ppc/build/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/lily' bison -o out/parser-tmp.cc -d /home/gub/gub/target/darwin-ppc/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstab

Re: GUB failure

- Original Message - From: "Graham Percival" To: "Phil Holmes" Cc: "Devel" Sent: Tuesday, February 14, 2012 6:26 PM Subject: Re: GUB failure On Tue, Feb 14, 2012 at 04:40:54PM -, Phil Holmes wrote: ERROR: ld.so: object '/home/gub/gub/targe

Re: GUB failure

On Tue, Feb 14, 2012 at 04:40:54PM -, Phil Holmes wrote: > ERROR: ld.so: object > '/home/gub/gub/target/tools/root/usr/lib/librestrict.so' from > LD_PRELOAD cannot be preloaded: ignored. hmm. > Command barfed: tar -C /home/gub/gub/target/darwin-x86/installer > -zxf What happens when you run

Re: GUB failure

t;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/c

GUB failure

Not feeling too good today (cold) so I thought I'd do something not too mentally taxing - another go at building GUB. I've created a new user just for this, and git cloned the GUB repo. make bootstrap was fine, but make lilyond ended with this. Anyone any ideas? ERROR: ld.so: object '/home

GUB failure in tools::gzip

Hi Jan, I'm getting a build failure at the compile stage for gzip which is caused by a naming conflict with glibc's futimens () function: In file included from ./sys/stat.h:27, from ./fcntl.h:26, from /home/neil/gub/target/tools/src/gzip-1.3.12/lib/utimens.c:29:

gub failure

hi, make download fails, giving a 404 on http://lilypond.org/download/v2.11/ -- Erik ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel