Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build fails on i386 #1365

Closed
mr-c opened this issue Nov 17, 2019 · 1 comment
Closed

Build fails on i386 #1365

mr-c opened this issue Nov 17, 2019 · 1 comment
Labels
bug faulty or wrong behaviour of code

Comments

@mr-c
Copy link
Contributor

mr-c commented Nov 17, 2019

Platform

Description

How to repeat the problem

Build the seqan3 debian package on an i386 system

Expected behaviour

Build complete

Actual behaviour

/include/seqan3/alphabet/concept.hpp:155:22: error: invalid parameter type ‘seqan3::alphabet_rank_t<wchar_t&>’ {aka ‘void’}
/include/seqan3/alphabet/concept.hpp:155:22: error: in declaration ‘constexpr alph_t seqan3::detail::adl::only::assign_rank_to_fn::operator()(seqan3::alphabet_rank_t<alph_t>, alph_t&&) const’
In file included from /usr/include/gtest/gtest.h:375,
                 from test/unit/alphabet/adaptation/char_test.cpp:10:
test/unit/alphabet/adaptation/char_test.cpp:80:5: error: invalid use of void expression
   80 |     EXPECT_EQ(to_rank(TypeParam{65}), cmp);
      |     ^
test/unit/alphabet/adaptation/char_test.cpp:70:15: error: invalid application of ‘sizeof’ to a void type [-Werror=pointer-arith]
   70 |     EXPECT_GE(sizeof(alphabet_rank_t<TypeParam>), sizeof(TypeParam));
      |               ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Full log: https://buildd.debian.org/status/fetch.php?pkg=seqan3&arch=i386&ver=3.0.0%2Bds2-2&stamp=1574012481&raw=0

@mr-c mr-c added the bug faulty or wrong behaviour of code label Nov 17, 2019
@mr-c
Copy link
Contributor Author

mr-c commented Jan 14, 2020

From @marehr "we don't support 32 bit systems [yet]"

#1481 has been opened to document this

@mr-c mr-c closed this as completed Jan 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug faulty or wrong behaviour of code
Projects
None yet
Development

No branches or pull requests

1 participant