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

Bug#175978: sabre_0.2.4b-15(mipsel/unstable): fails to build with sudo

On Thu, Jan 09, 2003 at 03:40:04AM -0800, Ryan Murray wrote:
> Package: sabre
> Version: 0.2.4b-15
> Severity: serious
> > make[3]: Entering directory `/build/buildd/sabre-0.2.4b/lib/tzp'
> > rm -f Makefile 
> > rm -f config.cache config.log stamp-h stamp-h[0-9]*
> > make[3]: Leaving directory `/build/buildd/sabre-0.2.4b/lib/tzp'
> > make[2]: Leaving directory `/build/buildd/sabre-0.2.4b/lib'
> > rm -f config.status
> > make[1]: Leaving directory `/build/buildd/sabre-0.2.4b'
> > find -name Makefile -o -name Makefile.in | xargs -r rm -f
> > dh_clean
> >  debian/rules build
> > dh_testdir
> > automake && aclocal && autoconf
> > ./configure --prefix=/usr --bindir=/usr/games --without-svgalib
> > ./configure: line 903: config.log: Permission denied
> > make: *** [stamp-configure] Error 1
> A full build log can be found at:
> http://buildd.debian.org/build.php?arch=mipsel&pkg=sabre&ver=0.2.4b-15
> sabre fails to build from source with the following commands:
> apt-get source sabre
> cd sabre-0.2.4b
> dpkg-buildpackage -uc -us -B -rsudo
> Running automake, aclocal, and autoconf in your clean target (with root
> privs), and then running them again in the build target (without root privs)
> causes the build to fail.  You need to clean up after everything generated
> in clean, or stop generating files in your clean target.

sabre's debian/rules does do this cleanup, though, so I'm confused. Look
further up in that build log:

make[1]: Entering directory `/build/buildd/sabre-0.2.4b'
cd . \
  && CONFIG_FILES=Makefile CONFIG_HEADERS= /bin/sh ./config.status
config.status: creating Makefile
make[1]: Leaving directory `/build/buildd/sabre-0.2.4b'
make[1]: Entering directory `/build/buildd/sabre-0.2.4b'
Making distclean in .
make[2]: Entering directory `/build/buildd/sabre-0.2.4b'
rm -f TAGS ID
rm -f Makefile
rm -f config.cache config.log stamp-h stamp-h[0-9]*
make[2]: Leaving directory `/build/buildd/sabre-0.2.4b'

There's a fair bit of log after that, but none of it should touch
config.log, and building with -rsudo works fine for me on i386. However,
the mipsen do seem to be consistently failing. Since it doesn't appear
to be configure, can you shed any light on what's creating config.log?


Colin Watson                                  [cjwatson@flatline.org.uk]

Reply to: