Arch Linux User Repository

This error went away for me after adding

> options=(!lto)

How I missed that, I had enabled lto by default since some time and I'm quite familiar with occasional problems introduced by it, I tough I already gone that way

@prurigro: that's correct, the only thing necessary is to bump the version. While I understand that doing so is normally considered inappropriate, it seems to me it'd be proper here because compilation is broken otherwise. That being said, I can't find any actual authority saying this is an exception to the rule, so if you felt it'd be better to err on the side of caution, I'd understand.

@frankspace: Hey, I got your out of date notification- am I understanding correctly when I read that as no changes are required for the build to work correctly for you?

I encountered the same issue as emulti. I don't understand why, but without !lto, I also get the "configure: error: Unknown floating point format" error. I wonder if passing something like -ffloat=store or -fexcess-precision=standard would help, but I don't have time to test that right now.

Edit: I don't claim to understand it, but a bug report on Gentoo (https://bugs.gentoo.org/854510) seems to indicate that a "floating point format probe" quite simply does not work with link-time optimization, period. So emulti's recommendation of adding options=(!lto) is the simplest thing to do from here. That said, a patch for a different piece of software (https://github.com/aranym/aranym/commit/52c56bba30ddea27a0a7179da89cac1c71228de6) suggests it may be possible to tamper with the source code. I'll maybe suggest that upstream.

EDIT: upstream made a commit, e12789a, that now fixes the LTO compilation issue.

Configure error:

checking floating point format... configure: error: Unknown floating point format

This error went away for me after adding

options=(!lto)

to the first section of the PKGBUILD. I am no compiler expert, but the same issue was occurring with sheepshaver-git (see the AUR page)

Must be the default link-time-optimization setting of makepkg in /etc/makepkg.conf responsible, as the configure runs fine outside of makepkg. Why this would impact the configure step is a mystery to me.

Edit: The compile time options for makepkg were changed early Feb 2024 in this commit (https://gitlab.archlinux.org/archlinux/packaging/packages/pacman/-/commit/c787e8c65e0b1c92a98f81e8dddf234042cbb4e9)

@prurigro: For -git packages, you don't need to update the PKGBUILD when the only change is in the pkgver. That's what the pkgver function is there for.

Please kindly don't make empty pkgver bumps.

@FabioLolix, this compiles fine for me, but for what it's worth, my complete configure line looks like:

  ./configure \
    --prefix=/usr \
    --enable-sdl-video \
    --enable-sdl-audio \
    --with-sdl2 \
    --disable-vosf \
    --enable-jit-compiler \
    --with-x \
    --with-gtk \
    --with-mon=YES \
    --with-bincue \
    --with-vdeplug

...for whatever help that may be worth.

This is now a duplicate of https://aur.archlinux.org/packages/basiliskii-kanjitalk755-git which don't build with the same error either

Removed the patch.

For some reason the pkgbuild build using makepkg but not using devtools:

checking floating point format... configure: error: Unknown floating point format