NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-sun2/56158: sun2 m68000: super-block backups (for fsck -b #) at: 32,nbmakefs: Writing inode 152 (work/./bin/cat), bytes 528384 + 4096: No space left on device
The following reply was made to PR port-sun2/56158; it has been noted by GNATS.
From: Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost>
To: matthew green <mrg%eterna.com.au@localhost>
Cc: gnats-bugs%netbsd.org@localhost, Chris Pinnock <cjep%netbsd.org@localhost>,
gnats-admin%netbsd.org@localhost, netbsd-bugs%netbsd.org@localhost,
Chris Pinnock <chris_pinnock%mac.com@localhost>
Subject: Re: port-sun2/56158: sun2 m68000: super-block backups (for fsck -b
#) at: 32,nbmakefs: Writing inode 152 (work/./bin/cat), bytes 528384 + 4096:
No space left on device
Date: Tue, 11 May 2021 07:12:50 +0200
--q7lgkuvfqqythwdi
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi!
On Mon, 2021-05-10 16:00:13 +0200, Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost> wr=
ote:
> On Mon, 2021-05-10 09:08:47 +0200, Jan-Benedict Glaw <jbglaw%lug-owl.de@localhost> =
wrote:
> > Will now start a "bullseye"-based run. Just as a note of amazement,
> > I'd like to notice how self-contained the NetBSD build is and how
> > minimal (gcc, g++, zlib1g-dev and possibly make) the external
> > dependencies are.
>=20
> Testing in Docker so far:
>=20
> Debian stable "Buster": successful build for tools+release
> Debian testing "Bullseye": successful build for tools+release
> Debian unstable "Sid": Next to go!
The Debian "unstable" build also succeeded. So either something that's
installed or in the environment breaks the build.
My next guess is that, somehow, my compiler choice could be the
culprit: As these are CI builds, I implemented a way to choose a
compiler suite:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
# vim:filetype=3Dbash:
# This file is to be source'd.
#
# Input:
# $COMPILER_SUITE
# "gcc-system", "gcc-snapshot", "clang-12"
# Sets/Modifies
# $CC
# $CXX
# $CPP
# $LD
# $LD_LIBRARY_PATH
# $PATH
: "${COMPILER_SUITE:=3Dgcc-snapshot}"
case "${COMPILER_SUITE}" in
gcc-system)
export CC=3Dgcc
export CXX=3Dg++
export CPP=3Dcpp
export LD=3Dgcc
;;
gcc-snapshot)
export CC=3D/usr/lib/gcc-snapshot/bin/gcc
export CXX=3D/usr/lib/gcc-snapshot/bin/g++
export CPP=3D/usr/lib/gcc-snapshot/bin/cpp
export LD=3D/usr/lib/gcc-snapshot/bin/gcc
export LD_LIBRARY_PATH=3D/usr/lib/gcc-snapshot/lib:$LD_LIBR=
ARY_PATH
export PATH=3D/usr/lib/gcc-snapshot/bin:$PATH
hash -r
;;
clang-12)
export CC=3D/usr/bin/clang-12
export CXX=3D/usr/bin/clang++-12
export CPP=3D/usr/bin/clang-cpp-12
export LD=3D/usr/bin/clang-12
;;
*)
echo "Unknown compiler suite ${COMPILER_SUITE}, aborting" >=
&2
exit 1
;;
esac
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D
So maybe one of $CC, $CXX, $CPP or $LD interfered? Will check that
next...
Thanks,
Jan-Benedict
--=20
--q7lgkuvfqqythwdi
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
iF0EABECAB0WIQQlDTvPcScNjKREqWEdvV51g5nhuwUCYJoSUAAKCRAdvV51g5nh
u2N2AJ0QVzBR3Y9+11qfjth9qDPwpn6PygCfeGsxpPkhhiXg6d+13YSGeRPeo4s=
=+/Hu
-----END PGP SIGNATURE-----
--q7lgkuvfqqythwdi--
Home |
Main Index |
Thread Index |
Old Index