Re: CVS commit: src [llvm]

[Maxime Villard <max%m00nbsd.net@localhost>]

Le 12/11/2019 à 23:10, Joerg Sonnenberger a écrit :
> On Tue, Nov 12, 2019 at 04:31:00PM +0100, Maxime Villard wrote:
> > Le 12/11/2019 à 16:06, Maxime Villard a écrit :
> > > Le 12/11/2019 à 14:37, Joerg Sonnenberger a écrit :
> > > > On Tue, Nov 12, 2019 at 11:39:09AM +0100, Maxime Villard wrote:
> > > > > Le 11/11/2019 à 23:45, Joerg Sonnenberger a écrit :
> > > > > > Module Name:    src
> > > > > > Committed By:    joerg
> > > > > > Date:        Mon Nov 11 22:45:32 UTC 2019
> > > > > >
> > > > > > [...]
> > > > > > Log Message:
> > > > > > Update LLVM to 10.0.0git (01f3a59fb3e2542fce74c768718f594d0debd0da)
> > > > >
> > > > > Since this change, I cannot cross-compile GENERIC amd64 from Linux:
> > > >
> > > > What non-standard settings are you using? amd64 is certainly on my list
> > > > of architectures to test.
> > >
> > > No particular settings. Just the latest src/ compiled unchanged with
> > >
> > > ./build.sh -j4 -U -O ../obj -V MKLLVM=yes -V MKGCC=no -V HAVE_LLVM=yes -m amd64 kernel=GENERIC
> >
> > I'm also having the same issue on a NetBSD-amd64 host, with again an unchanged
> > src/ and the same command
>
> Is that a clean build? I certainly do full release builds for all LLVM
> architectures and I don't get this.

Yes, a clean build.

I've done two again just now, on different physical machines. One has NetBSD,
the other has Linux.

I deleted the src and obj directories and started from scratch using github,
with the following commands exactly as-is on both hosts from an empty folder:

	git clone https://github.com/NetBSD/src.git
	cd src
	./build.sh -j 4 -U -O ../obj -V MKGCC=no -V MKLLVM=yes -V HAVE_LLVM=yes -m amd64 tools
	./build.sh -j 4 -U -O ../obj -V MKGCC=no -V MKLLVM=yes -V HAVE_LLVM=yes -m amd64 kernel=GENERIC

Both hosts fail the same way.

My two tests from yesterday were on the same physical machine but with both
NetBSD/Linux, using the same commands as above except that it was anoncvs
instead of github, and both hosts failed the same way.

Am I the only one seeing this? It's hard to blame the configuration when the
failure is seen on several hardware and several OSes.