Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 06 Apr 2020 04:36:45 +0000
From:      bugzilla-noreply@freebsd.org
To:        powerpc@FreeBSD.org
Subject:   [Bug 245367] net-p2p/qbittorrent : Fails to build on FreeBSD 12.1-RELEASE-p1 powerpc 32 bit: error: 'constexpr' constructor does not have empty bod
Message-ID:  <bug-245367-25139-aO5t9iFMpI@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-245367-25139@https.bugs.freebsd.org/bugzilla/>
References:  <bug-245367-25139@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D245367

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

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

--- Comment #5 from Mark Millard <marklmi26-fbsd@yahoo.com> ---
(In reply to Yuri Victorovich from comment #4)

Just a note mostly about clang vs. powerpc64 and 32-bit
powerpc . . .

Head (13) is using llvm/clang and 4.2.1 gcc and related
materials have been removed from there. But using llvm
involves powerpc64 ABI changes (incompatible) and use
of llvm 10 materials (in order for clang and such to
fully work). Even now there is a pending ABI fix for
32-bit powerpc from llvm having a change in what it
does that no longer matches (modern) gcc when targeting
FreeBSD:

https://bugs.llvm.org//show_bug.cgi?id=3D40736

The powerpc64 and 32-bit powerpc ABIs for stable/12 and
stable/11 (and related releases) can not be changed at
this point. So it will be some time before all supported
FreeBSD versions have dropped 4.2.1 related materials
as the system compiler/toolchain (the default toolchain,
for building ports on stable/12 and stable/11).

Unfortuantely, devel/llvm* ports have the same sort of
problems for powerpc64 and 32-bit powerpc as the
historical ones that blocked llvm's general use in such
contexts: even llvm10, when not configured to use the
updated ABI(s) that head is based on, has such issues
if I understand right.

(The above is an overall summary only.)

As for GCC . . .

Modern GCC's licensing limits where/how it is used in
FreeBSD contexts, even if there were no technical
problems for powerpc64 or 32-bit powerpc.

--=20
You are receiving this mail because:
You are on the CC list for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245367-25139-aO5t9iFMpI>