Re: dolfin FTBFS on mips64el: ld error adding symbols: bad value

YunQiang Su <[email protected]>
Newsgroups gmane.linux.debian.ports.mips
Message-ID <CAKcpw6W88G1UsJ2Buw6uxQayJs7AURTPvdmvL+VmBKUEQW04ew@mail.gmail.com>
Drew Parsons <[email protected]> 于2020年8月25日周二 上午12:29写道:
>
> On 2020-08-22 18:52, Drew Parsons wrote:
> > On 2020-08-19 23:08, Drew Parsons wrote:
> >> Can anyone help with the mips64el build of dolfin?  It's failing when
> >> building python extensions:
> >>
> >> /usr/bin/ld:
> >> /tmp/cpp.cpython-38-mips64el-linux-gnuabi64.so.AnBotY.ltrans29.ltrans.o:
> >> .symtab local symbol at index 482 (>= sh_info of 99)
> >> /usr/bin/ld:
> >> /tmp/cpp.cpython-38-mips64el-linux-gnuabi64.so.AnBotY.ltrans29.ltrans.o:
> >> error adding symbols: bad value
> >> collect2: error: ld returned 1 exit status
> >
> >> (see
> >> https://buildd.debian.org/status/logs.php?pkg=dolfin&arch=mips64el )
>
>
> The error is reproducible on porterbox (sid_mips64el-dchroot chroot on
> eller.debian.org)
>
> If the problem is not a full /tmp partition, could the error be caused
> by some inconsistent library caught badly in the middle of the gcc-10
> transition?  How to know?

Maybe. Let's have a check.
I think that we can have a try to build the previous version.
I will do it.

>
> Drew
>


-- 
YunQiang Su
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.