subject:"build problem"

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-19 Thread Jacques Menu

Thanks a lot Werner, works like a charm!

JM

> Le 19 juil. 2020 à 09:11, Werner LEMBERG  a écrit :
> 
> 
> 
>> In fact I did the ‘git clone’ afresh, moving aside previous
>> attempts. Thus the contents of ‘build’ on both OSes is the result of
>> the commands I showed, up to '../configure'.
>> 
>> That’s why I don’t get what happens…
> 
> For me, using an up-to-date MacPorts system, compilation of LilyPond
> from the git works as follows.
> 
> (1) Clone `lilypond.git` or clean an existing repository with
> 
>  git clean -fdx 
> 
> (2) Configure LilyPond with
> 
>  ./autogen.sh --noconfigure
>  && ./configure \
> CC="ccache clang-mp-9.0" \
> CXX="ccache clang++-mp-9.0" \
> GUILE=/opt/local/bin/guile18 \
> GUILE_FLAVOR=guile-1.8 \
> --prefix="/foo/bar" \
> 
> --with-texgyre-dir="/usr/local/texlive/2020/texmf-dist/fonts/opentype/public/tex-gyre"
>  \
> --with-flexlexer-dir="/opt/local/include" \
> --disable-documentation
> 
>Remarks:
> 
>  . Adjust `--prefix` to whatever is suitable for you.
>  . Using `ccache` is optional.
>  . Slightly older clang versions should work, too.
>  . I use TeXLive directly, so please adapt the path to the
>TeX-Gyre fonts as necessary if you use the MacPorts packages
>of TeXLive.
> 
> (3) Build and install with
> 
>  make all && make install
> 
> (4) Run lilypond as
> 
>  LTDL_LIBRARY_PATH=/opt/local/lib \
>  PATH=/foo/bar/bin:$PATH \
>  lilypond 
> 
> 
>Werner

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-19 Thread Werner LEMBERG



> In fact I did the ‘git clone’ afresh, moving aside previous
> attempts. Thus the contents of ‘build’ on both OSes is the result of
> the commands I showed, up to '../configure'.
> 
> That’s why I don’t get what happens…

For me, using an up-to-date MacPorts system, compilation of LilyPond
from the git works as follows.

(1) Clone `lilypond.git` or clean an existing repository with

  git clean -fdx 

(2) Configure LilyPond with

  ./autogen.sh --noconfigure
  && ./configure \
 CC="ccache clang-mp-9.0" \
 CXX="ccache clang++-mp-9.0" \
 GUILE=/opt/local/bin/guile18 \
 GUILE_FLAVOR=guile-1.8 \
 --prefix="/foo/bar" \
 
--with-texgyre-dir="/usr/local/texlive/2020/texmf-dist/fonts/opentype/public/tex-gyre"
 \
 --with-flexlexer-dir="/opt/local/include" \
 --disable-documentation

Remarks:

  . Adjust `--prefix` to whatever is suitable for you.
  . Using `ccache` is optional.
  . Slightly older clang versions should work, too.
  . I use TeXLive directly, so please adapt the path to the
TeX-Gyre fonts as necessary if you use the MacPorts packages
of TeXLive.

(3) Build and install with

  make all && make install

(4) Run lilypond as

  LTDL_LIBRARY_PATH=/opt/local/lib \
  PATH=/foo/bar/bin:$PATH \
  lilypond 


Werner

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Jacques Menu

PS> My goal is to build Lily to do experiments on the Mac, which is much faster 
and confortable for me to work with, rather that on my Debian virtual machine.

> Le 18 juil. 2020 à 17:23, Jacques Menu  a écrit :
> 
> Hello Jonas and Werner,
> 
> In fact I did the ‘git clone’ afresh, moving aside previous attempts. Thus 
> the contents of ‘build’ on both OSes is the result of the commands I showed, 
> up to '../configure'.
> 
> That’s why I don’t get what happens…
> 
> JM
> 
> 
>> Le 18 juil. 2020 à 16:46, Werner LEMBERG  a écrit :
>> 
>> 
>>> I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and
>>> Mac OS X 10.14.6 (Mojave).  On the latter, I installed Apple’s
>>> XCode, the needed tools in /opt with MacPorts, and the needed fonts
>>> in /opt/local/share/fonts/urw-core35-fonts.
>> 
>> You might apply
>> 
>> https://github.com/macports/macports-ports/pull/7732
>> 
>> to build 2.21.3 with MacPorts.  It's a bit unfortunate that the
>> MacPorts people are slow with pull requests – 2.21.4 is coming soon...
>> 
>> 
>>   Werner
>

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Jacques Menu

Hello Jonas and Werner,

In fact I did the ‘git clone’ afresh, moving aside previous attempts. Thus the 
contents of ‘build’ on both OSes is the result of the commands I showed, up to 
'../configure'.

That’s why I don’t get what happens…

JM


> Le 18 juil. 2020 à 16:46, Werner LEMBERG  a écrit :
> 
> 
>> I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and
>> Mac OS X 10.14.6 (Mojave).  On the latter, I installed Apple’s
>> XCode, the needed tools in /opt with MacPorts, and the needed fonts
>> in /opt/local/share/fonts/urw-core35-fonts.
> 
> You might apply
> 
>  https://github.com/macports/macports-ports/pull/7732
> 
> to build 2.21.3 with MacPorts.  It's a bit unfortunate that the
> MacPorts people are slow with pull requests – 2.21.4 is coming soon...
> 
> 
>Werner

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Werner LEMBERG


> I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and
> Mac OS X 10.14.6 (Mojave).  On the latter, I installed Apple’s
> XCode, the needed tools in /opt with MacPorts, and the needed fonts
> in /opt/local/share/fonts/urw-core35-fonts.

You might apply

  https://github.com/macports/macports-ports/pull/7732

to build 2.21.3 with MacPorts.  It's a bit unfortunate that the
MacPorts people are slow with pull requests – 2.21.4 is coming soon...


Werner

Re: 2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Jonas Hahnfeld

Hi,

Am Samstag, den 18.07.2020, 15:14 +0200 schrieb Jacques Menu:
> Hello folks,
> 
> I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and Mac OS X 
> 10.14.6 (Mojave). 
> On the latter, I installed Apple’s XCode, the needed tools in /opt with 
> MacPorts, and the needed fonts in /opt/local/share/fonts/urw-core35-fonts. 
> 
> Performing the same ‘git clone’ and the same steps alongside, I run into a 
> situation in which the contents of the build directory is by far different on 
> both OSes, see below.
> 
> Then ‘make' runs fine on Debian, but fails on Mojave due to a missing 
> build/make directory.
> 
> That beats me. Can someone explain why ‘../configure’ creates fewer files on 
> the Mac OS X side? The trace it produces is at the end of this message.
> 
> [...]
> 
> menu@macbookprojm: ~/lilypond-git/build > ../configure 
> --with-urwotf-dir=/opt/local/share/fonts/urw-core35-fonts
> [...]
> configure: creating ./config.status
> config.status: creating config.make
> config.status: creating config.hh
> config.status: config.hh is unchanged

This looks as if the build directory was not empty. Could it be that
the directory still contained stale results from a previous invocation
of configure? If that failed, I'm not sure if configure correctly
recovers in all cases...
It's of course possible that this is the result of executing configure
again to obtain a log after the failures described before. In that
case, creating a new build directory won't help much and maybe you
already tried...

Jonas


signature.asc
Description: This is a digitally signed message part

2.21.3 build problem on Mac OS X Mojave

2020-07-18 Thread Jacques Menu

Hello folks,

I’m trying to build LilyPond 2.21.3 locally, both on Debian 9 and Mac OS X 
10.14.6 (Mojave). 
On the latter, I installed Apple’s XCode, the needed tools in /opt with 
MacPorts, and the needed fonts in /opt/local/share/fonts/urw-core35-fonts. 

Performing the same ‘git clone’ and the same steps alongside, I run into a 
situation in which the contents of the build directory is by far different on 
both OSes, see below.

Then ‘make' runs fine on Debian, but fails on Mojave due to a missing 
build/make directory.

That beats me. Can someone explain why ‘../configure’ creates fewer files on 
the Mac OS X side? The trace it produces is at the end of this message.

Thanks for your help!

JM

—

Linux side:

  574  git clone https://git.savannah.gnu.org/git/lilypond.git lilypond-git ; 
cd lilypond-git
  575  ll
  576  ./autogen.sh --noconfigure
  577  ll
  578  mkdir build/ ; cd build/
  579  ../configure


user@debian: ~/lilypond-git/build > ls -sal
total 228
 4 drwxr-xr-x 19 user user  4096 Jul 18 14:51 .
 4 drwxr-xr-x 23 user user  4096 Jul 18 14:51 ..
 4 drwxr-xr-x 20 user user  4096 Jul 18 14:51 Documentation
 4 -r--r--r--  1 user user73 Jul 18 14:51 GNUmakefile
40 -rw-r--r--  2 user user 38783 Jul 18 14:51 INSTALL.txt
 4 -rw-r--r--  2 user user  2390 Jul 18 14:51 README.txt
 4 -rw-r--r--  1 user user  2022 Jul 18 14:51 config.hh
60 -rw-r--r--  1 user user 57730 Jul 18 14:51 config.log
 8 -rw-r--r--  1 user user  4281 Jul 18 14:51 config.make
32 -rwxr-xr-x  1 user user 31770 Jul 18 14:51 config.status
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 elisp
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 flower
 4 drwxr-xr-x  3 user user  4096 Jul 18 14:51 input
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 lily
 0 -rw-r--r--  1 user user 0 Jul 18 14:51 local.make
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 ly
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 make
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 mf
 4 drwxr-xr-x  3 user user  4096 Jul 18 14:51 out
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 po
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 ps
 4 drwxr-xr-x  3 user user  4096 Jul 18 14:51 python
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 scm
 4 drwxr-xr-x  3 user user  4096 Jul 18 14:51 scripts
 4 drwxr-xr-x  3 user user  4096 Jul 18 14:51 stepmake
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 tex
 4 drwxr-xr-x  2 user user  4096 Jul 18 14:51 vim
user@debian: ~/lilypond-git/build >


Then ‘make' succeeds, with the make subdirectory containing:

