https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248230

Mark Millard <marklmi26-f...@yahoo.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |marklmi26-f...@yahoo.com

--- Comment #2 from Mark Millard <marklmi26-f...@yahoo.com> ---
> tests works fine on FreeBSD 11.4 with Clang 10 and 12.1 with Clang 8 (and 
> also on Linux).

(I assume system-clang/llvm was in use instead of devel/llvm* 's. This wording
presumes that the 11.4 and 12.1-STABLE system clang 10 based rxdock builds were
separate. If not, do the contrasting case implicit below.)

If you copy the rxdock installed materials from 11.4 to 12.1-STABLE, do you see
the
problem on 12.1-STABLE? This is different than building rxdock materials on
12.1-STABLE with the 12.1-STABLE's llvm10/clang10 toochain. This is sort of
like
upgrading FreeBSD after the rxdock software was installed, without rebuilding
the
rxdock software. (That is another way of doing the experiment.)

The alternatives would seem to be:

A) Still works on 12.1-STABLE, so that 12.1-STABLE's toolchain is involved for
   the behavioral change in the re-built rxdock.

vs.

B) Fails on 12.1-STABLE, so just other differences in the FreeBSD versions make
   the difference, not the toolchain used to do the build (rxdock held
   invariant).

So it is just a partial problem-isolation test but it might help limit what
else to explore.

Of course, the suggestion presumes that FreeBSD's backwards compatibility
support has been built and installed in the 12.1-STABLE system, so that
the 12.1-STABLE is supposed to execute 11.x material just fine.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
freebsd-toolchain@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-toolchain
To unsubscribe, send any mail to "freebsd-toolchain-unsubscr...@freebsd.org"

Reply via email to