Your message dated Fri, 22 Apr 2016 14:38:33 +0200
with message-id <[email protected]>
and subject line Re: Bug#821924: libvigraimpex: multi_array_chunked_hdf5.hxx
corrupted on mipsel
has caused the Debian Bug report #821924,
regarding libvigraimpex: multi_array_chunked_hdf5.hxx corrupted on mipsel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
821924: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821924
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvigraimpex-dev
Version: 1.10.0+git20160211.167be93+dfsg-2
User: [email protected]
Usertags: mipsel
$ sed -ne 264p
libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array_chunked_hdf5.hxx
| cat -A
// H5Pset_chunk_cache (dapl, rdcc_nslots, rdcc_nbytes, rdcc_w0);$
But in the mips binary package, this line is corrupted:
$ sed -ne 264p /usr/include/*/multi_array_chunked_hdf5.hxx | cat -A
^@// H5Ps^@t_chunk cache (eapl, rdcc_nslots, rdcc_nbytes, rdcc_w0);$
I have no idea how could this happen. It smells like a hardware problem.
(I CCed [email protected] and [email protected].)
--
Jakub Wilk
--- End Message ---
--- Begin Message ---
On 2016-04-20 15:28, Jakub Wilk wrote:
> Package: libvigraimpex-dev
> Version: 1.10.0+git20160211.167be93+dfsg-2
> User: [email protected]
> Usertags: mipsel
>
> $ sed -ne 264p
> libvigraimpex-1.10.0+git20160211.167be93+dfsg/include/vigra/multi_array_chunked_hdf5.hxx
> | cat -A
> // H5Pset_chunk_cache (dapl, rdcc_nslots, rdcc_nbytes, rdcc_w0);$
>
> But in the mips binary package, this line is corrupted:
>
> $ sed -ne 264p /usr/include/*/multi_array_chunked_hdf5.hxx | cat -A
> ^@// H5Ps^@t_chunk cache (eapl, rdcc_nslots, rdcc_nbytes, rdcc_w0);$
>
>
> I have no idea how could this happen. It smells like a hardware problem. (I
> CCed [email protected] and [email protected].)
This looks strange. It can be a hardware issue, a kernel issue, or a
still a chrpath issue (i haven't found time to fix cmake yet).
Anyway I have binNMued it, it build on the same machine and the problem
is gone. I am therefore closing the bug.
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
[email protected] http://www.aurel32.net
--- End Message ---
--
debian-science-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-science-maintainers