user@debian: ~/lilypond-git/build > ls -sal make
total 108
4 drwxr-xr-x  2 user user 4096 Jul 18 14:51 .
4 drwxr-xr-x 19 user user 4096 Jul 18 14:51 ..
4 -rw-r--r--  1 user user   79 Jul 18 14:51 abc-rules.make
4 -rw-r--r--  1 user user   81 Jul 18 14:51 abc-targets.make
4 -rw-r--r--  1 user user   78 Jul 18 14:51 abc-vars.make
4 -rw-r--r--  1 user user   89 Jul 18 14:51 doc-i18n-root-rules.make
4 -rw-r--r--  1 user user   91 Jul 18 14:51 doc-i18n-root-targets.make
4 -rw-r--r--  1 user user   88 Jul 18 14:51 doc-i18n-root-vars.make
4 -rw-r--r--  1 user user   83 Jul 18 14:51 generic-rules.make
4 -rw-r--r--  1 user user   85 Jul 18 14:51 generic-targets.make
4 -rw-r--r--  1 user user   82 Jul 18 14:51 generic-vars.make
4 -rw-r--r--  1 user user   89 Jul 18 14:51 lilypond-book-rules.make
4 -rw-r--r--  1 user user   91 Jul 18 14:51 lilypond-book-targets.make
4 -rw-r--r--  1 user user   88 Jul 18 14:51 lilypond-book-vars.make
4 -rw-r--r--  1 user user   84 Jul 18 14:51 lilypond-rules.make
4 -rw-r--r--  1 user user   86 Jul 18 14:51 lilypond-targets.make
4 -rw-r--r--  1 user user   83 Jul 18 14:51 lilypond-vars.make
4 -rw-r--r--  1 user user   78 Jul 18 14:51 ly-rules.make
4 -rw-r--r--  1 user user   80 Jul 18 14:51 ly-targets.make


—

Mac OS X side:

  657  git clone https://git.savannah.gnu.org/git/lilypond.git lilypond-git ; 
cd lilypond-git
  658  ll
  659  ./autogen.sh --noconfigure
  660  ll
  661  mkdir build/ ; cd build/
  662  ../configure --with-urwotf-dir=/opt/local/share/fonts/urw-core35-fonts


menu@macbookprojm: ~/lilypond-git/build > ls -sal
total 232
  0 drwxr-xr-x   8 menu  staff256 Jul 18 14:51 .
  0 drwxr-xr-x  46 menu  staff   1472 Jul 18 14:51 ..
  8 -r--r--r--   1 menu  staff 73 Jul 18 14:51 GNUmakefile
  8 -rw-r--r--   1 menu  staff   2022 Jul 18 14:51 config.hh
128 -rw-r--r--   1 menu  staff  62212 Jul 18 14:51 config.log
 16 -rw-r--r--   1 menu  staff   5353 Jul 18 14:51 config.make
 72 -rwxr-xr-x   1 menu  staff  32811 Jul 18 14:51 config.status
  0 -rw-r--r--   1 menu  staff  0 Jul 18 14:51 local.make
menu@macbookprojm: ~/lilypond-git/build > 


Then ‘make' fails because there’s no ‘make' subdirectory:

menu@macbookprojm: ~/lilypond-git/build > make 
/Users/menu/lilypond-git/build/../GNUmakefile.in:36: make/stepmake.make: No 
such file or directory


—

menu@macbookprojm: ~/lilypond-git/build > ../configure 
--with-urwotf-dir=/opt/local/share/fonts/urw-core35-fonts
checking build system type... x86_64-ap

Re: Build problem with fonts

2019-12-09 Thread Federico Bruni




Il giorno lun 9 dic 2019 alle 11:18, Federico Bruni 
 ha scritto:
Il giorno lun 9 dic 2019 alle 08:38, Werner LEMBERG  ha 
scritto:

Your `t1asm` binary crashes with a segmentation fault, as can be seen
in last two lines of `mf2pt1.strace.657213`:

  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, 
si_addr=0x3055683} ---

  +++ killed by SIGSEGV (core dumped) +++

You should also see an error message if you manually do

  t1asm feta11.pt1 feta11.pfb

Please try to either re-install `t1asm`, get a newer version, or
compile and install it by yourself.


Same here, I've reported the bug ten days ago:
https://bugzilla.redhat.com/show_bug.cgi?id=1777987

Maintainer did not reply yet.
I'll see if I can send a patch when I have some time.





Jean-Charles, I sent a PR here:
https://src.fedoraproject.org/rpms/t1utils/pull-request/1


I've built a new RPM from that spec file and I can build lilypond again.
Find it attached (x86_64).




t1utils-1.41-2.fc31.x86_64.rpm
Description: application/rpm

Re: Build problem with fonts

2019-12-09 Thread Federico Bruni

Il giorno lun 9 dic 2019 alle 08:38, Werner LEMBERG  ha 
scritto:

Your `t1asm` binary crashes with a segmentation fault, as can be seen
in last two lines of `mf2pt1.strace.657213`:

  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, 
si_addr=0x3055683} ---

  +++ killed by SIGSEGV (core dumped) +++

You should also see an error message if you manually do

  t1asm feta11.pt1 feta11.pfb

Please try to either re-install `t1asm`, get a newer version, or
compile and install it by yourself.


Same here, I've reported the bug ten days ago:
https://bugzilla.redhat.com/show_bug.cgi?id=1777987

Maintainer did not reply yet.
I'll see if I can send a patch when I have some time.

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG



>> Please try again with
>>strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf
>> so that we can see the strace messages from `t1asm` also.  Note that
>> you will get at least two files called `mf2pt1.strace.X`, where
>> `X` is a process ID.
>> 
> 
> Four log-files were created, and the 3 resulting font-files as well.

Thanks.

Your `t1asm` binary crashes with a segmentation fault, as can be seen
in last two lines of `mf2pt1.strace.657213`:

  --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x3055683} ---
  +++ killed by SIGSEGV (core dumped) +++

You should also see an error message if you manually do

  t1asm feta11.pt1 feta11.pfb

Please try to either re-install `t1asm`, get a newer version, or
compile and install it by yourself.

I use the `t1asm` binary from TeXLive 2019; it is works without
problems.


Werner

Re: Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude


Le 08/12/2019 à 18:12, Werner LEMBERG a écrit :


Please try again with

   strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf

so that we can see the strace messages from `t1asm` also.  Note that
you will get at least two files called `mf2pt1.strace.X`, where
`X` is a process ID.



Four log-files were created, and the 3 resulting font-files as well.

feta11.pfb seems to be truncated, last lines being just

"
dup 142 /scripts.caesura.straight put
dup 1
"

And the console, as usual, finally spits

"Invoking "t1asm feta11.pt1 feta11.pfb"...
mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find 
another way to convert feta11.pt1 to feta11.pfb"


I enclose the generated files in mf/ if it helps.

Thanks,

ps. The dinner is smoothly cooking, just waiting for Madame to come home 
after concert.

--
Jean-Charles


mf2pt1.strace-ff.tar.xz
Description: application/xz


feta11.tar.xz
Description: application/xz

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG



>> Strange indeed.  Can you temporarily replace `mf2pt1` with a script
>> that calls `strace`?  Something like
>>strace mf2pt1 ... &> ~/mf2pt1.strace.log
>> You could then investigate in more detail which files `mf2pt1` tries
>> to open and/or execute.
>> 
> 
> [jcharles@pc1 mf]$ strace mf2pt1 feta11.mf &> ~/mf2pt1.strace
> 
> generates the .pfb .pt1 and .tfm

Please try again with

  strace -ff -o ~/mf2pt1.strace mf2pt1 feta11.mf

so that we can see the strace messages from `t1asm` also.  Note that
you will get at least two files called `mf2pt1.strace.X`, where
`X` is a process ID.


   Werner

Re: Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude


Le 08/12/2019 à 17:10, Werner LEMBERG a écrit :


Strange indeed.  Can you temporarily replace `mf2pt1` with a script
that calls `strace`?  Something like

   strace mf2pt1 ... &> ~/mf2pt1.strace.log

You could then investigate in more detail which files `mf2pt1` tries
to open and/or execute.



[jcharles@pc1 mf]$ strace mf2pt1 feta11.mf &> ~/mf2pt1.strace

generates the .pfb .pt1 and .tfm

And I don't see anything special in the log (enclosed), at first glance 
since I'm not really able to interpret it.


Have to leave for now, and come back tomorrow.

TIA,
--
Jean-Charles


mf2pt1.strace.tar.xz
Description: application/xz

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG


> which t1asm
> /usr/bin/t1asm
> 
> so I don't see any reason why, just at once, it failed at running…
> after a good sleeping night!

Strange indeed.  Can you temporarily replace `mf2pt1` with a script
that calls `strace`?  Something like

  strace mf2pt1 ... &> ~/mf2pt1.strace.log

You could then investigate in more detail which files `mf2pt1` tries
to open and/or execute.


Werner

Re: Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude


Le 08/12/2019 à 16:51, Werner LEMBERG a écrit :


Can you execute t1asm?

   t1asm --help



It works either in $HOME or in my compiling folders.


Is it in your path that you use for compiling lilypond?



which t1asm
/usr/bin/t1asm

so I don't see any reason why, just at once, it failed at running… after 
a good sleeping night!


--
Jean-Charles

Re: Build problem with fonts

2019-12-08 Thread Werner LEMBERG



> I notice, upwards in the log, that
> 
> Invoking "t1asm feta11.pt1 feta11.pfb"...
> mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find
> another way to convert feta11.pt1 to feta11.pfb
> 
> 
> despite I've t1utils-1.41-1.fc31.x86_64 installed.

Can you execute t1asm?

  t1asm --help

Is it in your path that you use for compiling lilypond?


Werner

Build problem with fonts

2019-12-08 Thread Jean-Charles Malahieude


Hi all,

For about two weeks now, I'm unable to build and then merge translation 
with stable, even after a fresh clone. I cannot believe it has something 
to do with an upgrade from Fedora 30 to 31.


Tail of the log :
--8<--
cd ./out && /usr/bin/fontforge -script emmentaler-11.genpe
Copyright (c) 2000-2019. See AUTHORS for Contributors.
 License GPLv3+: GNU GPL version 3 or later 

 with many parts BSD . Please read 
LICENSE.

 Version: 20190801
 Based on sources from 00:00 UTC 15-Aug-2019-ML-D.
Cannot open /home/jcharles/GIT/Stable/mf/out/feta11.pfb
The requested file, feta11.pfb, does not exist
MergeFonts: Can't find font: feta11.pfb
Called from...
 emmentaler-11.genpe: line 17
make[1]: *** [GNUmakefile:138: out/emmentaler-11.otf] Error 1
make[1]: Leaving directory '/home/jcharles/GIT/Stable/mf'
make: *** 
[/home/jcharles/GIT/Stable/stepmake/stepmake/generic-targets.make:6: 
all] Error 2


Compilation exited abnormally with code 2 at Sun Dec  8 15:46:09
-->8--

I notice, upwards in the log, that

Invoking "t1asm feta11.pt1 feta11.pfb"...
mf2pt1: You'll need either to install t1utils and rerun mf2pt1 or find 
another way to convert feta11.pt1 to feta11.pfb



despite I've t1utils-1.41-1.fc31.x86_64 installed.

Some hints?

Cheers,
--
Jean-Charles

Re: build problem

2019-07-26 Thread Jean-Charles Malahieude


Le 26/07/2019 à 09:44, Federico Bruni a écrit :
Jean-Charles, version 1.0.3 is now available in Fedora 30 repositories. 
And version 1.1.0 is in rawhide.




As I've cloned the repository and built it without any problem, 
everything is fine.


Cheers,
Jean-Charles

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

Re: build problem

2019-07-26 Thread Federico Bruni

Il giorno lun 1 lug 2019 alle 8:03, Federico Bruni  
ha scritto:
Yes, I run Fedora 30 since it was released and I can compile lilypond 
without any problem  using the package available in Fedora.
I've now built the rpm for version 1.0.3 and it works as well. I'll 
submit the new version to the Fedora repository soon. (I think 1.1.0 
requires poppler>=0.74, which is not available in Fedora yet)


Jean-Charles, version 1.0.3 is now available in Fedora 30 repositories. 
And version 1.1.0 is in rawhide.




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

Re: build problem

2019-06-30 Thread Federico Bruni

Il giorno dom 30 giu 2019 alle 10:45, Jean-Charles Malahieude 
 ha scritto:
My first attempts were using the official Fedora package (as I do 
since one is available), version 1.0.2. Facing this library problem, 
I've built a package for 1.0.3 and then 1.1.0 which both bump the 
wall.


Unfortunately, I don't remember if my last merge was just before 
upgrading to Fedora 30 or not. And Federico, who runs a Fedora 30 as 
well if I'm not mistaken, pushed on Translation mid-June…


Yes, I run Fedora 30 since it was released and I can compile lilypond 
without any problem  using the package available in Fedora.
I've now built the rpm for version 1.0.3 and it works as well. I'll 
submit the new version to the Fedora repository soon. (I think 1.1.0 
requires poppler>=0.74, which is not available in Fedora yet)


I think Masamichi analysis is correct.
You probably built the rpm when you had Fedora 29 and a different 
version of poppler from what you currently have.
You could have checked it this way (after a new build from source you 
already fixed it):


$ ldd /usr/bin/extractpdfmark | grep poppler
libpoppler.so.84 => /lib64/libpoppler.so.84 (0x7f9a1930f000)

$ ls -l /lib64/libpoppler.so*
lrwxrwxrwx. 1 root root 16 30 mag 17.46 /lib64/libpoppler.so -> 
libpoppler.so.84
lrwxrwxrwx. 1 root root 20 30 mag 17.46 /lib64/libpoppler.so.84 -> 
libpoppler.so.84.0.0

-rwxr-xr-x. 1 root root 4831336 30 mag 17.46 /lib64/libpoppler.so.84.0.0




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

Re: build problem

2019-06-30 Thread Jean-Charles Malahieude


Le 30/06/2019 à 11:10, Knut Petersen a écrit :

Build it yourself. Building and installing extractpdfmark is  an easy
an fast task.
Cloning the repository, building, testing and installing of 
extractpdfmark takes less than 20 seconds here:




This, as intended, works like a charm, but I was expecting an rpm to do 
its job (and notice nothing wrong when creating them).


Cheers,
--
Jean-Charles

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

Re: build problem

2019-06-30 Thread Knut Petersen


On 30.06.19 10:45, Jean-Charles Malahieude wrote:


Unfortunately, I don't remember if my last merge was just before upgrading to 
Fedora 30 or not. And Federico, who runs a Fedora 30 as well if I'm not 
mistaken, pushed on Translation mid-June…


Build it yourself. Building and installing extractpdfmark is  an easy an fast 
task.
Cloning the repository, building, testing and installing of extractpdfmark takes
less than 20 seconds here:

   git clone https://github.com/trueroad/extractpdfmark.git && \
   cd extractpdfmark && \
   ./autogen.sh && \
   mkdir build && \
   cd build && \
   ../configure && \
   make && \
   make check && \
   sudo make install


If building fails: Have a look at extractpdfmark/README.md - there you find a 
list of required packages.

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

Re: build problem

2019-06-30 Thread Jean-Charles Malahieude


Le 30/06/2019 à 02:51, Masamichi Hosoda a écrit :

In Fedora 30, I suggest to use extractpdfmark from package,
rather than self-built extractpdfmark.
https://apps.fedoraproject.org/packages/extractpdfmark

If I understand correctly,
Fedora 30 has popler-0.73.0 package that has libpoppler.so.84.
https://koji.fedoraproject.org/koji/rpminfo?rpmID=17656985
Fedora 29 has popler-0.67.0 package that has libpoppler.so.78.
https://koji.fedoraproject.org/koji/rpminfo?rpmID=17657086

Did you build extractpdfmark on Fedora 29?
If so, it depends on libpoppler.so.78.
However, Fedora 30 does not have libpoppler.so.78.



My first attempts were using the official Fedora package (as I do since 
one is available), version 1.0.2. Facing this library problem, I've 
built a package for 1.0.3 and then 1.1.0 which both bump the wall.


Unfortunately, I don't remember if my last merge was just before 
upgrading to Fedora 30 or not. And Federico, who runs a Fedora 30 as 
well if I'm not mistaken, pushed on Translation mid-June…



Cheers,
--
Jean-Charles

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

Re: build problem

2019-06-29 Thread Masamichi Hosoda

> Hello,
> 
> Since I can't get a successful doc-build on my Fedora 30 box, I'm
> unable to check doc-changes and merge translation into stable.
> 
> It's the same with extractpdfmark 1.0.2 1.0.3 and 1.1.0
> 
> log spits:
> 
> extractpdfmark -o ./out-www/collated-files.pdfmark
> ./out-www/collated-files.tmp.pdf
> extractpdfmark: error while loading shared libraries:
> libpoppler.so.78: cannot open shared object file: No such file or
> directory
> 
> And I won't try to package poppler-0.78. There are too many
> dependencies for me (Fedora is stuck to 0.73).

In Fedora 30, I suggest to use extractpdfmark from package,
rather than self-built extractpdfmark.
https://apps.fedoraproject.org/packages/extractpdfmark

If I understand correctly,
Fedora 30 has popler-0.73.0 package that has libpoppler.so.84.
https://koji.fedoraproject.org/koji/rpminfo?rpmID=17656985
Fedora 29 has popler-0.67.0 package that has libpoppler.so.78.
https://koji.fedoraproject.org/koji/rpminfo?rpmID=17657086

Did you build extractpdfmark on Fedora 29?
If so, it depends on libpoppler.so.78.
However, Fedora 30 does not have libpoppler.so.78.

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

build problem

2019-06-29 Thread Jean-Charles Malahieude


Hello,

Since I can't get a successful doc-build on my Fedora 30 box, I'm unable 
to check doc-changes and merge translation into stable.


It's the same with extractpdfmark 1.0.2 1.0.3 and 1.1.0

log spits:

extractpdfmark -o ./out-www/collated-files.pdfmark 
./out-www/collated-files.tmp.pdf
extractpdfmark: error while loading shared libraries: libpoppler.so.78: 
cannot open shared object file: No such file or directory


And I won't try to package poppler-0.78. There are too many dependencies 
for me (Fedora is stuck to 0.73).


Cheers,
--
Jean-Charles

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

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-03 Thread James


Hello

On 03/06/2019 12:29, Knut Petersen wrote:

Hi Werner!

OK.  Do you have time to prepare a patch?


No time ... but attached is quick shot.

Min version 2.44 seems reasonable as we use it in gub.

Knut


Thanks

https://sourceforge.net/p/testlilyissues/issues/5525/


James



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

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-03 Thread Knut Petersen


Hi Werner!

OK.  Do you have time to prepare a patch?


No time ... but attached is quick shot.

Min version 2.44 seems reasonable as we use it in gub.

Knut


>From 619de1764cd472ec7587f98c34ba7b7e613be93c Mon Sep 17 00:00:00 2001
From: Knut Petersen 
Date: Mon, 3 Jun 2019 12:30:08 +0200
Subject: [PATCH] Add glib-2.0 and gobject-2.0 library dependency

For a long time we relied on pango/pangoft2 to pull in
the glib and gobject libraries. That worked as long as
every distribution used a pangoft2.pc file that included
both libs in the 'Required:' line.

According to the pkg-config documentation that was
definitely wrong, and the problem was corrected  on
opensuse tumbleweed recently. As a consequence building
lilypond failed with a linker error as we use symbols
from both libs directly in our c++ source code.

Signed-off-by: Knut Petersen 
---
 aclocal.m4 | 38 ++
 config.make.in |  6 --
 configure.ac   |  2 ++
 3 files changed, 44 insertions(+), 2 deletions(-)

diff --git a/aclocal.m4 b/aclocal.m4
index cf558c81e9..cb4fa83414 100644
--- a/aclocal.m4
+++ b/aclocal.m4
@@ -1284,6 +1284,44 @@ AC_DEFUN(PKG_CHECK_MODULES, [
   fi
 ])
 
