Bug#902174: #902174: RFP: mes
- To: Vagrant Cascadian <vagrant@debian.org>
- Cc: 902174@bugs.debian.org
- Subject: Bug#902174: #902174: RFP: mes
- From: Jan Nieuwenhuizen <janneke@gnu.org>
- Date: Wed, 13 Nov 2019 10:43:24 +0100
- Message-id: <[🔎] 87zhh0dscj.fsf@gnu.org>
- Reply-to: Jan Nieuwenhuizen <janneke@gnu.org>, 902174@bugs.debian.org
- In-reply-to: <[🔎] 87h838z9kh.fsf@yucca> (Vagrant Cascadian's message of "Tue, 12 Nov 2019 20:25:50 -0800")
- References: <87vaanor7p.fsf@gnu.org> <20180612173511.s2o2b4ryumxqsjkl@layer-acht.org> <87h8m7nvdm.fsf@gnu.org> <20180623062540.GV30489@gpm.stappers.nl> <20180623062540.GV30489@gpm.stappers.nl> <877em7opfc.fsf@aikidev.net> <874lhboci7.fsf@aikidev.net> <20180623062540.GV30489@gpm.stappers.nl> <87fu0uqa14.fsf@gnu.org> <87h8l9mhl0.fsf@aikidev.net> <87601opiho.fsf@gnu.org> <8736ornwg1.fsf@gnu.org> <87v9y66as9.fsf@yucca> <87h88ym0k4.fsf@gnu.org> <87h88xyc0q.fsf@yucca> <87blz4yks3.fsf@yucca> <[🔎] 87h838z9kh.fsf@yucca> <20180623062540.GV30489@gpm.stappers.nl>
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 <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
Reply to: