[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-sparc/44389: awk failure during m4 installation with pkgsrc
On 15/01/11 01:50, Izumi Tsutsui wrote:
> The following reply was made to PR port-sparc/44389; it has been noted by
> From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
> To: gnats-bugs%NetBSD.org@localhost
> Cc: martin%duskware.de@localhost, tsutsui%ceres.dti.ne.jp@localhost
> Subject: Re: port-sparc/44389: awk failure during m4 installation with pkgsrc
> Date: Sat, 15 Jan 2011 10:49:40 +0900
> > > > /usr/bin/awk: floating point exception 8
> > > > input record number 18792, file configure
> > > > source line number 1
> > > > *** Error code 2
> > >
> > > My bet would be a qemu bug.
> > Could you suggest how to isolate the problem,
> It just works on a real SS20.
> Isn't it enough to say it's a qemu bug?
I believe it is not.
The error I've reported is thrown by AWK called from deep abbys of
pkgsrc. AWK sits on the execution stack high above any hardware (even
emulated), so I can't really think of debugging emulator
without exact command AWK was executed, at least.
Is it possible to trace pkgsrc and find where AWK is called from
and find exact AWK command executed?
> ===> Overriding tools for m4-1.4.15
> ===> Extracting for m4-1.4.15
> ===> Patching for m4-1.4.15
> => Applying pkgsrc patches for m4-1.4.15
> ===> Creating toolchain wrappers for m4-1.4.15
> ===> Configuring for m4-1.4.15
> => Modifying GNU configure scripts to avoid --recheck
> => Replacing config-guess with pkgsrc versions
> => Replacing config-sub with pkgsrc versions
> => Replacing install-sh with pkgsrc version
> checking for a BSD-compatible install... /usr/bin/install -c -o root -g wheel
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... build-aux/install-sh -c -d
> checking for gawk... /usr/bin/awk
> checking whether make sets $(MAKE)... yes
> checking for sparc--netbsdelf-gcc... cc
> > find exact awk command
> > causing the error, so I can debug it or forward to QEMU developers with
> > details necessary to reproduce it?
> Probably you can mention what you did (including how to fetch pkgsrc)
> in a bug report to qemu?
I have forwarded the whole story to the QEMU team:
However, a reproducible test case is essential and I'm not surprised.
Mateusz Loskot, http://mateusz.loskot.net
Charter Member of OSGeo, http://osgeo.org
Member of ACCU, http://accu.org
Main Index |
Thread Index |