+AC_DEFUN(STEPMAKE_GLIB, [
+PKG_CHECK_MODULES(GLIB, $1 >= $3, have_glib=yes, true)
+if test "$have_glib" = yes; then
+	AC_DEFINE(HAVE_GLIB)
+save_CPPFLAGS="$CPPFLAGS"
+save_LIBS="$LIBS"
+	CPPFLAGS="$GLIB_CFLAGS $CPPFLAGS"
+	LIBS="$GLIB_LIBS $LIBS"
+	AC_SUBST(GLIB_CFLAGS)
+	AC_SUBST(GLIB_LIBS)
+	CPPFLAGS="$save_CPPFLAGS"
+	LIBS="$save_LIBS"
+else
+  r="libglib-dev or glib?-devel"
+  ver="`pkg-config --modversion $1`"
+  STEPMAKE_ADD_ENTRY($2, ["$r >= $3 (installed: $ver)"])
+fi
+])
+
+AC_DEFUN(STEPMAKE_GOBJECT, [
+PKG_CHECK_MODULES(GOBJECT, $1 >= $3, have_gobject=yes, true)
+if test "$have_gobject" = yes; then
+	AC_DEFINE(HAVE_GOBJECT)
+save_CPPFLAGS="$CPPFLAGS"
+save_LIBS="$LIBS"
+	CPPFLAGS="$GOBJECT_CFLAGS $CPPFLAGS"
+	LIBS="$GOBJECT_LIBS $LIBS"
+	AC_SUBST(GOBJECT_CFLAGS)
+	AC_SUBST(GOBJECT_LIBS)
+	CPPFLAGS="$save_CPPFLAGS"
+	LIBS="$save_LIBS"
+else
+  r="libgobject-dev or gobject?-devel"
+  ver="`pkg-config --modversion $1`"
+  STEPMAKE_ADD_ENTRY($2, ["$r >= $3 (installed: $ver)"])
+fi
+])
+
 AC_DEFUN(STEPMAKE_FREETYPE2, [
 PKG_CHECK_MODULES(FREETYPE2, $1 >= $3, have_freetype2=yes, true)
 if test "$have_freetype2" = yes; then
diff --git a/config.make.in b/config.make.in
index 420600ae8e..c9e1d992da 100644
--- a/config.make.in
+++ b/config.make.in
@@ -15,11 +15,12 @@ FREETYPE2_CFLAGS = @FREETYPE2_CFLAGS@
 GUILE_CFLAGS = @GUILE_CFLAGS@
 PANGO_FT2_CFLAGS = @PANGO_FT2_CFLAGS@
 PYTHON_CFLAGS = @PYTHON_CFLAGS@
+GLIB_CLFAGS = @GLIB_CFLAGS@ @GOBJECT_CFLAGS@
 
 CONFIG_CPPFLAGS = @CPPFLAGS@
 CONFIG_DEFINES = @DEFINES@
 
-CONFIG_CFLAGS = @CFLAGS@ $(GUILE_CFLAGS) $(FREETYPE2_CFLAGS) $(PANGO_FT2_CFLAGS)
+CONFIG_CFLAGS = @CFLAGS@ $(GLIB_CFLAGS)$(GUILE_CFLAGS) $(FREETYPE2_CFLAGS) $(PANGO_FT2_CFLAGS)
 CONFIG_CXXFLAGS = @CXXFLAGS@ $(GUILE_CFLAGS) $(FREETYPE2_CFLAGS) $(PANGO_FT2_CFLAGS)
 
 FONTCONFIG_LIBS = @FONTCONFIG_LIBS@
@@ -28,8 +29,9 @@ FREETYPE2_LIBS = @FREETYPE2_LIBS@
 PANGO_FT2_LIBS = @PANGO_FT2_LIBS@
 PYTHON_LIBS = @PYTHON_LDFLAGS@
 CXXABI_LIBS = @CXXABI_LIBS@
+GLIB_LIBS = @GLIB_LIBS@ @GOBJECT_LIBS@
 
-CONFIG_LIBS = @LIBS@ @EXTRA_LIBS@ $(GUILE_LIBS) $(PANGO_FT2_LIBS) $(FONTCONFIG_LIBS) $(FREETYPE2_LIBS)
+CONFIG_LIBS = @LIBS@ @EXTRA_LIBS@ $(GLIB_LIBS) $(GUILE_LIBS) $(PANGO_FT2_LIBS) $(FONTCONFIG_LIBS) $(FREETYPE2_LIBS)
 CONFIG_LDFLAGS = @LDFLAGS@
 
 PACKAGE = @PACKAGE@
diff --git a/configure.ac b/configure.ac
index e53bfcc4d6..bd1db31bdd 100644
--- a/configure.ac
+++ b/configure.ac
@@ -283,6 +283,8 @@ if test "$have_pangoft2_with_otf_feature" != yes ; then
 fi
 STEPMAKE_FONTCONFIG(fontconfig, REQUIRED, 2.4.0)
 STEPMAKE_FREETYPE2(freetype2, REQUIRED, 2.1.10)
+STEPMAKE_GLIB(glib-2.0, REQUIRED,2.44)
+STEPMAKE_GOBJECT(gobject-2.0, REQUIRED,2.44)
 
 STEPMAKE_WINDOWS
 
-- 
2.21.0

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

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-03 Thread Werner LEMBERG



> I think it is clear that we really need to test for and link against
> the glib-2.0 and gobject-2.0 libraries.

OK.  Do you have time to prepare a patch?


Werner

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

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-03 Thread Knut Petersen


Hi Werner!

I always thought that `pkg-config' resolves dependencies recursively.
Even with your `pangoft2.pc' file it should check the dependencies in
`pango.fc', right?  And there I see

   Requires: glib-2.0 gobject-2.0

Tumbleweed also moved those dependencies to 'Require.private' ;-)

But I guess this looks different for you, too.

Maybe a packaging error of pango?

It seems we have to add a test for pango to circumvent the problem...


We do use glib-2.0 and gobject-2.0 symbols directly (at least in lily/all-font-metrics.cc, lily/general-scheme.cc, lily/pano-font.cc, lily/pango-select.cc, lily/pango-select-scheme.cc, lily/pdf-scheme.cc), but we do not explicitly test for and link against the glib-2.0 and gobject-2.0 shared 
libraries. That works as long as the pango.pc and/or pangoft2.pc includes those libs after "Requires".


According to https://people.freedesktop.org/~dbn/pkg-config-guide.html the 
openSuSE Tumbleweed pangoft2.pc is correct:

   The most important pkg-config metadata fields are Requires, 
Requires.private, Cflags, Libs and Libs.private. They will define the metadata 
used by external projects to compile and link with the library.

   Requires and Requires.private define other modules needed by the library. It 
is usually preferred to use the private variant of Requires to avoid exposing 
unnecessary libraries to the program that is linking with your library. If the 
program will not be using the symbols of the required library,
   it should not be linking directly to that library. See the discussion of 
overlinking  
for a more thorough explanation.

   Since pkg-config always exposes the link flags of the Requires libraries, 
these modules will become direct dependencies of the program. On the other 
hand, libraries from Requires.private will only be included when static 
linking. For this reason, it is usually only appropriate to add modules
   from the same package in Requires.

   The Libs field contains the link flags necessary to use that library. In 
addition, Libs and Libs.private contain link flags for other libraries not 
supported by pkg-config. Similar to the Requires field, it is preferred to add 
link flags for external libraries to the Libs.private field so
   programs do not acquire an additional direct dependency.

   Finally, the Cflags contains the compiler flags for using the library. 
Unlike the Libs field, there is not a private variant of Cflags. This is 
because the data types and macro definitions are needed regardless of the 
linking scenario.

I think it is clear that we really need to test for and link against the 
glib-2.0 and gobject-2.0 libraries.

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

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-02 Thread Werner LEMBERG


> pkg-config --libs "pangoft2 >= 1.38.0" gives
> 
>-lpangoft2-1.0 -lpango-1.0 -lfontconfig -lfreetype

Not for me.  I get

  -L/usr/local/lib64 -lpangoft2-1.0 -lpango-1.0 \
  -lgobject-2.0 -lglib-2.0 -lfontconfig -lfreetype

> Weird. Look at /usr/lib64/pkgconfig/pangoft2.pc:
> 
>prefix=/usr
>libdir=${prefix}/lib64
>includedir=${prefix}/include
> 
>Name: Pango FT2 and Pango Fc
>Description: Freetype 2.0 and fontconfig font support for Pango
>Version: 1.43.0
>Requires: pango, freetype2, fontconfig >=  2.11.91
>Requires.private: glib-2.0 >=  2.38.0, gobject-2.0 >=  2.38.0, fribidi
>>=  0.19.7, libthai >=  0.1.9, harfbuzz >=  1.4.2, xrender, xft >= 
>2.0.0, cairo >= 1.12.10
>Libs: -L${libdir} -lpangoft2-1.0
> 
> Is there a difference to the pangoft2.pc on your system?

Yes.  I have version 1.40.13, and the `Requires.private' list only
contains `harfbuzz'.

I always thought that `pkg-config' resolves dependencies recursively.
Even with your `pangoft2.pc' file it should check the dependencies in
`pango.fc', right?  And there I see

  Requires: glib-2.0 gobject-2.0

But I guess this looks different for you, too.

Maybe a packaging error of pango?

It seems we have to add a test for pango to circumvent the problem...


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

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-02 Thread Knut Petersen


Hi Werner!

I added libgobject-2.0 to LIBS: "export LIBS='-lglib-2.0
-lgobject-2.0'", and after that building the lilypond executable
succeeded again.

Hmm.  LilyPond doesn't explicitly test for glib; it relies on
PANGO_FT2_LIBS, which should always add those two libraries for
building the `lilypond' binary.  For example, I see the following in
my `config.log' file:

   configure:9658: checking PANGO_FT2_LIBS
   configure:9661: result: -L/usr/local/lib64 -lpangoft2-1.0 \
   -lpango-1.0 -lgobject-2.0 -lglib-2.0 \
   -lfontconfig -lfreetype

Why is this not sufficient on your system?


configure has:

   $as_echo_n "checking PANGO_FT2_LIBS... " >&6; }
    PANGO_FT2_LIBS=`$PKG_CONFIG --libs "pangoft2 >= 1.38.0"`
    { $as_echo "$as_me:${as_lineno-$LINENO}: result: $PANGO_FT2_LIBS" 
>&5
   $as_echo "$PANGO_FT2_LIBS" >&6; }


pkg-config --libs "pangoft2 >= 1.38.0" gives

   -lpangoft2-1.0 -lpango-1.0 -lfontconfig -lfreetype

and pkg-config --cflags "pangoft2 >= 1.38.0" gives

   -I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include 
-I/usr/include/pixman-1 -I/usr/include/libdrm -I/usr/include/libpng16 
-I/usr/include/uuid -I/usr/include/freetype2


Weird. Look at /usr/lib64/pkgconfig/pangoft2.pc:

   prefix=/usr
   libdir=${prefix}/lib64
   includedir=${prefix}/include

   Name: Pango FT2 and Pango Fc
   Description: Freetype 2.0 and fontconfig font support for Pango
   Version: 1.43.0
   Requires: pango, freetype2, fontconfig >=  2.11.91
   Requires.private: glib-2.0 >=  2.38.0, gobject-2.0 >=  2.38.0, fribidi >=  0.19.7, 
libthai >=  0.1.9, harfbuzz >=  1.4.2, xrender, xft >=  2.0.0, cairo >= 1.12.10
   Libs: -L${libdir} -lpangoft2-1.0

Is there a difference to the pangoft2.pc on your system?

Knut


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

Re: Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-06-01 Thread Werner LEMBERG



> After some time without building lilypond I realized that my
> openSuSE Tumbleweed system had changed enough to be unable to build
> lilypond with my old and proven script.  The problem is that some
> required libraries are missing from the g++ command line that should
> produce the lilypond executable: [...]

I don't see this on my just installed openSUSE Leap 15.1 system, which
uses ld 2.31.1 and g++ 7.4.0 and which normally is quite similar to
Tumbleweed.

> I added libgobject-2.0 to LIBS: "export LIBS='-lglib-2.0
> -lgobject-2.0'", and after that building the lilypond executable
> succeeded again.

Hmm.  LilyPond doesn't explicitly test for glib; it relies on
PANGO_FT2_LIBS, which should always add those two libraries for
building the `lilypond' binary.  For example, I see the following in
my `config.log' file:

  configure:9658: checking PANGO_FT2_LIBS
  configure:9661: result: -L/usr/local/lib64 -lpangoft2-1.0 \
  -lpango-1.0 -lgobject-2.0 -lglib-2.0 \
  -lfontconfig -lfreetype

Why is this not sufficient on your system?


Werner

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

Build problem with binutils 2.3.2 / gcc 8.3.1: "DSO missing from command line"

2019-05-30 Thread Knut Petersen


Hi everybody!

After some time without building lilypond I realized that my openSuSE 
Tumbleweed system had changed enough to be unable to build lilypond with my old 
and proven script. The problem is that some required libraries are missing from 
the g++ command line that should produce the lilypond executable:

   make[2]: Leaving directory `/home/knut/sources/lily/build/flower
   g++ -o out/lilypond  [...] ./out/general-scheme.o [...]./out/pango-font.o 
[...]  ./out/../../flower/out/library.a -ldl -lgobject-2.0  -pthread 
-L/home/knut/sources/lilybuilt/share/lilypond/lib64 -lguile -lltdl -lgmp 
-lcrypt -lm -lltdl -lgobject-2.0 -lpangoft2-1.0 -lpango-1.0 -lfontconfig
   -lfreetype -lfontconfig -lfreetype -lfreetype 
-Wl,-rpath,/home/knut/sources/lilybuilt/share/lilypond/lib64 
-Wl,-rpath,/home/knut/sources/lilybuilt/share/lilypond/lib64 
-Wl,-rpath,/home/knut/sources/lilybuilt/share/lilypond/lib64
   /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: 
./out/general-scheme.o: undefined reference to symbol 'g_spawn_sync'
   /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: 
/usr/lib64/libglib-2.0.so.0: error adding symbols: DSO missing from command line
   collect2: error: ld returned 1 exit status
   make[1]: *** [out/lilypond] Error 1
   make[1]: Target `all' not remade because of errors.
   make[1]: Leaving directory `/home/knut/sources/lily/build/lily'
   make: *** [all] Error 2

g_spawn_sync is used in lily/general-scheme.cc, it is provided by 
libglib-2.0.so.0, the linker finds that library but it complains because the 
library dependency is not explicitly provided on the command line.

An easy way to tell ld to use some additional libraries is to export a LIBS environment 
variable before ./configure is executed. So I added "export LIBS='-lglib-2.0'" 
at the top of my build script. But ld complained again:

   /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: 
./out/pango-font.o: undefined reference to symbol 'g_object_unref'
   /usr/lib64/gcc/x86_64-suse-linux/8/../../../../x86_64-suse-linux/bin/ld: 
/usr/lib64/libgobject-2.0.so.0: error adding symbols: DSO missing from command 
line

I added libgobject-2.0 to LIBS: "export LIBS='-lglib-2.0 -lgobject-2.0'", and 
after that building the lilypond executable succeeded again.

   ||

ld is:

   GNU ld (GNU Binutils; openSUSE Tumbleweed) 2.32
   Copyright (C) 2019 Free Software Foundation, Inc.
   This program is free software; you may redistribute it under the terms of
   the GNU General Public License version 3 or (at your option) a later version.
   This program has absolutely no warranty.

g++ is:

   g++ (SUSE Linux) 8.3.1 20190226 [gcc-8-branch revision 269204]
   Copyright (C) 2018 Free Software Foundation, Inc.
   This is free software; see the source for copying conditions. There is NO
   warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Knut



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

Re: Lilypond gcc45 build problem

2010-02-28 Thread Dave Plater

On 02/22/2010 08:52 PM, Jan Nieuwenhuizen wrote:
>
> Yes... it's always nice to have lily building with the latest and
> greatest - although I see that gcc-4.5.0 development currently has
> about 250 regressions, half of them serious ones.  I'm not sure
> if debugging this right now is helpful.
>
> I note that it builds and runs with gcc-4.5.0 from 20091018 - haven't
> verified if the doc builds.
>
> Greetings,
> Jan.
>
>
>   
I have no idea what went wrong with the lilypond build when it failed
with the original patch applied, I can only speculate that a dependency
was broken at exactly the right moment and caused me to spend a lot of
time searching for a non existent error. Lilypond is now building for
11.2 (gcc44) and factory standard (gcc45) with the attached patch which
is the one I posted previously.
Regards
Dave P
Index: lilypond-2.12.3/lily/spacing-spanner.cc
===
--- lilypond-2.12.3.orig/lily/spacing-spanner.cc
+++ lilypond-2.12.3/lily/spacing-spanner.cc
@@ -38,7 +38,7 @@ Spacing_spanner::get_columns (Grob *me_g
   vsize end = binary_search (all, (Grob*) me->get_bound (RIGHT),
 			 &Paper_column::less_than);  
   
-  all = vector::vector (all.begin () + start,
+  all = vector (all.begin () + start,
   all.begin () + end + 1);
   return all;
 }
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Lilypond gcc45 build problem

2010-02-22 Thread Jan Nieuwenhuizen

Op maandag 22-02-2010 om 19:09 uur [tijdzone +0200], schreef Dave
Plater:

Hi Dave,

> lilypond is no longer building for openSUSE Factory due to the switch to
> gcc45. I noticed from the git logs that you have worked on
> spacing-spanner.cc recently which is where gcc45 fails.

Yes, I noticed.

 I received a
> solution from the gcc maintainer of openSUSE which didn't work, it
> stopped the build error but then the documentation build failed on all
> repositories.

Are these related?  Does lily produce any output at all?

> Lilypond-2.13.13 also has the same problem and although
> the problem isn't that urgent now but in a few months lilypond will fail
> to build on all distros that have gcc45.

Yes... it's always nice to have lily building with the latest and
greatest - although I see that gcc-4.5.0 development currently has
about 250 regressions, half of them serious ones.  I'm not sure
if debugging this right now is helpful.

I note that it builds and runs with gcc-4.5.0 from 20091018 - haven't
verified if the doc builds.

Greetings,
Jan.




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

Re: Local Gub build problem

2008-07-16 Thread John Mandereau

On 2008/07/14 20:17 +, Mark Hanlon wrote:
> LILYPOND_REPO_URL=file://localhost/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource
> 
> # ugh - make this automatic.
> LILYPOND_DIRRED_BRANCH=localhost/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource/$(LILYPOND_BRANCH)
> LILYPOND_FLATTENED_BRANCH=localhost--home-maz-lilypondbuilds-mygub-gub-PatchedLilySource-$(LILYPOND_BRANCH)

> UnknownVcSystem: Cannot determine source: 
> url=file://localhost/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource,
> dir=/home/maz/lilypondbuilds/mygub/gub/downloads/PatchedLilySource
> make: *** [get-local] Error 1
> 
> I know it's got something to do with git and version control (it's
> expecting LILYPOND_REPO_URL to perhaps be a location to a local git
> repository?).

Although I never got this kind of error, I always made makefile
variables for source URL point to a Git (local or remote) repository, so
I guess the answer for this particular question is "yes".

HTH,
John



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

Local Gub build problem

2008-07-14 Thread Mark Hanlon


Hello,

I've been trying to use the local.build file that Han-Wen supplied to do a GUB 
build of a patched version of lilypond for the music notation project.

I have amended the contents of the local.build file to point to the location of 
my source code
which is
/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource

The amended contents of the local build are...

BUILD_PLATFORM=linux-x86
LILYPOND_WEB_CPU_COUNT=2

#LILYPOND_BRANCH=hwn
#LILYPOND_LOCAL_BRANCH=hwn
MINGIT_BRANCH=
LILYPOND_REPO_URL=file://localhost/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource

# ugh - make this automatic.
LILYPOND_DIRRED_BRANCH=localhost/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource/$(LILYPOND_BRANCH)
LILYPOND_FLATTENED_BRANCH=localhost--home-maz-lilypondbuilds-mygub-gub-PatchedLilySource-$(LILYPOND_BRANCH)

GUB_ONLINE_OPTION= -vvv --offline

get-local:
python bin/gub --platform=linux-x86 -vvv --offline --online 
--download-only 
'file://localhost/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource?branch=master'
all-stable:
$(MAKE) LILYPOND_BRANCH=stable-2.11.45 
LILYPOND_LOCAL_BRANCH=stable-2.11.45 all

all-clean-stable:
$(MAKE) LILYPOND_BRANCH=stable-2.11.45 
LILYPOND_LOCAL_BRANCH=stable-2.11.45 doc-clean

PLATFORMS=linux-x86 linux-64 linux-ppc freebsd-x86 freebsd-64 darwin-ppc 
darwin-x86 mingw

When I run  make -f local.make get-local
I get this error
UnknownVcSystem: Cannot determine source: 
url=file://localhost/home/maz/lilypondbuilds/mygub/gub/PatchedLilySource,
dir=/home/maz/lilypondbuilds/mygub/gub/downloads/PatchedLilySource
make: *** [get-local] Error 1

I know it's got something to do with git and version control (it's expecting 
LILYPOND_REPO_URL to perhaps be a location to a local git repository?).
I'm stumbling about in the dark a bit, Han-Wen I'm sorry to ask you again, but 
could you shed any light?

Thanks
Mark

_
Invite your Facebook friends to chat on Messenger
http://clk.atdmt.com/UKM/go/101719649/direct/01/

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

source build problem 2.9.24

2006-10-17 Thread Ian Stirling

  I asked about this with 2.9.22 and had no answer.

On FreeBSD RELEASE-6.1,
Failed to open: /usr/X11R6/lib/X11/fonts/bitstream-vera/VeraBd.pfb

  This file is not in the bitstream-vera on my system.
Please, where can I get it or make it?

Ian
--


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

source build problem 2.9.22

2006-10-12 Thread Ian Stirling

  I have the following error trying to build 2.9.22 from source
on a FreeBSD 6.1-RELEASE system with bitstream-vera 1.10_2.

Cannot open /usr/X11R6/lib/X11/fonts/bitstream-vera/VeraBd.pfb
The requested file, VeraBd.pfb, does not exist
Open: Failed to open: /usr/X11R6/lib/X11/fonts/bitstream-vera/VeraBd.pfb
Called from...
 ../buildscripts/pfx2ttf.fontforge: line 3
gmake[1]: *** [out/CenturySchL-Ital.otf] Error 1

  There are ttf files in that directory but none of type pfb.

  This file is not in the file
 ttf-bitstream-vera-1.10.tar.gz 16-Apr-2003 21:54  342K 
that I fetched from
http://ftp.gnome.org/pub/GNOME/sources/ttf-bitstream-vera/1.10/

  Does anyone know where I can get this file and any others
that might be associated with this error?

Ian
--


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

Re: About lilypond's build problem with debian

2006-07-25 Thread Thomas Bushnell BSG

Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:

> Thomas Bushnell BSG schreef:
>> The problem is that lilypond's build system assumes that lilypond is
>> already installed on the system.
>>
>> Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out
>> in the thread, it is setting LILYPONDPREFIX *incorrectly*, and the
>> reason the builds are working for Han-Wen is that he already has
>> lilypond installed.
>
> this is false BTW, as I don't have lilypond installed at all.  I
> always run from the development tree.

On April 27 I submitted a bug report for 2.8.1, and explained the fix
that solves the problem.  I have no idea about 2.9 and what changes
you say have been made there.

Thomas


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

Re: About lilypond's build problem with debian

2006-07-25 Thread Ludovic RESLINGER

Re,

I have found why it builed for you and not on
my system.

The python version installed on my system was a
2.4 version. I had backported on a 2.3 version,
and the problem seem solved.

It will be interesting to know why there is this problem
with new versions of python, because if one
day Python is 2.4 by default, the bug could be a
problem to build. I don't know if it is a problem of
Debian Package or if it is a general problem of python 2.4.
I will test more...

So, for Thomas BUSHNELL: I don't know if it is really a good idea to
wait Python 2.4 by default to release lilypond in debian :)

I hope that you will be satisfy of my report, this
time :).

-- 
.---.  Ludovic RESLINGER
   / \
   [EMAIL PROTECTED]@./ Trumpet Student in CNR
   /`\_/`\ Free Software Developer
  // )X( \\
 | \  :  )|_   _,'|   .''`.
/`\_`>  <_/ \ @==TTT=::_  |  : :'  :
\__/'---'\__/   ((_<=HHH___))   `.|  `. `'`
 `---UUU---'=> `-


signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: About lilypond's build problem with debian

2006-07-25 Thread Han-Wen Nienhuys


Thomas Bushnell BSG schreef:

The problem is that lilypond's build system assumes that lilypond is
already installed on the system.

Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out
in the thread, it is setting LILYPONDPREFIX *incorrectly*, and the
reason the builds are working for Han-Wen is that he already has
lilypond installed.


this is false BTW, as I don't have lilypond installed at all.  I always 
run from the development tree.


I would welcome a usable bugreport about this, as Ludovic has so far 
declined to produce one.



--

Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

Re: About lilypond's build problem with debian

2006-07-25 Thread Ludovic RESLINGER

On Tue, Jul 25, 2006 at 02:08:03AM -0700, Thomas Bushnell BSG wrote:
> Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> 
> > Thomas Bushnell BSG schreef:
> >
> >> I'm distressed that nobody has bothered to fix the bug since then.  In
> >> the thread on the mailing list you can see that if LILYPONDPREFIX is
> >> set correctly, the bug goes away.
> >
> > This issue has been addressed in a more robust manner in the 2.9
> > series, and I would welcome a backport of the changes; we haven't
> > found the time to do it.
> 
> Good to hear.  I think for Debian's purposes, setting LILYPONDPREFIX
> properly is probably the simplest solution.  I look forward to 2.10
> having a bettr fix in place.
> 
It doesn't work in 2.9 series, I have tested tomorrow.
Actually, the only one solution that I found is to make
an symbolic link of pythons scripts in python/ -> scripts/
When I did that, the bug seems to go away, and help2man seem
to make correctly his job. There is a problem for scripts in
scripts/ for finding files in python, and when I put them in
the same directory, the problem goes away.

I think there is a problem again, the new implementation of
LILYPONDPREFIX in 2.9 series doesn't seem to correct 
the problem.

-- 
.---.  Ludovic RESLINGER
   / \
   [EMAIL PROTECTED]@./ Trumpet Student in CNR
   /`\_/`\ Free Software Developer
  // )X( \\
 | \  :  )|_   _,'|   .''`.
