Bug#1111064: laserboy: FTBFS: Fix build error on non-x86_64 architectures
* zhangdandan <zhangdandan@loongson.cn> [250815 19:47]:
> Compiling the laserboy failed on loong64 and other non x86_64 architectures
> in the Debian Package Auto-Building environment.
> The error log is as follows,
> ```
> ......
> make[2]: Entering directory '/<<PKGBUILDDIR>>/src'
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
> -ffile-prefix-map=/<<PKGBUILDDIR>>=. -fstack-protector-strong -Wformat
> -Werror=format-security -Wl,-z,relro -Wl,-z,now -c LaserBoy.cpp -o
> ../build/LaserBoy.obj -D__WITH_SDL2__ -std=c++17 -O3 -msse2 -mfpmath=sse
> -Wall -Wextra -frounding-math -fsignaling-nans -Wno-unused-parameter
> -Wno-implicit-fallthrough -Wno-missing-field-initializers
> -Wno-misleading-indentation -Wno-unused-but-set-variable
> -Wno-mismatched-new-delete -fexpensive-optimizations -static
> -L/usr/local/lib -lSDL2 -lboost_filesystem -lboost_system -lpthread
> g++: error: unrecognized command-line option ‘-msse2’
> g++: error: unrecognized command-line option ‘-mfpmath=sse’
> ......
> ```
> The full build log can be found at
> https://buildd.debian.org/status/package.php?p=laserboy&suite=sid.
> Maybe we need to filter out '-msse2 -mfpmath=sse' on non-x86_64
> architectures.
> Please consider the patch I attached.
> Based on attached patch, I have built laserboy (2024.03.08+dfsg-1+loong64)
> successfully on locally.
> ```
> ......
> dh_builddeb
> dpkg-deb: building package 'laserboy-indep' in
> '../laserboy-indep_2024.03.08+dfsg-1+loong64_all.deb'.
> dpkg-deb: building package 'laserboy' in
> '../laserboy_2024.03.08+dfsg-1+loong64_loong64.deb'.
> dpkg-deb: building package 'laserboy-dbgsym' in
> '../laserboy-dbgsym_2024.03.08+dfsg-1+loong64_loong64.deb'.
> dpkg-genbuildinfo -O../laserboy_2024.03.08+dfsg-1+loong64_loong64.buildinfo
> dpkg-genchanges -O../laserboy_2024.03.08+dfsg-1+loong64_loong64.changes
> ```
> Your opinions are welcome.
Hi,
I’m sorry, I uploaded a new version before seeing your bug report.
In my patch, I removed the sse2 option completely because I think that a
specific package is not supposed to restrict which CPU should be supported
by a Debian package.
Your opinions are welcome too.
Kind regards,
Nicolas.
Reply to: