[Bug 201623] /usr/ports/graphics/dri fails on powerpc
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Jan 13 00:23:42 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201623
--- Comment #8 from Mark Millard <markmi at dsl-only.net> ---
(In reply to Niclas Zeising from comment #7)
Some ports allow picking compilers/toolchains
that are used in building the port. Others
only work with a specific family. Yet others
with only specific vintages/versions.
What are the constraints on the graphics/mesa-dri
compiler/toolchain usage?
Can something like lang/gcc6 be used by
graphics/mesa-dri ? (Might also require
devel/binutils instead of the system
toolchain.)
If yes, then switching the port to use such a
lang/gcc* (and devel/binutils ) might avoid any
issues with the previously default compiler,
whatever it was. (Presumes someone then uses
a powerpc host to test the alternate compiler
and toolchain.)
If no, then can graphics/mesa-dri be modified
to allow alternative compilers/toolchains
from ports to be tried by those with an
appropriate context for targeting powerpc?
[My normal powerpc64 and powerpc context is
not a great test case because buildworld was
using the problematical clang that messes
up handling thrown C++ exceptions in the
libraries that clang builds. I report
problems that I find, which is why I do
the experiments.]
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the freebsd-ppc
mailing list