/`\_`>  <_/ \ @==TTT=::_  |  : :'  :
\__/'---'\__/   ((_<=HHH___))   `.|  `. `'`
 `---UUU---'=> `-


signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: About lilypond's build problem with debian

2006-07-25 Thread Thomas Bushnell BSG

Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:

> Thomas Bushnell BSG schreef:
>
>> I'm distressed that nobody has bothered to fix the bug since then.  In
>> the thread on the mailing list you can see that if LILYPONDPREFIX is
>> set correctly, the bug goes away.
>
> This issue has been addressed in a more robust manner in the 2.9
> series, and I would welcome a backport of the changes; we haven't
> found the time to do it.

Good to hear.  I think for Debian's purposes, setting LILYPONDPREFIX
properly is probably the simplest solution.  I look forward to 2.10
having a bettr fix in place.

Thomas


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

Re: About lilypond's build problem with debian

2006-07-24 Thread Ludovic RESLINGER

On Sun, Jul 23, 2006 at 12:25:42PM +0200, Han-Wen Nienhuys wrote:
> Thomas Bushnell BSG schreef:
> 
> >I'm distressed that nobody has bothered to fix the bug since then.  In
> >the thread on the mailing list you can see that if LILYPONDPREFIX is
> >set correctly, the bug goes away.
> 
> This issue has been addressed in a more robust manner in the 2.9 series, 
> and I would welcome a backport of the changes; we haven't found the time 
> to do it.
> 

