lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GUB


From: Graham Percival
Subject: Re: GUB
Date: Sun, 9 Oct 2011 14:42:12 +0100
User-agent: Mutt/1.5.20 (2009-06-14)

On Sun, Oct 09, 2011 at 12:32:52PM +0100, Phil Holmes wrote:
> ----- Original Message ----- From: "Graham Percival"
> <address@hidden>
> 
> >Nothing in guile.py looks particularly helpful to me, though.  Oh,
> >what exact package were you building?
> 
> This is the line that throws the error.  All one line - no linebreaks:
>
> /bin/bash ../libtool --tag=CC   --mode=link gcc  -O2

Back up.  We need more context.  You type
 bin/gub --platform=whatever "blah blah" flargle

and then you immediately see that error?  I don't think so; it
probably says something vaguely like

...
...
Building mingw::guile
Patching... done
Configure... done
Build... fail

---- tail of target/mingw/lib/build/whatever/guile.log
/bin/bash ../libtool --tag=CC   --mode=link gcc  -O2
-I/media/IntelSSD/lilypond/git-gub/gub/target/tools/root/usr/include
-L/media/IntelSSD/lilypond/git-gub/gub/target/tools/root/usr/lib
-Wl,-rpath -Wl,\$ORIGIN/../lib -Wl,-rpath
-Wl,/media/IntelSSD/lilypond/git-gub/gub/target/tools/root/usr/lib
-o gen-scmconfig gen-scmconfig.o  -lgmp -lcrypt -lm -lltdl
------ for more information, see target/mingw/cross-flargle/log/guile.log
build failed.  more info in log/gub.log


If you don't have this visible on your screen, then start by
looking at log/gub.log, which should have basically a copy of this
stuff, and it should also point you at a more detailed log file
somewhere inside target/

Cheers,
- Graham



reply via email to

[Prev in Thread] Current Thread [Next in Thread]