Trubles compiling lxqt on RPi4

Mark Millard marklmi at
Thu May 13 04:16:36 UTC 2021

On 2021-May-12, at 20:48, bob prohaska <fbsd at> wrote:

> On Wed, May 12, 2021 at 05:17:37PM -0700, Mark Millard via freebsd-ports wrote:
>> bob prohaska fbsd at wrote on
>> Wed May 12 21:10:02 UTC 2021 :
>>> Attempts to compile x11/x11-wm/lxqt on a Pi4 running -current
>>> get stuck with:
>>> ===>  Building for json-glib-1.6.2_1
> [....]
>>> FAILED: json-glib/
>>> Is there a workaround? Ports were up-to-date as of today, May 12, 2021.
>> You are not very explicit about the FreeBSD context and
>> such, beyond RPi4 (so aarm64/aarch64).
> Moving to /usr/ports/json-glib and using 
> reports several instances of 
> error: unknown argument: '-fno-color-diagnostics'
> Running make clean and restarting makes no difference. There don't seem to be
> any user options for making json-glib,

The build log at:

is the one that just python38 and it reports:

---Begin OPTIONS List---
===> The following configuration options are available for json-glib-1.6.2_1:
     DOCS=on: Build and/or install documentation
     GIR=on: Build introspection data
===> Use 'make config' to modify these settings
---End OPTIONS List---

as the options that were used for the build. So
there are 2 options, one of which is appearently
tied to the code's operation (introspection data).

> but I wonder if it might be inherting
> an incompatible option from something else.

That build log also has lines showing the likes of:

[ 21% 16/69] cc -Ijson-glib/ . . . -fno-color-diagnostics . . .

The compiler is reported in the log to be:

C compiler for the host machine: cc (clang 11.0.1 "FreeBSD clang version 11.0.1 (git at llvmorg-11.0.1-0-g43ff75f2c3fe)")
C linker for the host machine: cc ld.lld 11.0.1

That "llvmorg-11.0.1-0-g43ff75f2c3fe" matches what is in my
historical main [so: 14] environments.

So system-clang apparently allows the option.

You did not show any example command that got the complaint
about  -fno-color-diagnostics so I can ont even be sure it
was a cc command that had the option.

Still, your report suggests that the "cc" in your environment
for this build does not reach the normal system-clang.

Do you have /etc/make.conf or /etc/src.conf or the like that
might be interfering? Something else?

What does "cc -v" show in your context?

is incoherent: the first says not to do the last.

Mark Millard
marklmi at
( went
away in early 2018-Mar)

More information about the freebsd-ports mailing list