again trouble with scripts

classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

again trouble with scripts

Federico Bruni-2
Tonight I had the bad idea of rebuilding my git working copy from
scratch (because of some mess I did).
I've come across the old problem I used to have last year:
http://lilypond-translations.3384276.n2.nabble.com/problems-with-check-translation-td5570712.html 


fede@fede-laptop:~/lilypond-git/build/Documentation$ make ISOLANG=it
check-translation
ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py  
fede@fede-laptop:~/lilypond-git/build/Documentation$ make ISOLANG=it
update-translation
ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py --update


I tried all the solutions suggested in that thread (that is, I run any
possible make command you can think of) but it didn't help.
This is black magic for me: any idea?

Thanks,
Federico



Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Francisco Vila
2011/7/18 Federico Bruni <[hidden email]>:
> Tonight I had the bad idea of rebuilding my git working copy from
> scratch (because of some mess I did).
> I've come across the old problem I used to have last year:
> http://lilypond-translations.3384276.n2.nabble.com/problems-with-check-translation-td5570712.html

I see many problems and solutions here. Could you specify a bit?

> fede@fede-laptop:~/lilypond-git/build/Documentation$ make ISOLANG=it
> check-translation
> ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py
> fede@fede-laptop:~/lilypond-git/build/Documentation$ make ISOLANG=it
> update-translation
> ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py --update

What's the error here?

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Federico Bruni-2
2011/7/19 Francisco Vila <paconet.org@gmail.com>
2011/7/18 Federico Bruni <[hidden email]>:
> Tonight I had the bad idea of rebuilding my git working copy from
> scratch (because of some mess I did).
> I've come across the old problem I used to have last year:
> http://lilypond-translations.3384276.n2.nabble.com/problems-with-check-translation-td5570712.html

I see many problems and solutions here. Could you specify a bit?


Sorry, you are right.
The specific problem is that no output is printed, see my email of 4 october in that thread.
But it seems - reading the messages in October - that the problem was "self-resolved" after some time.

 
> fede@fede-laptop:~/lilypond-git/build/Documentation$ make ISOLANG=it
> check-translation
> ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py
> fede@fede-laptop:~/lilypond-git/build/Documentation$ make ISOLANG=it
> update-translation
> ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py --update

What's the error here?



There's no output, but I'm sure that it should show the files to be updated (first command) or the diff (second command).

Thanks for your help,
Federico
Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Federico Bruni-2
I've tried again on a different computer and I get the same error.
I can fix the warning about "gettext domain not found" but I don't know how to make the scripts work.

Of course I've already run make.
And I'm working inside build/

IIUC if I've already run 'make' 'make -C scripts && make -C python' will be useless.
What else should I try?


