Closed kevinushey closed 1 year ago
Perhaps we could apply the changes from https://github.com/mengyao/Complete-Striped-Smith-Waterman-Library/commit/e2c7ccca74633ac61150d55e7c03270ab049b439
@ChangqingW Looks like we should put sse2neon.h to put the to https://github.com/OliverVoogd/FLAMES/tree/master/src/utility/ssw folder?
Otherwise:
g++ -std=gnu++17 -I"/home/biocbuild/bbs-3.17-bioc/R/include" -DNDEBUG -D_FILE_OFFSET_BITS=64 -I'/home/biocbuild/bbs-3.17-bioc/R/library/Rcpp/include' -I'/home/biocbuild/bbs-3.17-bioc/R/library/Rhtslib/include' -I'/home/biocbuild/bbs-3.17-bioc/R/library/zlibbioc/include' -I/usr/local/include -fPIC -g -O2 -Wall -c utility/ssw/ssw_cpp.cpp -o utility/ssw/ssw_cpp.o
In file included from utility/ssw/ssw_cpp.cpp:6:
utility/ssw/ssw.h:19:10: fatal error: sse2neon.h: No such file or directory
19 | #include "sse2neon.h"
| ^~~~~~~~~~~~
compilation terminated.
make: *** [/home/biocbuild/bbs-3.17-bioc/R/etc/Makeconf:198: utility/ssw/ssw_cpp.o] Error 1
ERROR: compilation failed for package ‘FLAMES’
* removing ‘/home/biocbuild/bbs-3.17-bioc/R/library/FLAMES’
[1] Related: https://github.com/Yikun/BBS/issues/7 [2] [Bioc-devel] Support for Linux ARM64: https://stat.ethz.ch/pipermail/bioc-devel/2023-January/019398.html [3] Mac M1 also failed: https://bioconductor.org/checkResults/3.17/bioc-mac-arm64-LATEST/FLAMES/kjohnson2-install.html
@ChangqingW Looks like we should put sse2neon.h to put the to https://github.com/OliverVoogd/FLAMES/tree/master/src/utility/ssw folder?
Otherwise:
g++ -std=gnu++17 -I"/home/biocbuild/bbs-3.17-bioc/R/include" -DNDEBUG -D_FILE_OFFSET_BITS=64 -I'/home/biocbuild/bbs-3.17-bioc/R/library/Rcpp/include' -I'/home/biocbuild/bbs-3.17-bioc/R/library/Rhtslib/include' -I'/home/biocbuild/bbs-3.17-bioc/R/library/zlibbioc/include' -I/usr/local/include -fPIC -g -O2 -Wall -c utility/ssw/ssw_cpp.cpp -o utility/ssw/ssw_cpp.o In file included from utility/ssw/ssw_cpp.cpp:6: utility/ssw/ssw.h:19:10: fatal error: sse2neon.h: No such file or directory 19 | #include "sse2neon.h" | ^~~~~~~~~~~~ compilation terminated. make: *** [/home/biocbuild/bbs-3.17-bioc/R/etc/Makeconf:198: utility/ssw/ssw_cpp.o] Error 1 ERROR: compilation failed for package ‘FLAMES’ * removing ‘/home/biocbuild/bbs-3.17-bioc/R/library/FLAMES’
[1] Related: Yikun/BBS#7 [2] [Bioc-devel] Support for Linux ARM64: https://stat.ethz.ch/pipermail/bioc-devel/2023-January/019398.html [3] Mac M1 also failed: https://bioconductor.org/checkResults/3.17/bioc-mac-arm64-LATEST/FLAMES/kjohnson2-install.html
Done. Could you check if this fixed the problem? I don't have an arm machine. Feel free to make a PR.
$ uname -m
aarch64
$ /home/biocbuild/bbs-3.17-bioc/R/bin/R
R Under development (unstable) (2023-01-14 r83615) -- "Unsuffered Consequences"
Copyright (C) 2023 The R Foundation for Statistical Computing
Platform: aarch64-unknown-linux-gnu (64-bit)
> BiocManager::install("OliverVoogd/FLAMES")
installing to /home/biocbuild/bbs-3.17-bioc/R/library/00LOCK-FLAMES/00new/FLAMES/libs
** R
** inst
** byte-compile and prepare package for lazy loading
** help
*** installing help indices
** building package indices
** installing vignettes
** testing if installed package can be loaded from temporary location
** checking absolute paths in shared objects and dynamic libraries
** testing if installed package can be loaded from final location
** testing if installed package keeps a record of temporary installation path
* DONE (FLAMES)
> BiocManager::install("OliverVoogd/FLAMES")
Bioconductor version 3.17 (BiocManager 1.30.19), R Under development (unstable)
(2023-01-14 r83615)
Installing github package(s) 'OliverVoogd/FLAMES'
Skipping install of 'FLAMES' from a github remote, the SHA1 (42363bce) has not changed since last install.
Use `force = TRUE` to force installation
@ChangqingW Many thanks! I validated it in a Linux aarch64, it works!
Please let me know if I can help more. : )
Hi @OliverVoogd, the missing sse2neon.h
header issue showed up again in BioC 3.19, I think the fix only made it to older branches?
When I try to build this package from sources on my M1 macOS machine, I see:
Would it be possible to avoid the use of intrinsics on arm64 / aarch64?