I haven't paid much attention to the fltk package since Rex is the primary maintainer but I just attempted to build fldigi and ran into the following issue:
checking for fltk-config... /usr/bin/fltk-config
/usr/bin/fltk-config: line 3: exec: fltk-config-unknown: not found
configure: error: /usr/bin/fltk-config failed
From a local rebuild attempt of fltk I see:
+ mv /builddir/build/BUILDROOT/fltk-1.3.8-3.fc38.x86_64/usr/bin/fltk-config /builddir/build/BUILDROOT/fltk-1.3.8-3.fc38.x86_64/usr/bin/fltk-config-unknown
+ install -p -m755 -D /builddir/build/SOURCES/fltk-config.sh /builddir/build/BUILDROOT/fltk-1.3.8-3.fc38.x86_64/usr/bin/fltk-config
Which seems strange until I took a loot at the FLTK specfile:
# we only apply this hack to multilib arch's
%ifarch x86_64 %{ix86} ppc64 ppc s390x s390 sparc64 sparc
%global arch %(uname -i 2>/dev/null || echo undefined)
mv $RPM_BUILD_ROOT%{_bindir}/fltk-config \
$RPM_BUILD_ROOT%{_bindir}/fltk-config-%{arch}
install -p -m755 -D %{SOURCE1} $RPM_BUILD_ROOT%{_bindir}/fltk-config
%endif
Obviously this has been in place for a VERY long time but the only use case I can think of is to have fltk-devel installed from two different arches, i686 and x86_64 for instance.
Could this have anything to do with the systemd-nspawn change? Could it have caused `uname -i` to no longer resolve correctly?
Does this really need to be supported at this point?
Thanks,
Richard