Hi,

I tried to build lilypond 2.9.11 to see if the problem goes away with
2.9 series. The problem seems to be the same with 2.9 series, I had
the same build error: 

/usr/bin/perl /home/lr/lilypond-2.9.11/buildscripts/out/help2man
out/convert-ly > out/convert-ly.1
help2man: can't get `--help' info from out/convert-ly
make[1]: *** [out/convert-ly.1] Error 1
make[1]: Leaving directory `/home/lr/lilypond-2.9.11/scripts'
make: *** [all] Error 2

And when I do :
  scripts/out/convert-ly

Traceback (most recent call last):
  File "scripts/out/convert-ly", line 39, in 
  import lilylib as ly
ImportError: No module named lilylib

When I do LILYPONDPREFIX=out scripts/out/convert-ly

Usage: convert-ly [OPTIONS] FILE

Update LilyPond input to newer version.  By default, update from the
version taken from the \version command, to the current LilyPond
version.
[...]

So the problem seem to stay the same with new implementation of
LILYPONDPREFIX in 2.9 series.

-- 
.---.  Ludovic RESLINGER
   / \
   [EMAIL PROTECTED]@./ Trumpet Student in CNR
   /`\_/`\ Free Software Developer
  // )X( \\
 | \  :  )|_   _,'|   .''`.
/`\_`>  <_/ \ @==TTT=::_  |  : :'  :
\__/'---'\__/   ((_<=HHH___))   `.|  `. `'`
 `---UUU---'=> `-


signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: About lilypond's build problem with debian

2006-07-23 Thread Han-Wen Nienhuys


Thomas Bushnell BSG schreef:


I'm distressed that nobody has bothered to fix the bug since then.  In
the thread on the mailing list you can see that if LILYPONDPREFIX is
set correctly, the bug goes away.


This issue has been addressed in a more robust manner in the 2.9 series, 
and I would welcome a backport of the changes; we haven't found the time 
to do it.


--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen

LilyPond Software Design
 -- Code for Music Notation
http://www.lilypond-design.com



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

Re: About lilypond's build problem with debian

2006-07-22 Thread Ludovic RESLINGER

On Fri, Jul 21, 2006 at 04:57:14PM -0700, Thomas Bushnell BSG wrote:
> Ludovic RESLINGER <[EMAIL PROTECTED]> writes:
> 
> > I saw in archive some messages about a problem to build lilypond in
> > debian unstable. I think this is not a problem of python's version, because
> > I tested to build with python2.4 and python2.5, and the problem stay the
> > same:
> >
> > chmod 755 out/convert-ly
> > /usr/bin/perl /home/me/lilypond-2.8.4/buildscripts/out/help2man
> > out/convert-ly > out/convert-ly.1
> > help2man: can't get `--help' info from out/convert-ly
> > make[1]: *** [out/convert-ly.1] Error 1
> > make[1]: Leaving directory `/home/me/lilypond-2.8.4/scripts'
> > make: *** [all] Error 2
> 
> I reported this bug on lilypond-devel back on April 27, in a message
> titled "building lilypond 2.8.1 on Debian unstable".
> 
> The problem is that lilypond's build system assumes that lilypond is
> already installed on the system.
> 
> Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out
> in the thread, it is setting LILYPONDPREFIX *incorrectly*, and the
> reason the builds are working for Han-Wen is that he already has
> lilypond installed.
> 
> I'm distressed that nobody has bothered to fix the bug since then.  In
> the thread on the mailing list you can see that if LILYPONDPREFIX is
> set correctly, the bug goes away.
> 
> Thomas
> 

Hi,

I saw yours posts in April. I tested with the latest stable upstream, the 2.8.4,
and in effect, the bug isn't corrected.

I can do the same observation when I try to do LILYPONDPREFIX value on "out". 
But
if it is possible to display help of python script, it isn't possible
or help2man make his work.

Regards,
-- 
.---.  Ludovic RESLINGER
   / \
   [EMAIL PROTECTED]@./ Trumpet Student in CNR
   /`\_/`\ Free Software Developer
  // )X( \\
 | \  :  )|_   _,'|   .''`.
