On Sat, Nov 05, 2011 at 10:29:05PM -0600, Colin Campbell wrote: > This evening, I d/l a copy of the gub source, ran bin/gupdate > --replace gub/specs/curl.py which pulled curl up to version 7.22 so
wow, I had no clue about this bin/gupdate --replace program! > I got crazy and issued bin/gub lilypond-installer. Regrettably, > after a long session of building things, but it built curl, right? If so, then congratulations: you just fixed a Critical issue. Send patch in the mail for direct pushing to GUB. > it choked on python: > Command barfed: cd /home/colin/gub/target/tools/build/python-2.4.5 > && make BLDLIBRARY='-Wl,-rpath -Wl,\$$ORIGIN/../lib -Wl,-rpath > -Wl,/home/colin/gub/target/tools/root/usr/lib -L. > -lpython$(VERSION)' > DESTDIR=/home/colin/gub/target/tools/install/python-2.4.5-root > install > > Tail of target/tools/log/python.log >>>>>>>> > python$EXE ../../Tools/scripts/h2py.py -i '(u_long)' > /usr/include/netinet/in.h > python: error while loading shared libraries: > libpython2.4.so.1.0: cannot open shared object file: No such file or > directory Hmm, no clue at the moment. But once I get the fix to build curl, I'll of course try this out on my own machine, which will hopefully fail in the same way so I can poke around easily. > Interestingly, near the beginning of the console output was this: > > >cd: 1: can't cd to /home/colin/gub/downloads/lilypond/git > >read_pipe failed: cd /home/colin/gub/downloads/lilypond/git && git all totally normal warnings. Fixable with 1 or 2 lines of python. https://github.com/janneke/gub/issues/4 > >Checking for mpost ... /usr/bin/mpost > >cd: 1: can't cd to /home/colin/gub/downloads/lilypond/git > >read_pipe failed: cd /home/colin/gub/downloads/lilypond/git && git > >show git.sv.gnu.org/lilypond.git/master:VERSION hmm, I wasn't expecting to see that warning crop up here as well. - Graham _______________________________________________ bug-lilypond mailing list [email protected] https://lists.gnu.org/mailman/listinfo/bug-lilypond
