lilypond-devel
[Top][All Lists]
Advanced

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

Re: GUB3 at the lilypond-installer stage


From: Patrick McCarty
Subject: Re: GUB3 at the lilypond-installer stage
Date: Sun, 26 Apr 2009 22:25:06 -0700
User-agent: Mutt/1.5.18 (2008-05-17)

Hi Jan,

On Thu, Apr 23, 2009 at 11:18:25AM +0200, Jan Nieuwenhuizen wrote:
> Op woensdag 22-04-2009 om 21:07 uur [tijdzone -0700], schreef Patrick
> McCarty:
> 
> > Your latest fixes on master work for me.
> > 
> > I can now build all of the installers except for darwin-*.  Attached
> > is the log for darwin-x86.
> 
> Yes, this is a quite similar thing.  While it's nice that it builds
> for you, I would like to get rid of the other workaround rather than
> add yet another one.  Can you help to find out why librestrict kicks
> in?
> 
> * add an " echo LD_PRELOAD=$LD_PRELOAD" statement in gub/installer.py
>   (just after the #FIXME: ask TarBall or so)
> * double check LD_PRELOAD is unset in your shell/when invoking gub
> * ??
> 
> Also, doing LD_PRELOAD= tar ... would be a nicer workaround than
> the extra cd ... && 

Here is the output after double-checking that LD_PRELOAD was not set
in my shell:

  invoking # FIXME: ask TarBall where source lives
  invoking echo LD_PRELOAD=$LD_PRELOAD
  LD_PRELOAD=/home/pnorcks/git/gub/target/tools/root/usr/lib/librestrict.so
  invoking tar -C /home/pnorcks/git/gub/target/darwin-ppc/installer -zxf 
/home/pnorcks/git/gub/downloads/osx-lilypad/osx-lilypad-ppc-0.2.tar.gz
  /home/pnorcks/git/gub/target/tools/root/usr/bin/tar: tried to open () file 
/home/pnorcks/git/gub/downloads/osx-lilypad/osx-lilypad-ppc-0.2.tar.gz
  allowed:
    /home/pnorcks/git/gub/target
    /tmp
    /dev/null
  tar: Child died with signal 6
  tar: Error exit delayed from previous errors
  Command barfed: tar -C /home/pnorcks/git/gub/target/darwin-ppc/installer -zxf 
/home/pnorcks/git/gub/downloads/osx-lilypad/osx-lilypad-ppc-0.2.tar.gz


I tried adding more "echo" statements in various places in the GUB
source code to see if LD_PRELOAD was set, but this didn't seem very
helpful, and I didn't really know where to put them.

Could this be an issue with my system glibc?  I have glibc 2.9
installed.


Thanks,
Patrick




reply via email to

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