/`\_`>  <_/ \ @==TTT=::_  |  : :'  :
\__/'---'\__/   ((_<=HHH___))   `.|  `. `'`
 `---UUU---'=> `-


signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: About lilypond's build problem with debian

2006-07-21 Thread Thomas Bushnell BSG

Ludovic RESLINGER <[EMAIL PROTECTED]> writes:

> I saw in archive some messages about a problem to build lilypond in
> debian unstable. I think this is not a problem of python's version, because
> I tested to build with python2.4 and python2.5, and the problem stay the
> same:
>
> chmod 755 out/convert-ly
> /usr/bin/perl /home/me/lilypond-2.8.4/buildscripts/out/help2man
> out/convert-ly > out/convert-ly.1
> help2man: can't get `--help' info from out/convert-ly
> make[1]: *** [out/convert-ly.1] Error 1
> make[1]: Leaving directory `/home/me/lilypond-2.8.4/scripts'
> make: *** [all] Error 2

I reported this bug on lilypond-devel back on April 27, in a message
titled "building lilypond 2.8.1 on Debian unstable".

The problem is that lilypond's build system assumes that lilypond is
already installed on the system.

Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out
in the thread, it is setting LILYPONDPREFIX *incorrectly*, and the
reason the builds are working for Han-Wen is that he already has
lilypond installed.

I'm distressed that nobody has bothered to fix the bug since then.  In
the thread on the mailing list you can see that if LILYPONDPREFIX is
set correctly, the bug goes away.

Thomas

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

Re: About lilypond's build problem with debian

2006-07-20 Thread Ludovic RESLINGER

On Wed, Jul 19, 2006 at 07:47:35PM +0200, Mats Bengtsson wrote:
> If you run
> scripts/out/convert-ly --help
> from the lilypond/ directory, you will get a much more informative 
> error message that might
> help you find out what the problem is.
> 
>  /Mats
> 

Hello

Thank you for your answer.

When I did that I had this answer :

  scripts/out/convert-ly --help

  Traceback (most recent call last):
  File "scripts/out/convert-ly", line 39, in 
import lilylib as ly
  ImportError: No module named lilylib

So, I thought "convert-ly" didn't find lilylib.py.
To test, I copied lilylib.py into scripts/out/, 
and I had that :

   cp -a python/lilylib.py scripts/out/
   scripts/out/convert-ly --help

Traceback (most recent call last):
   File "scripts/out/convert-ly", line 42, in 
 from convertrules import *
   ImportError: No module named convertrules

It seem to found lilylib...
So, this time, I'd copied all tree in scripts/out :

   cp -a python/* scripts/out/
   scripts/out/convert-ly --help

   Usage: convert-ly [OPTIONS] FILE
   Update LilyPond input to newer version.  By default, update from the
   version taken from the \version command, to the current LilyPond
   version.

   Examples:
   etc...

It seemed to work at this time. So I deleted the scripts/out/convert-ly.1
whitch is empty, because I wanted to see if build failed anymore with
the python file in scripts/out/
   rm -rf scripts/out/convert-ly.1
   make

   [...]
   make[1]: Leaving directory `/home/lr/lilypond-2.8.4/python'
   make[1]: Entering directory `/home/lr/lilypond-2.8.4/scripts'
   /usr/bin/perl /home/lr/lilypond-2.8.4/buildscripts/out/help2man
   out/convert-ly > out/convert-ly.1
   help2man: can't get `--help' info from out/convert-ly
   make[1]: *** [out/convert-ly.1] Error 1
   make[1]: Leaving directory `/home/lr/lilypond-2.8.4/scripts'
   make: *** [all] Error 2

The error message is the same, it is strange because files are in the
scripts/out tree and scripts/out/convert-ly --help display help without
errors.

I think there is a problem somewhere to find the files but I don't see where is
it. I tried to change value of LILYPONDPREFFIX in
make/lilypond-vars.make but error stay the same.

-- 
.---.  Ludovic RESLINGER
   / \
   [EMAIL PROTECTED]@./ Trumpet Student in CNR
   /`\_/`\ Free Software Developer
  // )X( \\
 | \  :  )|_   _,'|   .''`.
/`\_`>  <_/ \ @==TTT=::_  |  : :'  :
\__/'---'\__/   ((_<=HHH___))   `.|  `. `'`
 `---UUU---'=> `-

signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: About lilypond's build problem with debian

2006-07-19 Thread Mats Bengtsson


If you run
scripts/out/convert-ly --help
from the lilypond/ directory, you will get a much more informative 
error message that might

help you find out what the problem is.

 /Mats

Quoting Ludovic RESLINGER <[EMAIL PROTECTED]>:


Hello,

I saw in archive some messages about a problem to build lilypond in
debian unstable. I think this is not a problem of python's version, because
I tested to build with python2.4 and python2.5, and the problem stay the
same:

chmod 755 out/convert-ly
/usr/bin/perl /home/me/lilypond-2.8.4/buildscripts/out/help2man
out/convert-ly > out/convert-ly.1
help2man: can't get `--help' info from out/convert-ly
make[1]: *** [out/convert-ly.1] Error 1
make[1]: Leaving directory `/home/me/lilypond-2.8.4/scripts'
make: *** [all] Error 2

I readed messages, but I didn't see any solution.

Thank for answers,

Cheers,

--
   .---.  Ludovic RESLINGER
  / \
  [EMAIL PROTECTED]@./ Trumpet Student in CNR
  /`\_/`\ Free Software Developer
 // )X( \\
| \  :  )|_   _,'|   .''`.
/`\_`>  <_/ \ @==TTT=::_  |  : :'  :
\__/'---'\__/   ((_<=HHH___))   `.|  `. `'`
`---UUU---'=> `-







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

About lilypond's build problem with debian

2006-07-19 Thread Ludovic RESLINGER

Hello,

I saw in archive some messages about a problem to build lilypond in
debian unstable. I think this is not a problem of python's version, because
I tested to build with python2.4 and python2.5, and the problem stay the
same:

chmod 755 out/convert-ly
/usr/bin/perl /home/me/lilypond-2.8.4/buildscripts/out/help2man
out/convert-ly > out/convert-ly.1
help2man: can't get `--help' info from out/convert-ly
make[1]: *** [out/convert-ly.1] Error 1
make[1]: Leaving directory `/home/me/lilypond-2.8.4/scripts'
make: *** [all] Error 2

I readed messages, but I didn't see any solution.

Thank for answers,

Cheers,

-- 
.---.  Ludovic RESLINGER
   / \
   [EMAIL PROTECTED]@./ Trumpet Student in CNR
   /`\_/`\ Free Software Developer
  // )X( \\
 | \  :  )|_   _,'|   .''`.
/`\_`>  <_/ \ @==TTT=::_  |  : :'  :
\__/'---'\__/   ((_<=HHH___))   `.|  `. `'`
 `---UUU---'=> `-


signature.asc
Description: Digital signature
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: cygwin build problem in mf

2005-02-09 Thread Peter Leschev

Hi,
   trap for young players...
   make SHELL=/bin/bashdid the trick
   Thanks for the quick response!
Peter
- Original Message - 
From: "Jan Nieuwenhuizen" <[EMAIL PROTECTED]>
To: "Peter Leschev" <[EMAIL PROTECTED]>
Cc: 
Sent: Wednesday, February 09, 2005 10:42 PM
Subject: Re: cygwin build problem in mf


Peter Leschev writes:
I'm trying to build the latest from CVS under cygwin, and I'm 
getting the following error. Any ideas?
Yes.
mv feta11.{pfa,pfb,svg} ./out
mv: cannot stat `feta11.{pfa,pfb,svg}': No such file or directory
{} is a bashism, use bash as /bin/sh, or try make SHELL=/bin/bash
While this should maybe be fixed, Cygwin is the only unix on earth
to use ash for /bin/sh (flame on).
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


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

Re: cygwin build problem in mf

2005-02-09 Thread Jan Nieuwenhuizen

Peter Leschev writes:

> I'm trying to build the latest from CVS under cygwin, and I'm getting 
> the following error. Any ideas?

Yes.

> mv feta11.{pfa,pfb,svg} ./out
> mv: cannot stat `feta11.{pfa,pfb,svg}': No such file or directory

{} is a bashism, use bash as /bin/sh, or try make SHELL=/bin/bash

While this should maybe be fixed, Cygwin is the only unix on earth
to use ash for /bin/sh (flame on).

Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org


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

cygwin build problem in mf

2005-02-09 Thread Peter Leschev




Hi,
 
        I'm trying to 
build the latest from CVS under cygwin, and I'm getting the following error. Any 
ideas?
 
Regards,
Peter
 
 
make[1]: Entering directory 
`/cygdrive/c/sandbox/org/lilypond/lilypond/mf'mftrace --encoding feta11.enc 
--no-afm -I ./out/ --formats=pfa,pfb,svg feta11mftrace 1.1.2Font 
`feta11'...Warning: no extra font information for this font.Consider 
writing a XX_guess_font_info() routine.Using encoding file: 
`./out/feta11.enc'Running Metafont...Tracing bitmaps... 
[33][34][35][36][37][38][39][40][41][42][43][44][45][46][47][48][49][50][51][52][53][54][55][56][57][58][59][60][61][62][63][64][65][66][67][68][69][70][71][72][73][74][75][76][77][78][79][80][81][82][83][84][85][86][87][88][89][90][91][92][93][94][95][96][97][98][99][100][101][102][103][104][105][106][107][108][109][110][111][112][113][114][115][116][117][118][119][120][121][122][123][124][125][126][127][128][129][130][131][132][133][134][135][136][137][138][139][140][141][142][143][144][145][146][147][148][149][150][151][152][153][154][155][156][157][158][159][160][161][162][163][164][165][166][167][168][169][170][171][172][173][174][175][176][177][178][179][180][181][182][183][184][185][186][187][188][189][190][191][192][193][194]Assembling 
raw font to `feta11.pfa'...Copyright (c) 2000-2005 by George 
Williams. Executable based on sources from 18:21 17-Jan-2005.mv 
feta11.{pfa,pfb,svg} ./outmv: cannot stat `feta11.{pfa,pfb,svg}': No such 
file or directorymake[1]: *** [out/feta11.pfa] Error 1make[1]: Leaving 
directory `/cygdrive/c/sandbox/org/lilypond/lilypond/mf'make: *** [all] 
Error 2
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel

