Vagrant Cascadian writes:
> Updated to 0.20 a while back and have iterated through a few test builds
> on i386, and it appears to be working:
>
> https://salsa.debian.org/vagrant/mes
\o/
>> A few test failures on amd64, but i386 tests run fine.
>
> Still one test suite failure on amd64, i386 works fine. The failing test
> on amd64 is:
>
> lib/tests/dirent/90-readdir.c
>
> Is there any way to mark the failing test as XFAIL conditionally by
> architecture?
As a developer: yes; not really as a user/packager atm. IOW, you will
need a patch.
The strange thing is that I tried to reproduce on a bullseye/sid VM of
about 2months ago; and for me all tests pass?
Anyway, I have updated the wip-0.20 branch to include three patches
--8<---------------cut here---------------start------------->8---
build: Mark lib/tests/dirent/90-readdir.c as XFAIL on x86_64-gcc.
build: Mark lib/tests/dirent/90-readdir.c as XFAIL on x86_64-mescc.
build: Mark lib/tests/dirent/90-readdir.c as XFAIL on x86_64.
--8<---------------cut here---------------end--------------->8---
you can cherry-pick the one that works for you.
> A bigger blocker at this point is that mes installs numerous files in
> /usr/include/, such as /usr/include/alloca.h, that conflict with other
> packages such as libc6-dev. In a Debian environment, we typically can't
> have multiple packages shipping the same files in the same PATHS. Other
> libc implementations seem to put them in /usr/include/IMPLEMENTATION/
> subdirs, e.g. /usr/include/mes/.
On wip-0.20, I have fixed install to honor configure's
--includedir=<some dir>, so you may use
./configure --includedir=/usr/include/mes
that should work now.
> With the /usr/include issue solved and ideally the test suite failure
> too, it would in my opinion be feasible to upload to Debian!
Hope this fixes it,
a big thank you again!
janneke
--
Jan Nieuwenhuizen <[email protected]> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
