Re: Building LilyPond with GUB on a 64bit machine with 32bit OS

[Jan Nieuwenhuizen]

Op woensdag 17-12-2008 om 18:58 uur [tijdzone +0100], schreef Reinhold
Kainhofer:

> > it would be nice to have documented why we [think we] need this.
> 
> Actually, this IS what is breaking the configure check. By setting 
> LD_LIBRARY_PATH to the tools dir, you are telling the linker to use the 
> libraries from there (which are linked to glib 2.3). This fails in the guile 
> check, since some libraries are used from the system and some from the tools 
> dir.
> 
> If I uncomment all three 
>   LD_LIBRARY_PATH': '%(tools_prefix)s/lib'
>             + misc.append_path (os.environ.get ('LD_LIBRARY_PATH', '')),
> settings in the gub/*.py files, then the configure check works fine and 
> lilypond 
> builds also fine.

Hmm.  It's good if we can junk it, but I wonder why we had this in
the first place.  Han-Wen?

I'm testing this now.  I still don't understand how LD_LIBRARY_PATH has
an effect on the linker, and why it works for me and not for you...

> It then only fails on the TODO file:
> 
> file from VC not distributed: lilypond-2.11.66/lily/TODO
> rm -rf /tmp/tmpMdXowy
> Traceback (most recent call last):
>   File "test-lily/dist-check.py", line 136, in <module>
>     main ()
>   File "test-lily/dist-check.py", line 131, in main
>     check_files (tarball, repo)
>   File "test-lily/dist-check.py", line 116, in check_files
>     raise Exception ('dist error found')
> Exception: dist error found

That must be a bug in lilypond HEAD. :-)

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music
typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org