Hi Michael,
I'd like to bring this issue to your attention. Usually it seems
to be cheap to patch out -msse2 from options. However, I'm hesitating
with this for targets explicitly named
ksw2_extz2_sse2.o:ksw2_extz2_sse.c
Since I have no idea about minimap2 at all I'd prefer to be a bit
careful - may be discussing the issue with upstream should be done in
case you have no idea as well.
Kind regards
Andreas.
Am Fri, Oct 15, 2021 at 04:37:51PM +0300 schrieb Adrian Bunk:
> Source: minimap2
> Version: 2.22+dfsg-1
> Severity: serious
> Tags: ftbfs
>
> https://buildd.debian.org/status/logs.php?pkg=minimap2&ver=2.22%2Bdfsg-1
>
> ...
> cc -c -g -O2 -ffile-prefix-map=/<>=. -fstack-protector-strong
> -Wformat -Werror=format-security -fopenmp-simd -O3 -DSIMDE_ENABLE_OPENMP
> -DUSE_SIMDE -DSIMDE_ENABLE_NATIVE_ALIASES -g -Wall -O2 -Wc++-compat -msse2
> -Wdate-time -D_FORTIFY_SOURCE=2 -DHAVE_KALLOC ksw2_ll_sse.c -o ksw2_ll_sse.o
> cc: error: unrecognized command-line option ‘-msse2’
> make[2]: *** [Makefile:64: ksw2_ll_sse.o] Error 1
> ___
> Debian-med-packaging mailing list
> debian-med-packag...@alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-med-packaging
--
http://fam-tille.de
