iOn zo, 2009-02-15 at 19:13 -0800, Patrick McCarty wrote:
Hi Patrick,
> Those files exist, and libintl.la looks correct. It is not executable
> (755) like all of the other .la files I see, but this does not seem to
> make a difference; compilation still fails.
Ok. I figure that libtool reads from /usr first, or possibly another
library is missing in your gub build root [or a combination of that].
> > /bin/sh -x ../libtool ....
>
> I cannot figure out how to do this. Is there an easy way to do this
> with GUB?
Edit gub/specs/guile.py:Guile__mingw
remove the prepending X
def Xmakeflags (self):
# hack for (only) running libtool under dash-librestrict.
return (Guile.makeflags (self)
+ ''' 'LIBTOOL=%(tools_prefix)s/bin/dash
$(top_builddir)/libtool' ''')
and change to
''' 'LIBTOOL=/bin/bash -x $(top_builddir)/libtool' '''
You'll have to run without LIBRESTRICT=open:stat
> > LIBRESTRICT=open:stat bin/gub mingw::guile # or mingw::lilypond
>
> Starting fresh, this halts at tools::tar. Attached are relevant
> sections of build.log and config.log.
Ah, my restrict-stat.c hack broke your stat function. Ouch. I had
the impression that Han-Wen also ran 32 bits and it worked there.
Otherwise I hope he can give some insight/fixes :-) Han-Wen?
Jan.
--
Jan Nieuwenhuizen <jann...@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
