Re: Lilypond build dependency tlasm

2022-09-07 Thread David Kastrup
Immanuel Litzroth writes: >> On Wed, Sep 7, 2022 at 12:02 PM David Kastrup wrote: >>> >>> But "is this a good idea?" is something people should really consider >>> when coining terms that other people will have to use as a reference. > > In this case the problem seems the font used rather than

Re: Lilypond build dependency tlasm

2022-09-07 Thread Immanuel Litzroth
In this case the problem seems the font used rather than in the naming. Immanuel On Wed, Sep 7, 2022 at 12:02 PM David Kastrup wrote: > > Lukas-Fabian Moser writes: > > > Hi Andrew, > > > > Am 07.09.22 um 10:19 schrieb Andrew Bernard: > >> I cant find out what tlasm is. It's a missing

Re: Lilypond build dependency tlasm

2022-09-07 Thread David Kastrup
Lukas-Fabian Moser writes: > Hi Andrew, > > Am 07.09.22 um 10:19 schrieb Andrew Bernard: >> I cant find out what tlasm is. It's a missing dependency for the >> build. Google's indexing of billions of pages produces nothing, >> unless I am dreaming. Could somebody help me understand what this >>

Re: Lilypond build dependency tlasm

2022-09-07 Thread Lukas-Fabian Moser
Hi Andrew, Am 07.09.22 um 10:19 schrieb Andrew Bernard: I cant find out what tlasm is. It's a missing dependency for the build. Google's indexing of billions of pages produces nothing, unless I am dreaming. Could somebody help me understand what this program is and where to find it?

Re: Lilypond build dependency tlasm

2022-09-07 Thread Jean Abou Samra
> Le 07/09/2022 10:19 CEST, Andrew Bernard a écrit  > : > > > I cant find out what tlasm is. It's a missing dependency for the build. > Google's indexing of billions of pages produces nothing, unless I am > dreaming. Could somebody help me understand what this program is and > where to find

Re: Lilypond build dependency tlasm

2022-09-07 Thread Kevin Barry
I have no issues when I Google it. Did you search for tlasm or t1asm? Kevin On Wed 7 Sept 2022, 09:51 Andrew Bernard, wrote: > I cant find out what tlasm is. It's a missing dependency for the build. > Google's indexing of billions of pages produces nothing, unless I am > dreaming. Could

Re: Lilypond build dependency tlasm

2022-09-07 Thread Andrew Bernard
Oh dear. It's t-one-asm, not t-ell-asm. Sorry for the noise. On 7/09/2022 6:19 pm, Andrew Bernard wrote: I cant find out what tlasm is. It's a missing dependency for the build. Google's indexing of billions of pages produces nothing, unless I am dreaming. Could somebody help me understand

Re: Lilypond build dependency tlasm

2022-09-07 Thread Aaron Hill
On 2022-09-07 1:19 am, Andrew Bernard wrote: I cant find out what tlasm is. It's a missing dependency for the build. Google's indexing of billions of pages produces nothing, unless I am dreaming. Could somebody help me understand what this program is and where to find it? ../configure outputs:

Lilypond build dependency tlasm

2022-09-07 Thread Andrew Bernard
I cant find out what tlasm is. It's a missing dependency for the build. Google's indexing of billions of pages produces nothing, unless I am dreaming. Could somebody help me understand what this program is and where to find it? ../configure outputs: ERROR: Please install required programs: 

Re: Lilypond build

