> Hi Mats,
>
>
> I looked around and I do have gettext 0.14.5 installed on this machine,
> and ports have nothing for msgfmt. If that is indeed part of gettext,
> then it should be doing the right thing (I would think). Still no
> farther ahead, though. What could I try?
>
> Blessings,
>
>
> Fr.
Hi Mats,
I looked around and I do have gettext 0.14.5 installed on this machine,
and ports have nothing for msgfmt. If that is indeed part of gettext,
then it should be doing the right thing (I would think). Still no farther
ahead, though. What could I try?
Blessings,
Fr. Gordon
It seems that the program msgfmt on your machine does something
else. The msgfmt to be used when compiling LilyPond is part of
Gnu gettext. Hopefully you can find some package for FreeBSD.
/Mats
Gordon Gilbert wrote:
Hey Mats again!
The gmake proceeded well until:
gmake[1]: Entering direct
Hey Mats again!
The gmake proceeded well until:
gmake[1]: Entering directory `/usr/ports/distfiles/lilypond-2.6.4/po'
/usr/ports/distfiles/lilypond-2.6.4/stepmake/stepmake/generic-targets.make:142:
out/dummy.dep: No such file or directory
please ignore innocent warning about dummy.dep
mkdir -p
Hey, Mats!
I think you may be onto something. The instructions has said to run
"gmake install", but I just now ran "gmake" alone, and it is whizzing
along at a great rate. Perhaps, after this is finished, all that stuff
will be in place, and I can run "gmake install" then to continue the
pr
Same thing here, buildscripts/out/help2man should have been
generated earlier by make. I hope you continued to use gmake
instead of make. Why not simply remove all the files in buildscripts/out/
(or run gmake -C buildscripts clean) and then run gmake again.
/Mats
Gordon Gilbert wrote:
Hi Mat
Hi Mats!
Your suggestions seemed to work somehow, although I had to use "gmake" not
simply "make". The make python clear didn't work, but the make python did
do something, after which I continued the gmake install (per instructions
in Digest, Vol 36, Issue 67) It then stopped, apparently at
The midi.so file should be produced when you run make, so the first
step for you is to figure out why that doesn't happen.
I would first try the following:
make -C python clear
make -C python
and look carefully for any warnings or errors printed out.
/Mats
Gordon Gilbert wrote:
Hi!
My insta
I wish I could help you. Have you tried asking this on the bug list?
Gordon Gilbert wrote:
Hi!
My install of 2.6.4 has stopped with the following output:
gmake[1]: Entering directory
`/usr/ports/distfiles/lilypond-2.6.4/python' /bin/sh
/usr/ports/distfiles/lilypond-2.6.4/stepmake/stepmake/..
Hi!
My install of 2.6.4 has stopped with the following output:
gmake[1]: Entering directory `/usr/ports/distfiles/lilypond-2.6.4/python'
/bin/sh
/usr/ports/distfiles/lilypond-2.6.4/stepmake/stepmake/../bin/install-sh -c
-d /usr/local/share/lilypond/2.6.4/python /bin/sh
/usr/ports/distfiles/l
10 matches
Mail list logo