another build problem

2004-10-30 Thread Laura Conrad


Again, Debian, Sid, 2.4.0.

rm -f ./out/lexer.dep; DEPENDENCIES_OUTPUT="./out/lexer.dep ./out/lexer.o" g++ -c   
-DHAVE_CONFIG_H  -DSTRING_UTILS_INLINED -Iinclude -I./out -I../flower/include 
-I../flower/./out -I../flower/include -O2 -finline-functions -g -pipe   
-I/usr/include/python2.3   -O2 -finline-functions -g -pipe   
-I/usr/include/python2.3   -W -Wall -Wconversion  -o out/lexer.o out/lexer.cc
g++: Internal error: Terminated (program cc1plus)
Please submit a full bug report.
See http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions,
see .

{standard input}: Assembler messages:
{standard input}:29286: Warning: end of file not at end of a line; newline inserted
{standard input}:30127: Error: unknown pseudo-op: `.lcfi17'
make[1]: *** [out/lexer.o] Error 1
rm out/lexer.cc
make[1]: Leaving directory `/home/lconrad/src/lilypond/lilypond-2.4.0/lily'
make: *** [all] Error 2

-- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097  fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139




___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Newbie Alert--build problem CVS

2002-07-16 Thread Zach Brewster-Geisz


Thus spake Christian Hitz:
>Am Dienstag den, 16. Juli 2002, um 11:45, schrieb Jan Nieuwenhuizen:
>>
>>Please send a patch if you get it working, maybe addding small
>>comments as above.
>
>With the attached patch applied to the current CVS, you can build 
>lilypond on MacOS X (and i hope also on darwin).
>
>Jan: your hint did the trick.

Ah. ha... I got the latest CVS and it built after I applied a patch 
of my own devising to score.cc. (It was a kludge, so I won't include 
it here.) I bet your patch will fix the problem I had, but probably 
does it better.

In any case, it works!  Now all I have to do is find a full score to 
"Messiah" that's in the public domain...

Thanks, everybody.
Zach

-- 
Don't bother reading this.  It's not funny.
--
Animation: http://www.hash.com/users/zachbg/
Family: http://brewstergeisz.cjb.net

___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel

Re: Newbie Alert--build problem CVS

2002-07-16 Thread Christian Hitz


Am Dienstag den, 16. Juli 2002, um 11:45, schrieb Jan Nieuwenhuizen:
>
> Please send a patch if you get it working, maybe addding small
> comments as above.

With the attached patch applied to the current CVS, you can build 
lilypond on MacOS X (and i hope also on darwin).

Jan: your hint did the trick.

Christian



macosx.patch
Description: application/text



Get my PGP-Public Key from:
http://people.ee.ethz.ch/~chitz/public-key.pgp




PGP.sig
Description: PGP signature

Newbie Alert--build problem CVS

2002-07-16 Thread Han-Wen Nienhuys


[EMAIL PROTECTED] writes:
> Hello.  Long time listener, first time caller.
> 
> I get the following error when building from the latest (well, this 
> morning's) CVS:

Thanks for the report ; should be fixed in CVS.

> I'm using gcc v. 2.95, building on Apple Darwin 1.4.1.  I have the 
> Fink installation working fine, but I'm trying to track the bleeding 
> edge in anticipation of 1.6.

Good, let us know about other problems.

-- 

Han-Wen Nienhuys   |   [EMAIL PROTECTED]| http://www.cs.uu.nl/~hanwen/


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel

Re: Newbie Alert--build problem CVS

2002-07-16 Thread Jan Nieuwenhuizen

Zach Brewster-Geisz <[EMAIL PROTECTED]> writes:

> Hello.  Long time listener, first time caller.

Loud and clear, over.

> I get the following error when building from the latest (well, this
> morning's) CVS:

> In file included from note-collision.cc:11:
> ../flower/include/drul-array.hh: In instantiation of
> `Drul_array>':
> include/note-collision.hh:31:  instantiated from here
> ../flower/include/drul-array.hh:22: invalid use of undefined type
> `struct Link_array'
> ../flower/include/flower-proto.hh:14: forward declaration of `struct
> Link_array'

That's not so nice.  It looks like your compiler

> I'm using gcc v. 2.95, building on Apple Darwin 1.4.1.

doesn't accept the declaration in flower-proto.hh

template struct Link_array;

when it sees Drul_array>.

You could try adding

#include "parray.hh"  /* gcc 2.95 on Darwin needs full declaration */

as the first include in note-column.cc, and see what happens.  If that
doesn't help, you may even have to comment-out the template
declarations in flower-proto.hh.  Then you'll may well experience more
of these 'undefined type' errors.

Please send a patch if you get it working, maybe addding small
comments as above.

> Any assistance is appreciated, though I somehow think I'll probably
> wind up waiting for the next Fink release.  :)

What makes you fink that?

> Don't bother reading this.  It's not funny.

Oops, sorry.

Jan.

-- 
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien   | http://www.lilypond.org

___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel

Newbie Alert--build problem CVS

2002-07-15 Thread Zach Brewster-Geisz


Hello.  Long time listener, first time caller.

I get the following error when building from the latest (well, this 
morning's) CVS:



rm -f ./out/note-collision.dep; 
DEPENDENCIES_OUTPUT="./out/note-collision.dep ./out/note-collision.o" 
c++ -c -DHAVE_CONFIG_H  -DSTRING_UTILS_INLINED -Iinclude -I./out 
-I.././lib/include -I../lib/./out -I.././flower/include 
-I../flower/./out -I../flower/include -no-cpp-precomp -I/sw/include 
-O2 -finline-functions -g  -I/sw/include -no-cpp-precomp 
-I/sw/include -O2 -finline-functions -g -I/sw/include -Wall  -W 
-Wmissing-prototypes
-Wconversion  -o out/note-collision.o 
note-collision.c
In file included from note-collision.cc:11:
../flower/include/drul-array.hh: In instantiation of 
`Drul_array>':
include/note-collision.hh:31:  instantiated from here
../flower/include/drul-array.hh:22: invalid use of undefined type 
`struct Link_array'
../flower/include/flower-proto.hh:14: forward declaration of `struct 
Link_array'
../flower/include/drul-array.hh:51: confused by earlier errors, bailing out
make[1]: *** [out/note-collision.o] Error 1
make: *** [all] Error 2

I'm using gcc v. 2.95, building on Apple Darwin 1.4.1.  I have the 
Fink installation working fine, but I'm trying to track the bleeding 
edge in anticipation of 1.6.

Any assistance is appreciated, though I somehow think I'll probably 
wind up waiting for the next Fink release.  :)

Zach
-- 
Don't bother reading this.  It's not funny.
--
Animation: http://www.hash.com/users/zachbg/
Family: http://brewstergeisz.cjb.net

___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel

Re: build problem with current cvs

2002-07-13 Thread Laura Conrad

> "Han-Wen" == Han-Wen  <[EMAIL PROTECTED]> writes:

Han-Wen> [EMAIL PROTECTED] writes:
>> I just upped CVS, and when I run "make", I get:

Han-Wen> run make clean

Now I get:

makeinfo --output=./out/lilypond.info out/lilypond.nexi
out/lilypond.nexi:269: Node `Preface' requires a sectioning command (e.g. @unnumbered).
out/lilypond.nexi:270: Unknown command `unnumberedchapter'.
./out/lilypond.nexi:54: Next field of node `Top' not pointed to.
./out/lilypond.nexi:269: This node (Preface) has the bad Prev.
./out/lilypond.nexi:269: `Preface' has no Up field.
./out/lilypond.nexi:314: Prev field of node `Introduction' not pointed to.
./out/lilypond.nexi:269: This node (Preface) has the bad Next.
makeinfo: Removing output file `./out/lilypond.info' due to errors; use --force to 
preserve.
make[2]: *** [out/lilypond.info] Error 2
rm out/lilypond.nexi
make[2]: Leaving directory `/home/lconrad/src/lilypond/cvs/lilypond/Documentation/user'
make[1]: *** [all] Error 2
rm out/index.texi
make[1]: Leaving directory `/home/lconrad/src/lilypond/cvs/lilypond/Documentation'
make: *** [all] Error 2
You have new mail in /var/spool/mail/lconrad
[lconrad@tuba lilypond]$ 

I realize I've had errors building the documentation for a while now.
Does this mean I have the wrong version of info or something?

-- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097  fax: (801) 365-6574 
233 Broadway, Cambridge, MA 02139

___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel

build problem with current cvs

2002-07-13 Thread Han-Wen


[EMAIL PROTECTED] writes:
> I just upped CVS, and when I run "make", I get:

run make clean


-- 

Han-Wen Nienhuys   |   [EMAIL PROTECTED]   |   http://www.cs.uu.nl/~hanwen 

___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel

build problem with current cvs

2002-07-13 Thread Laura Conrad


I just upped CVS, and when I run "make", I get:

rm -f ./out/align-interface.dep; DEPENDENCIES_OUTPUT="./out/align-interface.dep 
./out/align-interface.o" c++ -c  -DHAVE_CONFIG_H  -DSTRING_UTILS_INLINED -Iinclude 
-I./out -I.././lib/include -I../lib/./out -I.././flower/include -I../flower/./out 
-I../flower/include -O2 -finline-functions -g   -I/usr/include -O2 
-finline-functions -g   -I/usr/include -Wall  -W -Wmissing-prototypes -Wconversion  -o 
out/align-interface.o align-interface.cc
make[1]: *** No rule to make target `include/debug.hh', needed by 
`out/all-font-metrics.o'.  Stop.
make[1]: Leaving directory `/home/lconrad/src/lilypond/cvs/lilypond/lily'
make: *** [all] Error 2
[lconrad@tuba lilypond]$ 

-- 
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097  fax: (801) 365-6574 
233 Broadway, Cambridge, MA 02139


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel

63 matches

Mail list logo