fede@debian:~/lilypond-git/build/Documentation$ make ISOLANG=it check-translation
ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py 
langdefs.py: warning: lilypond-doc gettext domain not found.
fede@debian:~/lilypond-git/build/Documentation$
fede@debian:~/lilypond-git/build/Documentation$ make ISOLANG=it update-translation
ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py --update 
langdefs.py: warning: lilypond-doc gettext domain not found.
fede@debian:~/lilypond-git/build/Documentation$
fede@debian:~/lilypond-git/build/Documentation$ make -C po out=www messages
ls: impossibile accedere a ../../Documentation/snippets/*.ly: No such file or directory
make: Entering directory `/home/fede/lilypond-git/build/Documentation/po'
/home/fede/lilypond-git/./Documentation/po/GNUmakefile:28: warning: overriding commands for target `po-update'
/home/fede/lilypond-git/stepmake/stepmake/podir-targets.make:14: warning: ignoring old commands for target `po-update'
mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*' > ./out-www/.gitignore
make: Leaving directory `/home/fede/lilypond-git/build/Documentation/po'
ls: impossibile accedere a ../../Documentation/snippets/*.ly: No such file or directory
make: Entering directory `/home/fede/lilypond-git/build/Documentation/po'
/home/fede/lilypond-git/./Documentation/po/GNUmakefile:28: warning: overriding commands for target `po-update'
/home/fede/lilypond-git/stepmake/stepmake/podir-targets.make:14: warning: ignoring old commands for target `po-update'
msgfmt -o out-www/cs.mo /home/fede/lilypond-git/Documentation/po/cs.po
msgfmt -o out-www/de.mo /home/fede/lilypond-git/Documentation/po/de.po
msgfmt -o out-www/es.mo /home/fede/lilypond-git/Documentation/po/es.po
msgfmt -o out-www/fr.mo /home/fede/lilypond-git/Documentation/po/fr.po
msgfmt -o out-www/hu.mo /home/fede/lilypond-git/Documentation/po/hu.po
msgfmt -o out-www/it.mo /home/fede/lilypond-git/Documentation/po/it.po
msgfmt -o out-www/ja.mo /home/fede/lilypond-git/Documentation/po/ja.po
msgfmt -o out-www/nl.mo /home/fede/lilypond-git/Documentation/po/nl.po
msgfmt -o out-www/zh.mo /home/fede/lilypond-git/Documentation/po/zh.po
for i in cs de es fr hu it ja nl zh; do \
      mkdir -p ./out-www/$i/LC_MESSAGES; \
      cp ./out-www/$i.mo ./out-www/$i/LC_MESSAGES/lilypond-doc.mo; \
    done
touch out-www/messages
make: Leaving directory `/home/fede/lilypond-git/build/Documentation/po'
fede@debian:~/lilypond-git/build/Documentation$
fede@debian:~/lilypond-git/build/Documentation$
fede@debian:~/lilypond-git/build/Documentation$
fede@debian:~/lilypond-git/build/Documentation$ make ISOLANG=it update-translation
ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py --update 
fede@debian:~/lilypond-git/build/Documentation$ make ISOLANG=it check-translation
ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py
Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Francisco Vila
2011/7/19 Federico Bruni <[hidden email]>:
> I've tried again on a different computer and I get the same error.
> I can fix the warning about "gettext domain not found" but I don't know how
> to make the scripts work.
>
> Of course I've already run make.
> And I'm working inside build/

I think make check-translation is intended to be run only from the
Documentation/ folder.

Try it and tell us.

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Francisco Vila
In reply to this post by Federico Bruni-2
2011/7/19 Federico Bruni <[hidden email]>:
> IIUC if I've already run 'make' 'make -C scripts && make -C python' will be
> useless.
> What else should I try?

Remember that <directory> in 'make -C <directory>' is a relative path
from your current directory.  python/ and scripts/ are descendants of
the tree top, so you should only run make -C python from there.  Sorry
for this q'n'd, potentially pointless note.

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Federico Bruni-2
In reply to this post by Francisco Vila
2011/7/19 Francisco Vila <paconet.org@gmail.com>
2011/7/19 Federico Bruni <[hidden email]>:
> I've tried again on a different computer and I get the same error.
> I can fix the warning about "gettext domain not found" but I don't know how
> to make the scripts work.
>
> Of course I've already run make.
> And I'm working inside build/

I think make check-translation is intended to be run only from the
Documentation/ folder.

Try it and tell us.


Look at the output I've posted: I did run it inside Documentation/

What I meant to say is: my top dir is build/ and not the git topdir, because I've built in build/ (as recommended in the docs).
Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Federico Bruni-2
In reply to this post by Francisco Vila
2011/7/19 Francisco Vila <paconet.org@gmail.com>
2011/7/19 Federico Bruni <[hidden email]>:
> IIUC if I've already run 'make' 'make -C scripts && make -C python' will be
> useless.
> What else should I try?

Remember that <directory> in 'make -C <directory>' is a relative path
from your current directory.  python/ and scripts/ are descendants of
the tree top, so you should only run make -C python from there.  Sorry
for this q'n'd, potentially pointless note.


Just tried and it doesn't help:


fede@debian:~/lilypond-git/build$ make -C python
make: Entering directory `/home/fede/lilypond-git/build/python'
make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C auxiliar all && true
make[1]: Entering directory `/home/fede/lilypond-git/build/python/auxiliar'
true
make[1]: Leaving directory `/home/fede/lilypond-git/build/python/auxiliar'
make: Leaving directory `/home/fede/lilypond-git/build/python'
fede@debian:~/lilypond-git/build$
fede@debian:~/lilypond-git/build$ make -C scripts
make: Entering directory `/home/fede/lilypond-git/build/scripts'
make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C auxiliar man &&  make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C build man && true
make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/auxiliar'
true
make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/auxiliar'
make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/build'
true
make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/build'
make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C auxiliar all &&  make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C build all && true
make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/auxiliar'
true
make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/auxiliar'
make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/build'
true
make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/build'
make: Leaving directory `/home/fede/lilypond-git/build/scripts'
fede@debian:~/lilypond-git/build$
fede@debian:~/lilypond-git/build$
fede@debian:~/lilypond-git/build$ cd Documentation/
fede@debian:~/lilypond-git/build/Documentation$ make ISOLANG=it check-translation
ISOLANG=it /usr/bin/python /home/fede/lilypond-git/scripts/auxiliar/check_translation.py 
fede@debian:~/lilypond-git/build/Documentation$
 
Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Francisco Vila
2011/7/19 Federico Bruni <[hidden email]>:

> 2011/7/19 Francisco Vila <[hidden email]>
>>
>> 2011/7/19 Federico Bruni <[hidden email]>:
>> > IIUC if I've already run 'make' 'make -C scripts && make -C python' will
>> > be
>> > useless.
>> > What else should I try?
>>
>> Remember that <directory> in 'make -C <directory>' is a relative path
>> from your current directory.  python/ and scripts/ are descendants of
>> the tree top, so you should only run make -C python from there.  Sorry
>> for this q'n'd, potentially pointless note.
>>
>
> Just tried and it doesn't help:
>
>
> fede@debian:~/lilypond-git/build$ make -C python
> make: Entering directory `/home/fede/lilypond-git/build/python'
> make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C auxiliar all &&
> true
> make[1]: Entering directory `/home/fede/lilypond-git/build/python/auxiliar'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/python/auxiliar'
> make: Leaving directory `/home/fede/lilypond-git/build/python'
> fede@debian:~/lilypond-git/build$
> fede@debian:~/lilypond-git/build$ make -C scripts
> make: Entering directory `/home/fede/lilypond-git/build/scripts'
> make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C auxiliar man
> &&  make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C build man
> && true
> make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/auxiliar'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/auxiliar'
> make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/build'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/build'
> make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C auxiliar all
> &&  make --no-builtin-rules PACKAGE=LILYPOND package=lilypond -C build all
> && true
> make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/auxiliar'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/auxiliar'
> make[1]: Entering directory `/home/fede/lilypond-git/build/scripts/build'
> true
> make[1]: Leaving directory `/home/fede/lilypond-git/build/scripts/build'
> make: Leaving directory `/home/fede/lilypond-git/build/scripts'
> fede@debian:~/lilypond-git/build$
> fede@debian:~/lilypond-git/build$
> fede@debian:~/lilypond-git/build$ cd Documentation/
> fede@debian:~/lilypond-git/build/Documentation$ make ISOLANG=it
> check-translation
> ISOLANG=it /usr/bin/python
> /home/fede/lilypond-git/scripts/auxiliar/check_translation.py
> fede@debian:~/lilypond-git/build/Documentation$

I have never tried the outside-tree build, but for me, your build/
directory is only a build directory for compiling lilypond into it,
not your source directory and of course it is NOT your source tree
top.  My experience ends here but I am willing to make my first
attempt of building into build/ just to see what happens.

What if (for once) you do

  ~/lilypond-git$ ./autogen.sh
  ~/lilypond-git$ cd Documentation/
  ~/lilypond-git/Documentation$ make ISOLANG=it check-translation

for me?


--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Federico Bruni-2
2011/7/19 Francisco Vila <paconet.org@gmail.com>

I have never tried the outside-tree build, but for me, your build/
directory is only a build directory for compiling lilypond into it,
not your source directory and of course it is NOT your source tree
top.  My experience ends here but I am willing to make my first
attempt of building into build/ just to see what happens.



But it's the recommended way in the docs (I think it was added recently).
In the CG I couldn't find any warning for translators, so maybe there should be a way to make it work.
 
What if (for once) you do

 ~/lilypond-git$ ./autogen.sh
 ~/lilypond-git$ cd Documentation/
 ~/lilypond-git/Documentation$ make ISOLANG=it check-translation

for me?


Yes, it works if I build in top dir.
Let me know your try with building in build/

BTW, there's a fatal object.
I'll fix it with a new patch (I got a revision of those files):


warning: it/texidocs/ancient-notation-template----modern-transcription-of-gregorian-music.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/ancient-notation-template----modern-transcription-of-mensural-music.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/anglican-psalm-template.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/hymn-template.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/jazz-combo-template.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/orchestra,-choir-and-piano-template.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/piano-template-simple.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/piano-template-with-centered-dynamics.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/piano-template-with-centered-lyrics.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/piano-template-with-melody-and-lyrics.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/satb-choir-template---four-staves.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/single-staff-template-with-notes,-lyrics,-and-chords.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/single-staff-template-with-notes-and-chords.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/single-staff-template-with-notes-and-lyrics.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/single-staff-template-with-only-notes.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/string-quartet-template-simple.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/string-quartet-template-with-separate-parts.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/vocal-ensemble-template-with-automatic-piano-reduction.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/vocal-ensemble-template-with-lyrics-aligned-below-and-above-the-staves.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/vocal-ensemble-template-with-verse-and-refrain.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42
warning: it/texidocs/vocal-ensemble-template.texidoc: fatal: bad object 4077120c18ac1dc490501b3d7d5886bc93e61a42



Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Francisco Vila
2011/7/19 Federico Bruni <[hidden email]>:

> 2011/7/19 Francisco Vila <[hidden email]>
>>
>> I have never tried the outside-tree build, but for me, your build/
>> directory is only a build directory for compiling lilypond into it,
>> not your source directory and of course it is NOT your source tree
>> top.  My experience ends here but I am willing to make my first
>> attempt of building into build/ just to see what happens.
>>
>
>
> But it's the recommended way in the docs (I think it was added recently).

From my understanding, building in build/ is recommended, not running
check-translation from there.

> Yes, it works if I build in top dir.

Do not confuse 'build in top dir' with 'running scripts from the top
dir'.  Scripts that do not build things do not qualify for 'building'.
 You can compile binary/docs in build but you _should_  run
manteinance scripts from top dir or from the appropriate directory in
the _original_ source tree.

> Let me know your try with building in build/

What you tried was running scripts not directly related to building,
so that was the problem.  Let me know if you need more help for doing
things that are not explicitly documented :-)

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com


Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Federico Bruni-2
Il giorno mar, 19/07/2011 alle 18.40 +0200, Francisco Vila ha scritto:

> 2011/7/19 Federico Bruni <[hidden email]>:
> > 2011/7/19 Francisco Vila <[hidden email]>
> >>
> >> I have never tried the outside-tree build, but for me, your build/
> >> directory is only a build directory for compiling lilypond into it,
> >> not your source directory and of course it is NOT your source tree
> >> top.  My experience ends here but I am willing to make my first
> >> attempt of building into build/ just to see what happens.
> >>
> >
> >
> > But it's the recommended way in the docs (I think it was added recently).
>
> >From my understanding, building in build/ is recommended, not running
> check-translation from there.
>
> > Yes, it works if I build in top dir.
>
> Do not confuse 'build in top dir' with 'running scripts from the top
> dir'.  Scripts that do not build things do not qualify for 'building'.
>  You can compile binary/docs in build but you _should_  run
> manteinance scripts from top dir or from the appropriate directory in
> the _original_ source tree.


Ok, I see what you mean.
So I can use build/ just for building.

And if I want to use the maintenance scripts on the top dir, I must run
these commands on the top dir:

./autogen.sh # I need the configure
cp GNUmakefile.in GNUmakefile
make -C scripts && make -C python # don't need to build everything

It works.

Thanks for your patience



Reply | Threaded
Open this post in threaded view
|

Re: again trouble with scripts

Francisco Vila
2011/7/19 Federico Bruni <[hidden email]>:
> ./autogen.sh # I need the configure
> cp GNUmakefile.in GNUmakefile

I think the configure process already takes care of copying this.

> make -C scripts && make -C python # don't need to build everything
>
> It works.

Great!

--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com