2020-09-22 Thread Michael Käppler
Am 18.09.2020 um 16:05 schrieb Federico Bruni: [snip] (./Documentation/out-www/it/web.texi (/usr/share/texlive/texmf-dist/tex/texinfo/texinfo.tex Loading texinfo [version 2019-09-20.22]: pdf, fonts, markup, glyphs, page headings, tables, conditionals, indexing, sectioning, toc, environments,

Re: Lilypond build

2020-09-18 Thread Federico Bruni
Il giorno ven 18 set 2020 alle 10:18, Michael Käppler ha scritto: Am 18.09.2020 um 00:49 schrieb Federico Bruni: Il giorno mer 16 set 2020 alle 15:39, Michael Käppler ha scritto: Am 16.09.2020 um 13:45 schrieb Michael Käppler: Am 16.09.2020 um 12:18 schrieb Federico Bruni: Il giorno

Re: Lilypond build

2020-09-18 Thread Michael Käppler
Am 18.09.2020 um 00:49 schrieb Federico Bruni: Il giorno mer 16 set 2020 alle 15:39, Michael Käppler ha scritto: Am 16.09.2020 um 13:45 schrieb Michael Käppler: Am 16.09.2020 um 12:18 schrieb Federico Bruni: Il giorno sab 12 set 2020 alle 15:13, Jonas Hahnfeld ha scritto: I think right

Re: Lilypond build

2020-09-17 Thread Federico Bruni
Il giorno mer 16 set 2020 alle 15:39, Michael Käppler ha scritto: Am 16.09.2020 um 13:45 schrieb Michael Käppler: Am 16.09.2020 um 12:18 schrieb Federico Bruni: Il giorno sab 12 set 2020 alle 15:13, Jonas Hahnfeld ha scritto: I think right now it makes most sense to just release 2.21.6

Re: Lilypond build

2020-09-16 Thread Michael Käppler
Am 16.09.2020 um 13:45 schrieb Michael Käppler: Am 16.09.2020 um 12:18 schrieb Federico Bruni: Il giorno sab 12 set 2020 alle 15:13, Jonas Hahnfeld ha scritto: I think right now it makes most sense to just release 2.21.6 as a "normal" unstable release, without any extra wording. The issue

Re: Lilypond build

2020-09-16 Thread Michael Käppler
Am 16.09.2020 um 12:18 schrieb Federico Bruni: Il giorno sab 12 set 2020 alle 15:13, Jonas Hahnfeld ha scritto: I think right now it makes most sense to just release 2.21.6 as a "normal" unstable release, without any extra wording. The issue with the Documentation build should again be fixed,

Re: Lilypond build

2020-09-16 Thread Federico Bruni
Il giorno sab 12 set 2020 alle 15:13, Jonas Hahnfeld ha scritto: I think right now it makes most sense to just release 2.21.6 as a "normal" unstable release, without any extra wording. The issue with the Documentation build should again be fixed, so from my perspective you should be good to go

Re: Lilypond build

2020-09-12 Thread Jonas Hahnfeld
Am Freitag, den 11.09.2020, 13:29 +0200 schrieb Jonas Hahnfeld: > Am Freitag, den 11.09.2020, 12:20 +0100 schrieb Phil Holmes: > > I can't work out whether there was consensus on the next released build. > > With nobody else replying, I wouldn't call it consensus. > > > Are we going with 2.21.6

Re: Lilypond build

2020-09-11 Thread Jonas Hahnfeld
Am Freitag, den 11.09.2020, 12:20 +0100 schrieb Phil Holmes: > I can't work out whether there was consensus on the next released build. With nobody else replying, I wouldn't call it consensus. > Are we going with 2.21.6 and a release announcement that this is an initial > pre-release for a new

Lilypond build

2020-09-11 Thread Phil Holmes
I can't work out whether there was consensus on the next released build. Are we going with 2.21.6 and a release announcement that this is an initial pre-release for a new stable 2.22.0? Or perhaps go for 2.21.80 as a clearer sign that it's a pre-release? -- Phil Holmes

Re: LilyPond build for windows?

2020-06-21 Thread Jonas Hahnfeld via Discussions on LilyPond development
Am Sonntag, den 21.06.2020, 13:35 +0200 schrieb Han-Wen Nienhuys: > On Sun, Jun 21, 2020 at 12:07 PM Jonas Hahnfeld wrote: > > Am Samstag, den 20.06.2020, 20:25 +0200 schrieb Han-Wen Nienhuys: > > > What is the status of our lilypond binary on windows? > > > > > > The GUB based binary used to

Re: LilyPond build for windows?

2020-06-21 Thread Han-Wen Nienhuys
On Sun, Jun 21, 2020 at 12:07 PM Jonas Hahnfeld wrote: > > Am Samstag, den 20.06.2020, 20:25 +0200 schrieb Han-Wen Nienhuys: > > What is the status of our lilypond binary on windows? > > > > The GUB based binary used to include a hacked-together Python > > interpreter, which -due to being

Re: LilyPond build for windows?

2020-06-21 Thread Jonas Hahnfeld via Discussions on LilyPond development
Am Samstag, den 20.06.2020, 20:25 +0200 schrieb Han-Wen Nienhuys: > What is the status of our lilypond binary on windows? > > The GUB based binary used to include a hacked-together Python > interpreter, which -due to being cross-compiled- had some serious > limitations. Is this still the binary

LilyPond build for windows?

2020-06-20 Thread Han-Wen Nienhuys
What is the status of our lilypond binary on windows? The GUB based binary used to include a hacked-together Python interpreter, which -due to being cross-compiled- had some serious limitations. Is this still the binary we recommend to use ? -- Han-Wen Nienhuys - hanw...@gmail.com -

Re: GUB lilypond build fails

2019-01-01 Thread Werner LEMBERG
>> Please cherry-pick 8067320145662554d85e59e6b9e6df3770f9e4a3 also; >> I'm going to submit fontconfig changes to gub that rely on the >> availability of this feature. > > Well, I am not happy with such fresh changes in the stable-2.20 > branch but a 2.20 that we don't manage to get through GUB

Re: GUB lilypond build fails

2018-12-31 Thread David Kastrup
Werner LEMBERG writes: >>> cherry-picking 915799cad7118c39c89f564430093c0ad021dd9e from master >>> fixes that. >> >> Of course (change to Python 2.4 syntax). Done. > > Please cherry-pick 8067320145662554d85e59e6b9e6df3770f9e4a3 also; I'm > going to submit fontconfig changes to gub that rely on

Re: GUB lilypond build fails

2018-12-31 Thread Werner LEMBERG
>> cherry-picking 915799cad7118c39c89f564430093c0ad021dd9e from master >> fixes that. > > Of course (change to Python 2.4 syntax). Done. Please cherry-pick 8067320145662554d85e59e6b9e6df3770f9e4a3 also; I'm going to submit fontconfig changes to gub that rely on the availability of this

Re: GUB lilypond build fails

2018-12-30 Thread David Kastrup
Knut Petersen writes: > On 30.12.18 19:31, Phil Holmes wrote: >> >> >> Success building from master. Thanks Werner.  Will take me a time to >> sort out a build from the stable candidate, but it looks like we're >> on track. > > stable/2.20 currently will not build with gub. > > cherry-picking

Re: GUB lilypond build fails

2018-12-30 Thread Knut Petersen
On 30.12.18 19:31, Phil Holmes wrote: Success building from master. Thanks Werner.  Will take me a time to sort out a build from the stable candidate, but it looks like we're on track. stable/2.20 currently will not build with gub. cherry-picking 915799cad7118c39c89f564430093c0ad021dd9e

Re: GUB lilypond build fails

2018-12-30 Thread David Kastrup
"Phil Holmes" writes: > - Original Message - > From: "David Kastrup" > To: "Phil Holmes" > Cc: "Werner LEMBERG" ; > Sent: Sunday, December 30, 2018 6:46 PM > Subject: Re: GUB lilypond build fails > > >> "

Re: GUB lilypond build fails

2018-12-30 Thread Phil Holmes
- Original Message - From: "David Kastrup" To: "Phil Holmes" Cc: "Werner LEMBERG" ; Sent: Sunday, December 30, 2018 6:46 PM Subject: Re: GUB lilypond build fails "Phil Holmes" writes: - Original Message - From: "Phil Holmes

Re: GUB lilypond build fails

2018-12-30 Thread David Kastrup
David Kastrup writes: > "Phil Holmes" writes: > >> - Original Message - >> From: "Phil Holmes" >> To: "Werner LEMBERG" >> Cc: ; >> Sent: Sunday, December 30, 2018 12:29 PM >> Subject: Re: GUB lilypond build

Re: GUB lilypond build fails

2018-12-30 Thread David Kastrup
"Phil Holmes" writes: > - Original Message - > From: "Phil Holmes" > To: "Werner LEMBERG" > Cc: ; > Sent: Sunday, December 30, 2018 12:29 PM > Subject: Re: GUB lilypond build fails > > >> >> The problem with "N

Re: GUB lilypond build fails

2018-12-30 Thread Phil Holmes
- Original Message - From: "Phil Holmes" To: "Werner LEMBERG" Cc: ; Sent: Sunday, December 30, 2018 12:29 PM Subject: Re: GUB lilypond build fails The problem with "NewGub" would seem to be my issue. I've always made and uploaded GUB in a VM w

Re: GUB lilypond build fails

2018-12-30 Thread David Kastrup
"Phil Holmes" writes: > The problem with "NewGub" would seem to be my issue. I've always made > and uploaded GUB in a VM with a user gub and a directory called NewGub > under that user's home directory. I'm currently trying to build from > a user with a home directory called gubd and in a

Re: GUB lilypond build fails

2018-12-30 Thread Phil Holmes
- Original Message - From: "Werner LEMBERG" To: Cc: ; Sent: Saturday, December 29, 2018 8:42 PM Subject: Re: GUB lilypond build fails It now fails with a different file not found, but essentially still the same: [...] OK. If I try to locate the f

Re: GUB lilypond build fails

2018-12-29 Thread Werner LEMBERG
> It now fails with a different file not found, but essentially still > the same: [...] OK. > If I try to locate the file we get: [...] Are these files displayable? You could try gv -nosafedir -nosafer foo.eps > A curious other problem which I'd not remarked on before is that a > little

Re: GUB lilypond build fails

2018-12-29 Thread Phil Holmes
- Original Message - From: "Werner LEMBERG" To: Cc: ; Sent: Monday, December 24, 2018 9:39 PM Subject: Re: GUB lilypond build fails It may be of note that an earlier (i.e. 6 months' earlier) successful run doesn't have the "invoking GS" line in its output.

Re: GUB lilypond build fails

2018-12-24 Thread Werner LEMBERG
> It may be of note that an earlier (i.e. 6 months' earlier) > successful run doesn't have the "invoking GS" line in its output. What does locate merge-rests-engraver say? Are files containing this name actually present for the old version? And what about newer version? Maybe a log file

Re: GUB lilypond build fails

2018-12-24 Thread Werner LEMBERG
> Now done and I get this: > > Error: /undefinedfilename in (v2.19.64-1/merge-rests-engraver.eps) > > [...] > > Which is true. The file doesn't exist. It should have come from > the test-output-distance.py, I think, but have no clue as to why > it's not there. How many processes do run in

Re: GUB lilypond build fails

2018-12-24 Thread Phil Holmes
- Original Message - From: "Phil Holmes" To: "Werner LEMBERG" Cc: ; Sent: Monday, December 24, 2018 3:17 PM Subject: Re: GUB lilypond build fails - Original Message - From: "Werner LEMBERG" To: Cc: ; Sent: Monday, December 24, 2018 1:1

Re: GUB lilypond build fails

2018-12-24 Thread Phil Holmes
-- Phil Holmes - Original Message - From: "Werner LEMBERG" To: Cc: ; Sent: Monday, December 24, 2018 1:11 PM Subject: Re: GUB lilypond build fails This command seems to fail. Can you run it manually (with proper values for $PATH, $GS_FONTPATH, and $GS_LIB) so t

Re: GUB lilypond build fails

2018-12-24 Thread Phil Holmes
-- Phil Holmes - Original Message - From: "Werner LEMBERG" To: Cc: ; Sent: Monday, December 24, 2018 1:11 PM Subject: Re: GUB lilypond build fails This command seems to fail. Can you run it manually (with proper values for $PATH, $GS_FONTPATH, and $GS_LIB) so t

Re: GUB lilypond build fails

2018-12-24 Thread Werner LEMBERG
>> This command seems to fail. Can you run it manually (with proper >> values for $PATH, $GS_FONTPATH, and $GS_LIB) so that we can see its >> output? Information about the environment variables should be >> available in `lilypond-test.log'. > > Any idea of what would be the proper values for

Re: GUB lilypond build fails

2018-12-24 Thread Phil Holmes
- Original Message - From: "Werner LEMBERG" To: Cc: ; ; Sent: Sunday, December 23, 2018 11:19 PM Subject: Re: GUB lilypond build fails Almost completed a GUB build today, building against release/unstable. Unfortunately it eventually failed with the errors below.

Re: GUB lilypond build fails

2018-12-23 Thread Werner LEMBERG
> Almost completed a GUB build today, building against > release/unstable. Unfortunately it eventually failed with the errors > below. Can anyone suggest what ids going wrong? > > invoking gs -sDEVICE=png16m \ > -dGraphicsAlphaBits=4 \ > -dTextAlphaBits=4 \ >

Re: GUB lilypond build fails

2018-12-23 Thread Phil Holmes
Almost completed a GUB build today, building against release/unstable. Unfortunately it eventually failed with the errors below. Can anyone suggest what ids going wrong? mkdir /home/gubd/GubDir/gub/uploads/webtest/v2.21.0-1/compare-v2.19.64-1 mkdir

Re: GUB lilypond build fails

2018-12-17 Thread David Kastrup
Werner LEMBERG writes: >> So it would be really _urgent_ to get GUB advanced to a recent >> version of Python 2 in all supported platforms > > Yes. > >> (and I think we can delist the PPC platform support by now): > > What's exactly the reason for this? Considerable resources in compilation and

Re: GUB lilypond build fails

2018-12-17 Thread Werner LEMBERG
> So it would be really _urgent_ to get GUB advanced to a recent > version of Python 2 in all supported platforms Yes. > (and I think we can delist the PPC platform support by now): What's exactly the reason for this? > But at least PPC seems reasonably safe to retire, and possibly > FreeBSD

Re: GUB lilypond build fails

2018-12-17 Thread David Kastrup
Andrew Bernard writes: > Hi All, > > I am new to lilypond dev. work. My intention may be naive, but I am wanting > to do the work to uplift gub and lilypond to python 3. Am I premature, or > foolish, or misguided? I did have some encouraging email about this > previously, but I just wanted to

Re: GUB lilypond build fails

2018-12-16 Thread Andrew Bernard
Hi Carl, I'm on the case. This is the sort of work I can do. I have never been able to get into the groove of lilypond internals for some reason, but this type of system building tool is right up my alley. Andrew On Mon, 17 Dec 2018 at 14:53, Carl Sorensen wrote: > > GUB provides us a pretty

Re: GUB lilypond build fails

2018-12-16 Thread David Kastrup
Carl Sorensen writes: > On 12/16/18, 6:42 PM, "lilypond-devel on behalf of Andrew Bernard" > andrew.bern...@gmail.com> wrote: > > Hi All, > > I am new to lilypond dev. work. My intention may be naive, but I am > wanting > to do the work to uplift gub and lilypond to python 3.

Re: GUB lilypond build fails

2018-12-16 Thread Carl Sorensen
On 12/16/18, 6:42 PM, "lilypond-devel on behalf of Andrew Bernard" wrote: Hi All, I am new to lilypond dev. work. My intention may be naive, but I am wanting to do the work to uplift gub and lilypond to python 3. Am I premature, or foolish, or misguided? I did have some

Re: GUB lilypond build fails

2018-12-16 Thread Andrew Bernard
Hi All, I am new to lilypond dev. work. My intention may be naive, but I am wanting to do the work to uplift gub and lilypond to python 3. Am I premature, or foolish, or misguided? I did have some encouraging email about this previously, but I just wanted to check before I dive in and spend large

Re: GUB lilypond build fails

2018-12-16 Thread Carl Sorensen
On 12/16/18, 4:38 PM, "lilypond-devel on behalf of Werner LEMBERG" wrote: >I think you have the same issue me and others had. You don't see >it in the tail below, but if you open the lilypond.log file >you'll see a python command failing to generate a file

Re: GUB lilypond build fails

2018-12-16 Thread Werner LEMBERG
> lilypond should now build with gub as soon as this commit goes to > `master'. To be more precise: I can build lilypond with gub on my openSuSE Leap 42.3 GNU/Linux box.[*] I use the attached patches for gub (relative to HEAD), which are based on https://github.com/gperciva/gub/pull/7 plus

Re: GUB lilypond build fails

2018-12-16 Thread Werner LEMBERG
>I think you have the same issue me and others had. You don't see >it in the tail below, but if you open the lilypond.log file >you'll see a python command failing to generate a file because >GUB python is 2.4 while lilypond python code uses if statements. >It's discussed in

Re: GUB lilypond build fails

2018-12-16 Thread Federico Bruni
Hi Andrew I think you have the same issue me and others had. You don't see it in the tail below, but if you open the lilypond.log file you'll see a python command failing to generate a file because GUB python is 2.4 while lilypond python code uses if statements. It's discussed in

GUB lilypond build fails

2018-12-16 Thread Andrew Bernard
I am setup with lilydev 0.3, the latest release. I have installed gub from github, current master. Gub bootstrap runs to completion with no errors. Attempting to make lilypond, it fails as follows: $ bin/gub lilypond building package: linux-64::lilypond *** Stage: download (lilypond, linux-64)

Re: Lilypond build: version

2015-03-03 Thread Masamichi HOSODA
On Mar 2, 2015, at 09:03 , Masamichi HOSODA truer...@sea.plala.or.jp wrote: darwin-x86: Untested My Intel Mac environment was quite a temporary. Now, I don't have it. It runs without crashing on 10.10.2. Thank you for reporting. I'm happy to hear it.

Re: Lilypond build: version

2015-03-02 Thread Dan Eble
On Mar 2, 2015, at 09:03 , Masamichi HOSODA truer...@sea.plala.or.jp wrote: darwin-x86: Untested My Intel Mac environment was quite a temporary. Now, I don't have it. It runs without crashing on 10.10.2. — Dan ___ lilypond-devel mailing list

Re: Lilypond build: version

2015-03-02 Thread Masamichi HOSODA
Upload is now proceeding. Takes about 5 hours and slows internet access for the house to a crawl :-( Thank you for uploading official binaries. I've tested the binaries in my environments. The results are as follows. linux-x86: Ubuntu 14.04 LTS x86_64 (with 32bit libs) Fine linux-64:

Re: Lilypond build: version

2015-03-02 Thread David Kastrup
Keith OHara k-ohara5...@oco.net writes: Phil Holmes mail at philholmes.net writes: I completed a full GUB build of lilypond yesterday That's very good news. I was beginning to worry. Well, it's been 5 months. It's clear that our current maintainership of GUB is not working out.

Lilypond build: version

2015-03-01 Thread Phil Holmes
I completed a full GUB build of lilypond yesterday (it took 5 hours on my superfast machine). However, at present I can't upload it: I'm investigating but can't guarantee a solution quickly. I would like to be able to keep the package I've built available for upload as 2.19.16. I would

Re: Lilypond build: version

2015-03-01 Thread Phil Holmes
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Sunday, March 01, 2015 11:10 AM Subject: Re: Lilypond build: version Phil Holmes m...@philholmes.net writes: I completed a full GUB build of lilypond yesterday

Re: Lilypond build: version

2015-03-01 Thread Phil Holmes
- Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Sunday, March 01, 2015 11:40 AM Subject: Re: Lilypond build: version Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d

Re: Lilypond build: version

2015-03-01 Thread David Kastrup
Phil Holmes m...@philholmes.net writes: - Original Message - From: David Kastrup d...@gnu.org To: Phil Holmes m...@philholmes.net Cc: lilypond-devel@gnu.org Sent: Sunday, March 01, 2015 11:10 AM Subject: Re: Lilypond build: version Phil Holmes m...@philholmes.net writes: I

Re: Lilypond build: version

2015-03-01 Thread David Kastrup
Phil Holmes m...@philholmes.net writes: I completed a full GUB build of lilypond yesterday (it took 5 hours on my superfast machine). Sounds about par for the course. However, at present I can't upload it: I'm investigating but can't guarantee a solution quickly. I would like to be able

Re: Lilypond build: version

2015-03-01 Thread Keith OHara
Phil Holmes mail at philholmes.net writes: I completed a full GUB build of lilypond yesterday That's very good news. I was beginning to worry. Thanks for taking the time to work through the problems. ___ lilypond-devel mailing list

Lilypond build dependencies

2013-10-05 Thread Joseph Rushton Wakeling
Hello all, I'm trying to build Lilypond from git-HEAD source for the first time in a while and running into some curiosities from the ./configure script. This is on Ubuntu 13.10. First of all: ./configure requests a number of build dependencies that are not listed on the pages here:

Re: Lilypond build dependencies

2013-10-05 Thread David Kastrup
Joseph Rushton Wakeling joseph.wakel...@webdrake.net writes: What's the problem here, and is it possible to work around (i.e. tell ./configure I don't care, go ahead and accept working with 1.802) or is the bug sufficiently show-stopping that nothing can be done bar install the updated

Re: Lilypond build dependencies

2013-10-05 Thread Joseph Rushton Wakeling
On 05/10/13 19:01, David Kastrup wrote: Maybe you can use tlmgr for updating your Metapost. Well, you saw the error I encountered when trying to use tlmgr to do that. (Maybe I'm just misunderstanding how it works, I've never used it before.) No idea. Or complain to Ubuntu that they still

Re: Lilypond build dependencies

2013-10-05 Thread David Kastrup
Joseph Rushton Wakeling joseph.wakel...@webdrake.net writes: On 05/10/13 19:01, David Kastrup wrote: Maybe you can use tlmgr for updating your Metapost. Well, you saw the error I encountered when trying to use tlmgr to do that. (Maybe I'm just misunderstanding how it works, I've never used

Does the LilyPond build generate shared libraries you can use with Guile (load-extension) ?

2011-10-24 Thread Ian Hulin
Hi all, Is there am easy way of generating a shared library with all the scheme definitions generated in code by the C++ macro LY_DEFINE and friends? I would like have a way of testing scheme files from the Guile repl. It would take some of the grief out of hacking for the Guile V2 scheme port

Re: Generating compiled scm (.go) files as part of LilyPond build

2011-07-21 Thread Andy Wingo
Greets, On Tue 19 Jul 2011 15:28:41 BST, Andy Wingo wrote: On Tue 19 Jul 2011 15:18, Ian Hulin i...@hulin.org.uk writes: It may boil down to a matter of taste, but I find double and triple extensions on a filename intrinsically nasty. I've normally come across them before on Windows

Re: Generating compiled scm (.go) files as part of LilyPond build

2011-07-19 Thread Ian Hulin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 29/01/11 11:21, Andy Wingo wrote: Hi Ian, [re-adding the list; please keep the list CC'd on all guile-related topics] On Fri 28 Jan 2011 22:37, Ian Hulin i...@hulin.org.uk writes: Are you going to fix the double extension bug for

Re: Generating compiled scm (.go) files as part of LilyPond build

2011-07-19 Thread Andy Wingo
Hi Ian, On Tue 19 Jul 2011 15:18, Ian Hulin i...@hulin.org.uk writes: It may boil down to a matter of taste, but I find double and triple extensions on a filename intrinsically nasty. I've normally come across them before on Windows systems where a filename such as thing.htm.exe usually

Re: Generating compiled scm (.go) files as part of LilyPond build

2011-07-19 Thread Ian Hulin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue 19 Jul 2011 15:28:41 BST, Andy Wingo wrote: Hi Ian, On Tue 19 Jul 2011 15:18, Ian Hulin i...@hulin.org.uk writes: It may boil down to a matter of taste, but I find double and triple extensions on a filename intrinsically nasty. I've

Re: a new lilypond build failure

2005-10-24 Thread Han-Wen Nienhuys
Jan Nieuwenhuizen wrote: Well, it's a dangerous thing. Among other things, their version numbers might collide badly with the official Debian ones. Best it should have different package names to prevent this sort of thing from happening. Whe have this on our website, I think that Anthoy Fok

Re: a new lilypond build failure

2005-10-24 Thread Thomas Bushnell BSG
Jan Nieuwenhuizen [EMAIL PROTECTED] writes: Well, it's a dangerous thing. Among other things, their version numbers might collide badly with the official Debian ones. Best it should have different package names to prevent this sort of thing from happening. Whe have this on our website, I

Re: a new lilypond build failure

2005-10-24 Thread Thomas Bushnell BSG
Jan Nieuwenhuizen [EMAIL PROTECTED] writes: Ok; they were once used for processing the texinfo docs, right? They are still used for producing the PDF documentatation, so there is still a build dependency on tetex. Also, tetex is great for making documents with lilypond snippets, but this

Re: a new lilypond build failure

2005-10-24 Thread Jan Nieuwenhuizen
Han-Wen Nienhuys writes: Perhaps it's better to put them into a separate packaging CVS repo. Yes, let's just [re]move them all. The mingw/cygwin stuff is already in the installer repo. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter

Re: a new lilypond build failure

2005-10-24 Thread Jan Nieuwenhuizen
Han-Wen Nienhuys writes: then again, who actually uses these recipes? Now I remember, we used to have debian repackagers of development releases for debian stable and debian unstable. Anyway, what I'd really like to do is to build debs of any software that I need which is not in Debian (mostly

Re: a new lilypond build failure

2005-10-23 Thread Jan Nieuwenhuizen
Thomas Bushnell writes: But now there's a new, more subtle, one. Fixed in CVS, see patch below. Thanks for the report (and sorry that this kludge survived in the first place). Jan. Index: ChangeLog === RCS file:

Re: a new lilypond build failure

2005-10-23 Thread Jan Nieuwenhuizen
Thomas Bushnell writes: Anyway, with my patch (or equivalently with yours, I'm sure), lilypond 2.6.3 is now in Debian. (Whew!) That's great, thanks a lot for your efforts. I'm going to start going through the many Debian bug reports That's a good thing too. Btw, have you checked the

Re: a new lilypond build failure

2005-10-23 Thread Thomas Bushnell BSG
Han-Wen Nienhuys [EMAIL PROTECTED] writes: Thomas Bushnell BSG wrote: ec-fonts-mftraced Wait, you mean showed up and is now gone? What's it for anymore? Why did we ever have it? :) It was for Lily 2.4, which supported Latin1 encoding and fonts, but not unicode. I see, so now that

a new lilypond build failure

2005-10-21 Thread Thomas Bushnell BSG
So delightfully, mftrace version 1.1.17 does indeed fix the previous build problems. But now there's a new, more subtle, one. Normal Debian automatic build procedure is to build things with input redirected from /dev/null. This causes a failure in running lilypond for documentation generation.

lilypond build

2003-03-12 Thread raoul.megelas
Hello all, I have just cvs updated lily. since I upgraded my system (FreeBSD 5.0 lily don't build due to gcc (please see below). A patch or something like lexer-gcc-3.2.1.sh will be ineeded and appreciated? Many thanks. raoul [EMAIL PROTECTED]

Re: guile-1.4 shared patch (was: Re: lilypond build on cygwin stucks)

2001-09-20 Thread Gerrit P. Haase
Jan Nieuwenhuizen schrieb am 2001-09-20, 9:54: Gerrit P. Haase [EMAIL PROTECTED] writes: Jan Nieuwenhuizen schrieb am 2001-09-18, 22:04: Well now, after several attempts, I got it managed to build guile on Cygwin with shared libs (libguile.dll libguilereadline.dll). Now it is:

guile-1.4 shared patch (was: Re: lilypond build on cygwin stucks)

2001-09-19 Thread Gerrit P. Haase
Jan Nieuwenhuizen schrieb am 2001-09-18, 22:04: Well now, after several attempts, I got it managed to build guile on Cygwin with shared libs (libguile.dll libguilereadline.dll). Now it is: guile-1.4-2. The patch is up (because 30K), i hope it works for others, too.

Re: lilypond build on cygwin stucks

2001-09-18 Thread Jan Nieuwenhuizen
Gerrit P. Haase [EMAIL PROTECTED] writes: uh, kpathsea.h includes kpatsea/getopt.h and getopt.h, which doesn't work. Not on cygwin, only kpathsea/getopt.h is included: on cygwin, getopt.h is included through unistd.h. both are unneeded, that's why you cat use the -D__GETOPT_H__

Re: lilypond build on cygwin stucks

2001-09-18 Thread Gerrit P. Haase
Jan Nieuwenhuizen schrieb am 2001-09-18, 17:26: Gerrit P. Haase [EMAIL PROTECTED] writes: Jan Nieuwenhuizen schrieb am 2001-09-17, 11:53: Gerrit P. Haase [EMAIL PROTECTED] writes: [..] Ok, that's fine. See my edits to the wiki. ... it is not possible to post the GuilePatch here. (Try

Re: lilypond build on cygwin stucks

2001-09-17 Thread Gerrit P. Haase
Jan Nieuwenhuizen schrieb am 2001-09-17, 21:06: Gerrit P. Haase [EMAIL PROTECTED] writes: What kind of bug do you think of? uh, kpathsea.h includes kpatsea/getopt.h and getopt.h, which doesn't work. And I saw that unistd.h now includes getopt.h by default, too. That is too bad. I use an old

Re: lilypond build on cygwin stucks

2001-09-16 Thread Jan Nieuwenhuizen
Gerrit P. Haase [EMAIL PROTECTED] writes: I got compiletime errors: = rm -f ./out/kpath.dep; DEPENDENCIES_OUTPUT=./out/kpath.dep ./out/kpath.o g++ -c -DHAVE_ CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out -I.././lib/include -I../lib/./out -I../

Re: lilypond build on cygwin stucks

2001-09-16 Thread Gerrit P. Haase
Jan Nieuwenhuizen schrieb am 2001-09-16, 11:52: Gerrit P. Haase [EMAIL PROTECTED] writes: I got compiletime errors: = rm -f ./out/kpath.dep; DEPENDENCIES_OUTPUT=./out/kpath.dep ./out/kpath.o g++ -c -DHAVE_ CONFIG_H -DSTRING_UTILS_INLINED -Iinclude -I./out