Re: GUB3 at the lilypond-installer stage

[Jan Nieuwenhuizen]

Op woensdag 15-04-2009 om 00:06 uur [tijdzone -0700], schreef Patrick
McCarty:

Hi Patrick,

> >   ('tar -t -z -f 
> > "/home/pnorcks/git/gub/target/linux-x86/packages/libtool-runtime-2.2.6.a.linux-x86.gup"',)
> >   {}
> > invoking tar -C 
> > /home/pnorcks/git/gub/target/linux-x86/installer/lilypond-git.sv.gnu.org--lilypond.git-master
> >  -p -x -z -f 
> > /home/pnorcks/git/gub/target/linux-x86/packages/libtool-runtime-2.2.6.a.linux-x86.gup
> > /home/pnorcks/git/gub/target/tools/root/usr/bin/tar: tried to open () file 
> > /home/pnorcks/git/gub/.
> > allowed:
> >   /home/pnorcks/git/gub/target
> >   /tmp
> >   /dev/null
> > 
> > gzip: stdout: Broken pipe
> > Command barfed: tar -C 
> > /home/pnorcks/git/gub/target/linux-x86/installer/lilypond-git.sv.gnu.org--lilypond.git-master
> >  -p -x -z -f 
> > /home/pnorcks/git/gub/target/linux-x86/packages/libtool-runtime-2.2.6.a.linux-x86.gup
> 
> Does anyone have any ideas about this?

I haven't! ;-)

> The errors look like they involve librestrict.  Is this the case?

Yes, that's the case.  It looks like "your" tools/root/usr/bin/tar
tries to access the CWD.  I'm not sure why it would do that as

   * it should -C change directory to target/installer/...,
     I see no reason for . to exist, be writable, much less
     to be open()ed
   * "my" tools/root/usr/bin/tar does not seem to do this,
     so librestrict does not kick in.

We should try to figure out why "your" tar reads CWD, ie, git/gub/.

Jan.

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