Bug#840030: lambda-align: FTBFS on non-Linux: undefined references to aio_*64
Source: lambda-align Version: 1.0.0-1 Severity: important Justification: fails to build from source The kfreebsd-amd64 build of lambda-align failed: /usr/include/seqan/system/file_async.h:1003: undefined reference to `aio_suspend64' /usr/include/seqan/system/file_async.h:1004: undefined reference to `aio_return64' /usr/include/seqan/system/file_async.h:1010: undefined reference to `aio_error64' [...] Please take care to link against -lrt on kFreeBSD and the Hurd, not just Linux. Thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#840030: [Debian-med-packaging] Bug#840030: lambda-align: FTBFS on non-Linux: undefined references to aio_*64
Hi Aaron, thanks again for noticing. > The kfreebsd-amd64 build of lambda-align failed: > > /usr/include/seqan/system/file_async.h:1003: undefined reference to > `aio_suspend64' > /usr/include/seqan/system/file_async.h:1004: undefined reference to > `aio_return64' > /usr/include/seqan/system/file_async.h:1010: undefined reference to > `aio_error64' > [...] > > Please take care to link against -lrt on kFreeBSD and the Hurd, not > just Linux. As these get set by FindSeqan.cmake in libseqan2-dev (via $SEQAN_LIBRARIES) I guess this issue must be fixed there as ‘Linux' is currently hardcoded [1]. I’ll take a look. Cheers Sascha P.S. Just wanting to say that I'm very thankful for your investigations and constructive bug reports for these architectures. Much appreciated! [1] https://github.com/seqan/seqan/blob/master/util/cmake/FindSeqAn.cmake#L290
Bug#840030: [Debian-med-packaging] Bug#840030: lambda-align: FTBFS on non-Linux: undefined references to aio_*64
Sascha Steinbiss writes: > As these get set by FindSeqan.cmake in libseqan2-dev (via $SEQAN_LIBRARIES) I > guess this issue must be fixed there as ‘Linux' is currently hardcoded [1]. > I’ll take a look. Ah, OK; I hadn't traced it back. > P.S. Just wanting to say that I'm very thankful for your investigations and > constructive bug reports for these architectures. Much appreciated! Glad to hear it. I suppose I could take it one step further and perform team uploads, but I prefer to leave those to primary maintainers. -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
