Re: GUB log always goes to linux-x86 ?

[Patrick McCarty]

On Mon, Aug 10, 2009 at 05:08:51PM -0700, Graham Percival wrote:
> GUB "make lilypond" fails with:
> 
> building package: freebsd-x86::guile
>  *** Stage: download (guile, freebsd-x86)
>  *** Stage: untar (guile, freebsd-x86)
>  *** Stage: patch (guile, freebsd-x86)
>  *** Stage: autoupdate (guile, freebsd-x86)
>  *** Stage: configure (guile, freebsd-x86)
>  *** Stage: compile (guile, freebsd-x86)
>  *** Stage: install (guile, freebsd-x86)
> Command barfed: cd
> /home/lilypond/gub/target/freebsd-x86/build/guile-1.8.7 && make
> LDFLAGS='-Wl,-rpath -Wl,\$$ORIGIN/../lib'
> DESTDIR=/home/lilypond/gub/target/freebsd-x86/install/guile-1.8.7-root
> install
> 
> Tail of target/linux-x86/log/build.log >>>>>>>>
>     make[1]: *** [install] Error 2
>     make[1]: Leaving directory
> `/home/lilypond/gub/target/freebsd-x86/build/guile-1.8.7/srfi'
>     make: *** [install-recursive] Error 1
>     Command barfed: cd
> /home/lilypond/gub/target/freebsd-x86/build/guile-1.8.7 && make
> LDFLAGS='-Wl,-rpath -Wl,\$$ORIGIN/../lib'
> DESTDIR=/home/lilypond/gub/target/freebsd-x86/install/guile-1.8.7-root
> install
> <<<<<<<< Tail of target/linux-x86/log/build.log
> 
> *** Failed target: freebsd-x86::guile

Since Jan recently condensed the console output for errors, you might
find the reason why this failed in target/linux-x86/log/build.log.

I suspect

  rm -rf target/freebsd-x86/packages/guile*

might solve your problem.

> No, that's not a typo -- the attempt to build guile on freebsd
> ends up writing to target-linux-x86/log (??)

Hasn't this always been the case?

When I run `make lilypond', the log file is linux-64/log/build.log
(since I am running a 64-bit OS).  But when I run
  
  bin/gub darwin-ppc::lilypond

the log file is darwin-ppc/log/build.log.


-Patrick