[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#953584: libsbml: FTBFS on mipsel

Andreas Tille <tille@debian.org> 于2020年3月11日周三 下午4:00写道:
> Hi Ivo,
> On Tue, Mar 10, 2020 at 09:35:25PM +0000, Ivo De Decker wrote:
> > The latest upload of libsbml to unstable fails on mipsel:
> >
> > https://buildd.debian.org/status/package.php?p=libsbml
> This says:
> ...
> [100%] Building CXX object src/bindings/python/CMakeFiles/binding_python_lib.dir/libsbml_wrap.cpp.o
> /tmp/ccOdlaux.s: Assembler messages:
> /tmp/ccOdlaux.s: Fatal error: can't close CMakeFiles/binding_python_lib.dir/libsbml_wrap.cpp.o: memory exhausted
> make[4]: *** [src/bindings/python/CMakeFiles/binding_python_lib.dir/build.make:645: src/bindings/python/CMakeFiles/binding_python_lib.dir/libsbml_wrap.cpp.o] Error 1
> make[4]: Leaving directory '/<<PKGBUILDDIR>>/build'
> make[3]: *** [CMakeFiles/Makefile2:694: src/bindings/python/CMakeFiles/binding_python_lib.dir/all] Error 2
> ...
> If there is no chance to extend the memory on this porter machine I

Currently no...
In fact all of 32bit platform may meet this problem, and mipsel is the
first one.
It is not due to the lack of memory on build machine. Instead, it is
due to the 2GiB userspace memory limiation.
the value of i386 is 3GiB.

I have a plan to figure out a gcc64/binutils64 toolchain for these
32bit architectures.

This schema cannot work on all 32bit architectures, since some of them
doesn't have paired 64bit machines.

> think the best idea is to exclude this architecture where probability
> that this package is used is pretty close to zero anyway.

You can do so for now.

> Kind regards
>        Andreas.
> --
> http://fam-tille.de

YunQiang Su

Reply to: