On 18/07/2014 4:56 PM, Julien Rioux wrote:
On 18/07/2014 4:21 PM, Br. Samuel Springuel wrote:
I'm running LilyPond 2.18.2 on a Mac OS 10.8.5 and reported the same
error back in June:
http://lists.gnu.org/archive/html/lilypond-user/2014-06/msg00610.html
The problem (at least for me) see
On 18/07/2014 4:21 PM, Br. Samuel Springuel wrote:
I'm running LilyPond 2.18.2 on a Mac OS 10.8.5 and reported the same
error back in June:
http://lists.gnu.org/archive/html/lilypond-user/2014-06/msg00610.html
The problem (at least for me) seems to occur only when the --output or
--lily-output-
On 16/03/2014 5:08 PM, David Kastrup wrote:
Julien Rioux writes:
On 11/01/2014 6:31 AM, Matthias Steup wrote:
Matthias Steup arcor.de> writes:
David Kastrup gnu.org> writes:
Matthias Steup arcor.de> writes:
Lilypond-book seems to be broken in lilypond version 18.0. The s
On 11/01/2014 6:31 AM, Matthias Steup wrote:
Matthias Steup arcor.de> writes:
David Kastrup gnu.org> writes:
Matthias Steup arcor.de> writes:
Lilypond-book seems to be broken in lilypond version 18.0. The score runs
By the way, I cannot update to lilypond 18.0 because of liylpond-
On 08/03/2014 3:19 PM, Thomas Spuhler wrote:
Now that Mageia4 is out with Lilypond-2.18.0. We are working on the next
version to be release
around Christmas 2014.
Lilypond is now the only package (Gnucash has been ported to and Requires
Guile-2) that requires
Guile < 2.0. I have built Lilypond-
On 24/10/2013 3:10 PM, Thomas Klausner wrote:
GNU make 4.0 is out.
It stops, reporting an error, when trying to build lilypond-2.17.28:
"recipes commence before first target"
It looks to me like a misplaced endif. The attached patch fixes it.
Thanks, I've opened http://code.google.com/p/lil
On 02/09/2013 4:33 AM, David Kastrup wrote:
Thomas Klausner writes:
Can you also report which of the preexisting files in lily/out/ gets
overwritten by the problematic build, and which not?
The header file is not recreated, but the cc file is:
But actually, this should not overwrite parse
On 29/08/2013 12:35 PM, Werner LEMBERG wrote:
Here's my make.log:
http://www.markpolesky.com/norobots/make.log
Indeed: Instead of calling the script pfx2ttf.fontforge four times, I
just see
true
true
true
true
The rule covering this can be found in file `mf/GNUmakefile':
$(
On 26/07/2013 4:59 AM, bb wrote:
Obviously configure is not checking for texlive-metapost?
In my case (Linux) configure runs downright, but make reports the error
"
...
make[1]: Entering directory `/home/ich/lilypond-2.14.2/build/mf'
mkdir -p ./out
touch ./out/dummy.dep
On 14/07/2013 12:54 AM, Frédéric Bron wrote:
Fedora 19 comes with guile 2. However, it is possible to have both
guile 2 and guile 1.8.8 installed but the default is to point to guile
2.
configure does not complain when it finds guile 2 and the build
process can continue although the final lilypon
On 18/01/2013 4:56 PM, Stefan Thomas wrote:
Dear community,
when I compile the following file with latex and lilypondbook, it looks
quite strange.
There's is a break after every bar of the lilypond example.
I think it has to do with the input-command.
Here is the code of the latex-file:
\docume
On 25/10/2012 4:22 AM, Julien Rioux wrote:
This is ugly. We need to audit the fix for
http://code.google.com/p/lilypond/issues/detail?id=1455 more carefully.
It affects all python scripts on windows and since it's a GUB fix, all
versions built from latest GUB master.
A suggested fix
On 21/10/2012 9:30 AM, Eluze wrote:
bugs:
running without parameters produces 8 errors messages:
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error: : Unable to open file
convert-ly.py: error:
On 26/01/2012 6:14 PM, Graham Percival wrote:
On Thu, Jan 26, 2012 at 05:57:43PM -0500, Julien Rioux wrote:
On 22/01/2012 2:58 PM, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
input/regression/col
On 26/01/2012 11:13 AM, Reinhold Kainhofer wrote:
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
The pr
On 22/01/2012 2:58 PM, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
Could we redistribute the regression test input files
On 22/01/2012 2:38 PM, David Kastrup wrote:
Julien Rioux writes:
I can't run -j, I have a single core.
This is factually incorrect. You can run -j just fine, but you can't
expect much of a speedup. On a single-core machine,
make -j 2
typically gives you a speedup of maybe
On 22/01/2012 2:15 PM, Julien Rioux wrote:
On 22/01/2012 2:11 PM, Jean-Charles Malahieude wrote:
What I've done to check is:
open Documentation/fr/usage/running.itely
add the five X at the beginning of the first text line
XCe chapitre passe en revue ce qui se passe lorsque vous l
On 22/01/2012 2:11 PM, Jean-Charles Malahieude wrote:
What I've done to check is:
open Documentation/fr/usage/running.itely
add the five X at the beginning of the first text line
XCe chapitre passe en revue ce qui se passe lorsque vous lancez
LilyPond.
save it and "make -j3 doc LANGS='fr'"
On 22/01/2012 1:32 PM, Julien Rioux wrote:
The second issue I have not seen. If I correct a typo in a file in
Documentation then make doc will rebuild it. OK I should check
Documentation/fr right now...
When I edit Documentation/fr/essay/literature.itely and issue a make doc
from within
On 22/01/2012 1:30 PM, Phil Holmes wrote:
I've run a few with -j9 CPU_COUNT=9 this afternoon with no problems. The
only oddity I've noticed is that make doc make doc now seems to rebuild
a lot of files the second run.
--
Phil Holmes
I've hit a roadblock with issue 2125 which attempted to fix
On 22/01/2012 1:19 PM, Jean-Charles Malahieude wrote:
Hi all!
Not only that I can no longer use "-j" on a first build (it is OK
on the next builds), which means 40' for a "make doc LANGS='fr' and
about 2 hours for all languages, I now have to "make doc-clean" in
order to view a corrected typo. I
ly.progress (_ ("Applying conversion: "), newline = False)
TypeError: progress() got an unexpected keyword argument 'newline'
The line in question is following git-blame
86c0609e scripts/convert-ly.py (Julien Rioux 2011-12-14
08:40:02 -0500 184) ly.pr
On 11/01/2012 3:58 PM, Ian Hulin wrote:
Hi all I'm running make doc-stage-1 after
$ cd build
$ git checkout master
$ ../configure --disable-optimising
$ make
$ make test-baseline
$ git checkout T2026-1
$ make test-clean
$ make check
$ make doc-clean
Make doc-clean fails with:
.
.
.
/home/ian/src
On 02/11/2011 5:08 PM, David Kastrup wrote:
If you read all of the text I wrote above, you'll not find _any_
postulate. I am providing information and impressions from my own
experience and knowledge in order to help the original poster have a
better idea how to figure out what is wrong. I am n
On 02/11/2011 4:04 PM, David Kastrup wrote:
Julien Rioux writes:
On 27/10/2011 7:01 AM, Thomas Spuhler wrote:
LANG= makeinfo --enable-encoding -I
/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.15.15/Documentation -I.
-I./out --no-split --no-headers --output out/contributor.txt
out
On 27/10/2011 7:01 AM, Thomas Spuhler wrote:
LANG= makeinfo --enable-encoding -I
/home/spuhler/MageiaSVN/lilypond/BUILD/lilypond-2.15.15/Documentation -I.
-I./out --no-split --no-headers --output out/contributor.txt
out/contributor.texi
out/contributor.texi: No such file or directory
make[1]: **
On 12/10/2011 5:55 AM, Colin Campbell wrote:
On 11-10-11 04:49 PM, Julien Rioux wrote:
File "/home/jrioux/git/lilypond/scripts/out/musicxml2ly", line 220, in
extract_score_information
set_if_exists ('source', ids.get_source ())
AttributeError: Identification insta
File "/home/jrioux/git/lilypond/scripts/out/musicxml2ly", line 220, in
extract_score_information
set_if_exists ('source', ids.get_source ())
AttributeError: Identification instance has no attribute 'get_source'
Recipe to reproduce: just type make doc and CTRL-C fast enough when you
start to
On 18/09/2011 11:44 AM, Phil Holmes wrote:
"Julien Rioux" wrote in message
news:j52ida$6cf$1...@dough.gmane.org...
On 17/09/2011 6:10 PM, Reinhold Kainhofer wrote:
Am Saturday, 17. September 2011, 18:00:50 schrieb Julien Rioux:
On 17/09/2011 5:48 PM, Reinhold Kainhofer wrote:
S
On 17/09/2011 6:10 PM, Reinhold Kainhofer wrote:
Am Saturday, 17. September 2011, 18:00:50 schrieb Julien Rioux:
On 17/09/2011 5:48 PM, Reinhold Kainhofer wrote:
So, I think we can rule out any backend-cause.
I just checked all the banckends I got ('eps, 'null, 'ps, 'scm,
On 17/09/2011 5:48 PM, Reinhold Kainhofer wrote:
So, I think we can rule out any backend-cause.
I just checked all the banckends I got ('eps, 'null, 'ps, 'scm, 'socket,
'svg), and with guile 1.8.8 it only happens with the eps backend.
Finding any cause here is a real bugger.
--
Julien
___
On 17/09/2011 4:06 PM, Reinhold Kainhofer wrote:
Am Friday, 16. September 2011, 23:05:49 schrieb Julien Rioux:
After dumping guile 1.8.7 provided by the official ubuntu repository, I
downloaded, compiled and installed the latest stable guile 1.8.8 and
recompiled latest lilypond git. I still get
On 15/11/2010 10:54 PM, Patrick McCarty wrote:
Hi Julien,
On 2010-11-15, Julien Rioux wrote:
On 15/11/2010 2:59 PM, Patrick McCarty wrote:
Compiling with debug flags*might* help to narrow down the issue. The
easiest way to compile without optimization is by running autogen.sh
like so
On 15/11/2010 2:59 PM, Patrick McCarty wrote:
Compiling with debug flags*might* help to narrow down the issue. The
easiest way to compile without optimization is by running autogen.sh
like so
./autogen.sh --disable-optimising
I have done this now, and get the problem again, with little mo
Hi Patrick,
On 15/11/2010 2:59 PM, Patrick McCarty wrote:
That being said, this could be a problem with Guile on Ubuntu. As an
additional test, I would try compiling/installing Guile 1.8.7 from
scratch to see if this solves the problem.
I won't try this now, don't have much time.
Can you s
On 13/11/2010 4:51 PM, Patrick McCarty wrote:
If you want to start again with a pristine git checkout (I don't know
if this is in the Contributor's Guide yet), the following command
sequence usually works for me.
make doc-clean
make distclean
git clean -f -x
Then proceed with ./autogen
On 04/11/2010 7:34 PM, Patrick McCarty wrote:
Are you compiling LilyPond from scratch
by the way for my builds initially I did
git clone git://git.sv.gnu.org/lilypond.git lilypond
./autogen.sh
./configure.sh
make
sudo make install
Since then I have been doing
git pull
make
sudo make install
On 04/11/2010 7:34 PM, Patrick McCarty wrote:
Are you compiling LilyPond from scratch and using Guile 1.9, by chance?
Sorry that I didn't mention it originally.
I'm compiling the git master from
git://git.sv.gnu.org/lilypond.git
I am running ubuntu 10.10 and installed the dependencies with
a
Hi,
I've found a strange behaviour using lilypond-book --safe on a lytex
file: With multiple snippets each containing one \fret-diagram-x markup
command, compilation works for the first snippet but fails on the next
one. Then if you run lilypond-book --safe a second time, it will
successfully
Dear list,
This is a feature request for a safe mode for lilypond-book.
One can run lilypond with the -dsafe switch to avoid a security risk
when compiling .ly files including evil scheme code. There is no
equivalent switch for lilypond-book, and using --process leads to errors.
I'll post be
41 matches
Mail list logo
