Re: hypre failing dwz on mispen

YunQiang Su <[email protected]>
Newsgroups gmane.linux.debian.ports.mips
Message-ID <CAKcpw6WoZEZRqTJg3-yNca0byVC7B-3x9VJ8gUjdCFAADAFc=Q@mail.gmail.com>
Drew Parsons <[email protected]> 于2019年7月15日周一 上午12:48写道:
>
> hypre 2.16.0-2 fails build at dh_dwz on mips, mipsel and mips64el,
> https://buildd.debian.org/status/package.php?p=hypre.  2.16.0-1exp1
> previously built successfully.
>
> Building on eller,debian.org, dh_dwz -v gives more detail:
>
> $ dh_dwz -v -O--sourcedirectory=src
>         dwz -q
> -mdebian/libhypre-2.16.0/usr/lib/debug/.dwz/mips64el-linux-gnuabi64/libhypre-2.16.0.debug
> -M/usr/lib/debug/.dwz/mips64el-linux-gnuabi64/libhypre-2.16.0.debug --
> debian/libhypre-2.16.0/usr/lib/mips64el-linux-gnuabi64/libHYPRE-2.16.0.so
> debian/libhypre-2.16.0/usr/lib/mips64el-linux-gnuabi64/libHYPRE_FEI-2.16.0.so
> debian/libhypre-2.16.0/usr/lib/mips64el-linux-gnuabi64/libHYPRE_core-2.16.0.so
> dwz:
> debian/libhypre-2.16.0/usr/lib/mips64el-linux-gnuabi64/libHYPRE_core-2.16.0.so:
> .gnu_debugaltlink section already present
> dwz: Too few files for multifile optimization
> dh_dwz: dwz -q
> -mdebian/libhypre-2.16.0/usr/lib/debug/.dwz/mips64el-linux-gnuabi64/libhypre-2.16.0.debug
> -M/usr/lib/debug/.dwz/mips64el-linux-gnuabi64/libhypre-2.16.0.debug --
> debian/libhypre-2.16.0/usr/lib/mips64el-linux-gnuabi64/libHYPRE-2.16.0.so
> debian/libhypre-2.16.0/usr/lib/mips64el-linux-gnuabi64/libHYPRE_FEI-2.16.0.so
> debian/libhypre-2.16.0/usr/lib/mips64el-linux-gnuabi64/libHYPRE_core-2.16.0.so
> returned exit code 1
>
>
>
> I'm not familiar with dwz or these errors, so it's not clear to me how
> to proceed.  Is the problem related to the build failure of dwz
> 0.12.20190711-1 on mipsen?  The version of dwz on the eller chroot is
> 0.12.20190710-1.

I just try to build hypre with dwz  0.12.20190716-1.
It build successfully. So I guess we should have a retry to build hypre on mips*

>
>
> Drew
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.