On 11-12-31 10:52 AM, Carl Sorensen wrote:
Colin Campbell<cpkc<at> shaw.ca> writes:
For additional data points: I've built an Ubuntu 10.04 VM and used GUB
to build 2.15.24, which seems to work correctly, in that it produced an
installer which in turn gave me a copy of lilypond that can compile .ly
and which reports itself as version 2.15.24 in response to lilypond -v.
<snip>
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
make: ***
Colin,
Like you, I have problems with not finding a shared object file. I haven't yet
worked out an approach to resolve this.
I'm currently thinking of trying Ubuntu 10.04 (non-lilydev), as you have had
success with it.
Did you do a multi-platform build with 10.04, or just a single-platform build?
Thanks,
Carl
I'm still learning how to control GUB, Carl, so the successful build on
10.04 was simply bin/gub lilypond-installer and it produced a single .sh
in /uploads.
FWIW, the failing versions all have linux >= 3.0 gcc >= 4.6 and the
successful one was linux 2.6.32 and gcc 4.4.3. Python was 2.6 on one
and 2.7.2 on the others, but I'm thinking that the linux and python
aren't significant. The successful build had libc 2.11.1, the 11.10 had
2.13.20, and the Fedora has 2.14.90 of glibc. Given the non-finding of
objects in the same directory, it seems that the change from (g)libc
2.11 may be part or all of the problem. The wider issue may be that GUB
is seeing too much of the host system, too soon in the tool chain
building process.
Colin
--
I've learned that you shouldn't go through life with a catcher's mitt on both
hands.
You need to be able to throw something back.
-Maya Angelou, poet (1928- )
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
