Your message dated Fri, 05 Sep 2014 19:22:08 +0200
with message-id <5409f140.3050...@debian.org>
and subject line Re: Bug#729767: H5detect failed to run on mips64el
has caused the Debian Bug report #729767,
regarding H5detect failed to run on mips64el
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 ow...@bugs.debian.org
immediately.)


-- 
729767: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: hdf5
Version: 1.8.11-5

I try to build hdf5 on mips64el, while H5detect failed to build.
If you need to use porterbox, please contact with me.

syq@thor> ./debian/build/src/H5detect

                 ~/hdf5/hdf5-1.8.11
/* Generated automatically by H5detect -- do not edit */



/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 * Copyright by The HDF Group.                                               *
 * Copyright by the Board of Trustees of the University of Illinois.         *
 * All rights reserved.                                                      *
 *                                                                           *
 * This file is part of HDF5.  The full HDF5 copyright notice, including     *
 * terms governing use, modification, and redistribution, is contained in    *
 * the files COPYING and Copyright.html.  COPYING can be found at the root   *
 * of the source code distribution tree; Copyright.html can be found at the  *
 * root level of an installed copy of the electronic HDF5 document set and   *
 * is linked from the top-level documents page.  It can also be found at     *
 * http://hdfgroup.org/HDF5/doc/Copyright.html.  If you do not have          *
 * access to either file, you may request a copy from h...@hdfgroup.org.     *
 * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 *
 * Created:        Nov 17, 2013
 *            syq@thor
 *
 * Purpose:        This machine-generated source code contains
 *            information about the various integer and
 *            floating point numeric formats found on this
 *            architecture.  The parameters below should be
 *            checked carefully and errors reported to the
 *            HDF5 maintainer.
 *
 *            Each of the numeric formats listed below are
 *            printed from most significant bit to least
 *            significant bit even though the actual bytes
 *            might be stored in a different order in
 *            memory.     The integers above each binary byte
 *            indicate the relative order of the bytes in
 *            memory; little-endian machines have
 *            decreasing numbers while big-endian machines
 *            have increasing numbers.
 *
 *            The fields of the numbers are printed as
 *            letters with `S' for the mantissa sign bit,
 *            `M' for the mantissa magnitude, and `E' for
 *            the exponent.  The exponent has an associated
 *            bias which can be subtracted to find the
 *            true exponent.    The radix point is assumed
 *            to be before the first `M' bit.     Any bit
 *            of a floating-point value not falling into one
 *            of these categories is printed as a question
 *            mark.  Bits of integer types are printed as
 *            `I' for 2's complement and `U' for magnitude.
 *
 *            If the most significant bit of the normalized
 *            mantissa (always a `1' except for `0.0') is
 *            not stored then an `implicit=yes' appears
 *            under the field description.  In thie case,
 *            the radix point is still assumed to be
 *            before the first `M' but after the implicit
 *            bit.
 *
 * Modifications:
 *
 *    DO NOT MAKE MODIFICATIONS TO THIS FILE!
 *    It was generated by code in `H5detect.c'.
 *
 *-------------------------------------------------------------------------
 */

[1]    8971 illegal hardware instruction  ./debian/build/src/H5detect
syq@thor> gdb ./debian/build/src/H5detect

                 ~/hdf5/hdf5-1.8.11
GNU gdb (GDB) 7.6.1 (Debian 7.6.1-1)
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "mips64el-linux-gnuabi64".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from
/home/syq/hdf5/hdf5-1.8.11/debian/build/src/H5detect...done.
(gdb) r
Starting program: /home/syq/hdf5/hdf5-1.8.11/./debian/build/src/H5detect
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/mips64el-linux-gnuabi64/libthread_db.so.1".

Program received signal SIGBUS, Bus error.
0x000000fff7f8defc in raise () from /lib/mips64el-linux-gnuabi64/libpthread.so.0
(gdb) backtrace
#0  0x000000fff7f8defc in raise () from
/lib/mips64el-linux-gnuabi64/libpthread.so.0
#1  0x000000012000220c in verify_signal_handlers
(signum=signum@entry=10, handler=handler@entry=0x120002080
<sigbus_handler>) at ../../../src/H5detect.c:1609
#2  0x00000001200012b8 in main () at ../../../src/H5detect.c:1682

-- 
YunQiang Su

--- End Message ---
--- Begin Message ---
YunQiang Su a écrit , Le 05/09/2014 19:03:
> On Fri, Sep 5, 2014 at 6:29 AM, pini <p...@pustule.org> wrote:
>> Hi,
>>
>> Does this failure still occur with release 1.8.13 in unstable?
>> If so an access to a porterbox would be appreciated.
>>
> 
> It works now. thank you very much.

Closing the bug then.

Thanks,

_g.


Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel

Reply via email to