On Mon, 2021-05-10 07:18:02 +1000, matthew green <mrg%eterna.com.au@localhost> wrote:
> > Oh and now it's verified: I don't export HAVE_GCC=3D10 anywhere.
> > (Though the initial GCC was a "gcc (Debian 10.2.1-6) 10.2.1 20210110",
> > which is now the system GCC and not the more recent one from the
> > "gcc-snapshot" DEB (which'd identify as "gcc (Debian 20210320-1)
> > 11.0.1 20210320 (experimental) [master revision
> > 3279a9a5a9a:6526c452d22:5f256a70a05fcfc5a1caf56678ceb12b4f87f781]").)
>
> as you previously said, the host compiler _should not_ affect
> what is being built for the target sun2.
>
> just to confirm that this isn't happening, running this will
> tell you what target GCC is being used:
>
> /var/lib/laminar/run/netbsd-sun2-m68000/nn/obj/tooldir.Linux-5.9.0-2-amd64-x86_64/bin/m68010--netbsdelf-gcc -v
>
> (at least, i think that is your path.)
First run done (manually, in a Debian "buster" Docker container),
succeeded for "tools" and "release", with this GCC:
(debian:buster)root@toolchaintest-host:~/xxx/NetBSD-src# ../obj/tooldir.Linux-5.9.0-2-amd64-x86_64/bin/m68010--netbsdelf-gcc -v
Using built-in specs.
COLLECT_GCC=../obj/tooldir.Linux-5.9.0-2-amd64-x86_64/bin/m68010--netbsdelf-gcc
COLLECT_LTO_WRAPPER=/root/xxx/obj/tooldir.Linux-5.9.0-2-amd64-x86_64/bin/../libexec/gcc/m68010--netbsdelf/9.3.0/lto-wrapper
Target: m68010--netbsdelf
Configured with: /root/xxx/NetBSD-src/tools/gcc/../../external/gpl3/gcc.old/dist/configure --target=m68010--netbsdelf --enable-long-long --enable-threads --with-bugurl=http://www.NetBSD.org/support/send-pr.html --with-pkgversion='NetBSD nb1 20200907' --with-system-zlib --without-isl --enable-__cxa_atexit --enable-libstdcxx-time=rt --enable-libstdcxx-threads --with-diagnostics-color=auto-if-env --with-default-libstdcxx-abi=new --with-sysroot=/root/xxx/NetBSD-src/../obj/destdir.sun2 --with-mpc=/root/xxx/NetBSD-src/../obj/tooldir.Linux-5.9.0-2-amd64-x86_64 --with-mpfr=/root/xxx/NetBSD-src/../obj/tooldir.Linux-5.9.0-2-amd64-x86_64 --with-gmp=/root/xxx/NetBSD-src/../obj/tooldir.Linux-5.9.0-2-amd64-x86_64 --disable-nls --disable-multilib --program-transform-name='s,^,m68010--netbsdelf-,' --enable-languages='c c++ objc' --prefix=/root/xxx/NetBSD-src/../obj/tooldir.Linux-5.9.0-2-amd64-x86_64 --disable-shared
Thread model: posix
gcc version 9.3.0 (NetBSD nb1 20200907)
Just FTR, this is how I did it:
docker run --env SSH_AUTH_SOCK=/ssh-agent \
--net=host \
--volume "${SSH_AUTH_SOCK}:/ssh-agent" \
--volume "/tmp:/tmp-host" \
--volume "/tmp/.X11-unix:/tmp/.X11-unix" \
--volume "/tmp/.X11-unix:/tmp/.X11-unix" \
--volume "${HOME}/.Xauthority:/root/.Xauthority" \
--volume "${HOME}:/home-host" \
--volume /var/cache/git:/varcachegit \
--cap-add=SYS_PTRACE \
--security-opt=apparmor:unconfined \
--security-opt seccomp=unconfined \
-h "`hostname`" \
--interactive \
--tty \
debian:buster
rm /etc/apt/apt.conf.d/docker-*
apt-get update
apt-get install gcc g++ make zlib1g-dev
apt-get install git less vim
mkdir xxx
cd xxx
git clone --shared /varcachegit/NetBSD-src
cd NetBSD-src
mkdir ../obj
./build.sh -U -O "`pwd`/../obj" -m sun2 -a m68000 tools
./build.sh -U -u -O "`pwd`/../obj" -m sun2 -a m68000 release
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.
MfG, JBG
--
Attachment:
signature.asc
Description: PGP signature