gdcm: Dep-Wait: mono-runtime

Could someone please let me know what is going on with gdcm buildd ? I have taken out mono from mipsel: $ cat control ... mono-devel (= 2.0) [!alpha !armel !mipsel !m68k !hppa] ... But it still shows up as: Dep-Wait: mono-runtime on https://buildd.debian.org/pkg.cgi?pkg=gdcm thank you --

Re: gdcm: Dep-Wait: mono-runtime

On Mon, Jul 13, 2009 at 6:39 PM, Luk Claesl...@debian.org wrote: Mathieu Malaterre wrote: Could someone please let me know what is going on with gdcm buildd ? I have taken out mono from mipsel: $ cat control ...  mono-devel (= 2.0) [!alpha !armel !mipsel !m68k !hppa] ...   But it still

Please remove sticky Dep-Wait: libvtk5 (= 5.2.1-3) on gdcm

Please clear sticky Dep-Wait: libvtk5 (= 5.2.1-3) on gdcm package. Ref: https://buildd.debian.org/pkg.cgi?pkg=gdcm Thank you -- Mathieu -- To UNSUBSCRIBE, email to debian-mips-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: GCC-4.5 as the default for (at least some) architectures

On Tue, Apr 26, 2011 at 5:31 PM, Konstantinos Margaritis mar...@genesi-usa.com wrote: On 26 April 2011 18:03, Matthias Klose d...@debian.org wrote: I'll make GCC 4.6 the default after the release of GCC 4.5.3, expected later this week, at least on amd64, armel, i386 and powerpc. Could you

Re: o32 != n32

On Thu, May 7, 2015 at 11:41 AM, James Cowgill james...@cowgill.org.uk wrote: On Thu, 2015-05-07 at 11:25 +0200, Mathieu Malaterre wrote: On Thu, May 7, 2015 at 10:57 AM, James Cowgill james...@cowgill.org.uk wrote: On Thu, 2015-05-07 at 09:27 +0200, Mathieu Malaterre wrote: Hello MIPS

Re: o32 != n32

Hi James, On Thu, May 7, 2015 at 10:57 AM, James Cowgill james...@cowgill.org.uk wrote: On Thu, 2015-05-07 at 09:27 +0200, Mathieu Malaterre wrote: Hello MIPS gurus, Could someone please let me know if this is possible to have a dual-ABI system (eg: n32 o32) on MIPS. On my x86-64 system I

o32 != n32

Hello MIPS gurus, Could someone please let me know if this is possible to have a dual-ABI system (eg: n32 o32) on MIPS. On my x86-64 system I can run a multi-arch system (x86 x86-64), thanks to the recent multi-arch effort. Is it possible on MIPS ? Does it make sense ? Thanks, -- To

Re: o32 != n32

On Thu, May 7, 2015 at 4:24 PM, YunQiang Su wzss...@gmail.com wrote: On Thu, May 7, 2015 at 6:01 PM, Mathieu Malaterre ma...@debian.org wrote: On Thu, May 7, 2015 at 11:41 AM, James Cowgill james...@cowgill.org.uk wrote: On Thu, 2015-05-07 at 11:25 +0200, Mathieu Malaterre wrote: On Thu, May

src:tbb on mips

Hi there, src:tbb was uploaded over the week end. We've included a patch to fix compilation on mips and powerpc (see #787084 for details). Everything went -finally- fine on powerpc. However I was suprised to see test failures on mips:

Re: [Stretch] Status for architecture qualification

Hi Hector, On Thu, Jun 16, 2016 at 2:12 AM, Hector Oron wrote: [...] > While working out ArchitectureQualification/Stretch wiki page I > believe everything is mostly fine for release, however I got a > personal concern on powerpc architecture. Is it well maintained? Does >

Re: SGI O2 Jessie kernel issue

On Sun, Feb 21, 2016 at 10:49 PM, Florian Lohoff wrote: > On Wed, Feb 17, 2016 at 09:01:10AM -0500, Stefan Monnier wrote: >> > I own a SGI O2 which is running as a shell-, mail- and webserver since >> > 2006. The machine has 1 GB of RAM and two 72 GB hard disks configured as >> >

Re: Bug#815998: golang: add mips64/mips64el support

On Tue, Aug 30, 2016 at 8:31 AM, Mathieu Malaterre <ma...@debian.org> wrote: > On Sun, Aug 28, 2016 at 5:12 PM, Tianon Gravi <tia...@debian.org> wrote: >> Given that upstream officially supports bootstrapping via gccgo, I'd >> rather keep the discussion of "fix

Re: Bug#815998: golang: add mips64/mips64el support

On Sun, Aug 28, 2016 at 5:12 PM, Tianon Gravi wrote: > Given that upstream officially supports bootstrapping via gccgo, I'd > rather keep the discussion of "fix cross build" to a separate issue if > we can. I am interested in updating the packaging to properly support >

Re: Porter roll call for Debian Stretch

Hi all, On Fri, Sep 23, 2016 at 3:54 PM, Matthias Klose wrote: > On 20.09.2016 23:46, John Paul Adrian Glaubitz wrote: >> On 09/20/2016 11:16 PM, Niels Thykier wrote: >>>- powerpc: No porter (RM blocker) >> >> I'd be happy to pick up powerpc to keep it for Stretch. I'm

Re: Porter roll call for Debian Stretch

Adrian, On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz wrote: [...] > On the other hand, some packages dropped support for PowerPC32 like Mono > but this isn't a concern for most users, I would say. [...] Thanks very much for stepping up as porter, you

Re: Porter roll call for Debian Stretch

On Sat, Oct 1, 2016 at 2:28 AM, Adam Borowski <kilob...@angband.pl> wrote: > On Fri, Sep 30, 2016 at 11:01:55PM +0200, Mathieu Malaterre wrote: >> On Fri, Sep 30, 2016 at 10:34 PM, John Paul Adrian Glaubitz >> <glaub...@physik.fu-berlin.de> wrote: >> [...] >

Re: [Ceph-maintainers] Bug#849657: ceph: FTBFS on mips(el): g++: virtual memory exhausted: Cannot allocate memory

On Fri, Dec 30, 2016 at 10:06 AM, Emilio Pozuelo Monfort wrote: > On 29/12/16 20:56, Gaudenz Steinlin wrote: >> >> Hi Emilio >> >> Emilio Pozuelo Monfort writes: >> >>> Source: ceph >>> Version: 10.2.5-2 >>> Severity: serious >>> >>> Your package failed to

Re: Bug#858405: xmlto: intermittent Segmentation fault when building manpages for libreswan on mips64el

Seems like debian-mips@l.d.o was missing (I added mips64el tag) On Wed, Mar 22, 2017 at 2:29 AM, Daniel Kahn Gillmor wrote: > Package: xmlto > Version: 0.0.28-1 > Severity: normal > > https://buildd.debian.org/status/fetch.php?pkg=libreswan=mips64el=3.20-6=1490132010=0 >

Re: kodi on ci20 creator

On Mon, Apr 3, 2017 at 6:11 PM, James Cowgill <james...@cowgill.org.uk> wrote: > Hi, > > On 02/04/17 18:06, James Cowgill wrote: >> [+CC multimedia team] >> >> On 02/04/17 17:38, Mathieu Malaterre wrote: >>> On Sun, Apr 2, 2017 at 6:03 PM, Mathieu M

CI20 Creator as media center (kodi)

Hi there, So right now what prevent the Creator CI20 from being a good replacement of a RPI2B+ (for example) is the video hardware decoding capabilities, right ? Is anyone working on it ? I do not see much activities in: https://groups.google.com/forum/#!forum/mips-creator-ci20-dev Also, does

kodi on ci20 creator

Hi there, Does anyone knows what is going on with kodi dependencies on mipel ? root@ci20:~# apt-cache policy libavcodec57 libavcodec57: Installed: (none) Candidate: 7:3.0.2-4~bpo8+1 Version table: 7:3.0.2-4~bpo8+1 0 100 http://ftp.fr.debian.org/debian/ jessie-backports/main

Re: kodi on ci20 creator

On Sun, Apr 2, 2017 at 6:03 PM, Mathieu Malaterre <ma...@debian.org> wrote: > Hi there, > > Does anyone knows what is going on with kodi dependencies on mipel ? OK I think I see the build dependencies loop: https://buildd.debian.org/status/package.php?p=chromaprint=jessie-backports

Bug#613610: xburst-tools: contains precompiled binaries in debian/

Hi there, > It should be works just fine. I have done this before:(just FYI) > http://downloads.openmobilefree.net/NanoNote/xburst-tools/mipsel/ So the link has disappeared. What is the status of xburst-tools in Debian ? Do we really want that package in Debian ? Thanks for comments

Re: kodi on ci20 creator

On Tue, Apr 4, 2017 at 11:11 AM, James Cowgill <jcowg...@debian.org> wrote: > Hi, > > On 04/04/17 09:47, Mathieu Malaterre wrote: >> On Mon, Apr 3, 2017 at 6:11 PM, James Cowgill <james...@cowgill.org.uk> >> wrote: >>> Hi, >>> >>> On 02

#warning "Consider adding the right clone() syscall definitions here!"

Hi there, Did anyone review the warning(s) generated during systemd building on mipsel* ? I am starring at the clone warning (mmap seems to trigger something equivalent apparently): https://buildd.debian.org/status/fetch.php?pkg=systemd=mips64el=232-22=1490743348=0 See:

CI20: jz4780-rng

Hi there, If anyone owns a CI20 (or X1000 SoC) I'd be interested in feedback from the attached patch. Thanks much ! jz4780_rng_cgu_v3.patch Description: Binary data

Re: Bug#841645: golang-go: There is no mips64el support

Hi Tianon, > The main issue with getting it in essentially boils down to gccgo and > upstream Go disagreeing on the GOARCH for mips64el (gccgo uses > "mipsn64"[0]), which makes bootstrapping difficult. > > [0]: https://groups.google.com/d/topic/golang-nuts/waTy56I_KWQ/discussion Are you saying

Fwd: Free MIPS hardware....you pay shipping.

FYI -- Forwarded message -- From: Steven J. Hill Date: Thu, Jun 15, 2017 at 7:02 PM Subject: Free MIPS hardwareyou pay shipping. To: linux-m...@linux-mips.org, port-sgim...@netbsd.org, port-m...@netbsd.org, port-hpcm...@netbsd.org,

Re: Bug#861171: #warning "Consider adding the right clone() syscall definitions here!"

Control: tags -1 patch On Wed, May 3, 2017 at 11:10 AM, James Cowgill <jcowg...@debian.org> wrote: > Control: forwarded -1 https://github.com/systemd/systemd/pull/5880 > > Hi, > > On 25/04/17 12:55, Michael Biebl wrote: >> Am 25.04.2017 um 12:56 schrieb Mathieu Mala

Ingenic X1000 SoC or halley2 development kit?

Hi all, Does anyone have access to Ingenic X1000 SoC or halley2 development kit ? Please contact me. Thanks.

#849657: virtual memory exhausted: Cannot allocate memory

Dear mips gurus, Could someone please suggest a fix for the following FTBFS issue for OpenVDB package: https://buildd.debian.org/status/fetch.php?pkg=openvdb=mipsel=4.0.2-1=1508213166=0 Thanks much

mips/mipsel: enforce --param ggc-min-expand=10 always (was: virtual memory exhausted: Cannot allocate memory)

YunQiang, Do you know of any drawbacks ? On Thu, Nov 23, 2017 at 11:29 AM, YunQiang Su <wzss...@gmail.com> wrote: > I guess we should set this param for mips/mipsel by default? > > On Thu, Nov 23, 2017 at 5:20 AM, Mathieu Malaterre <ma...@debian.org> wrote: >> On W

Re: mips/mipsel: enforce --param ggc-min-expand=10 always

Hi James, On Thu, Nov 23, 2017 at 1:14 PM, James Cowgill <jcowg...@debian.org> wrote: > On 23/11/17 11:42, Mathieu Malaterre wrote: >> YunQiang, >> >> Do you know of any drawbacks ? > > This has been raised before: > https://lists.debian.org/debian-mips/20

Re: #879636: virtual memory exhausted: Cannot allocate memory

On Wed, Nov 22, 2017 at 2:24 PM, Mathieu Malaterre <ma...@debian.org> wrote: > Dear mips gurus, > > Could someone please suggest a fix for the following FTBFS issue for > OpenVDB package: > > https://buildd.debian.org/status/fetch.php?pkg=openvdb=mipsel=4.0.2-1=1508213166=

Re: Debian/MIPSeb: proposal to drop mipseb port?

On Mon, Jul 9, 2018 at 12:47 PM YunQiang Su wrote: > > Mathieu Malaterre 于2018年7月9日周一 下午6:31写道： > > > > On Mon, Jul 9, 2018 at 12:12 PM YunQiang Su wrote: > > > > > > Adi Kriegisch 于2018年7月9日周一 下午4:34写道： > > > > > > > > Hi! > >

Re: Debian/MIPSeb: proposal to drop mipseb port?

On Mon, Jul 9, 2018 at 12:12 PM YunQiang Su wrote: > > Adi Kriegisch 于2018年7月9日周一 下午4:34写道： > > > > Hi! > > > > > due to lack of enough man power and build machines for 3 mips* port at > > > the same time, I think that now it is time for us to have a talk about > > > dropping mips32eb support

MIPS: PT_GNU_STACK (gcc/binutils)

On Fri, Mar 23, 2018 at 3:19 PM James Cowgill wrote: > > Control: notforwarded -1 > > Hi, > > On 22/03/18 14:28, Michael Biebl wrote: > > Am 22.03.2018 um 12:31 schrieb James Cowgill: > >> I sent a patch upstream (see above). > > > > Thanks! > > Unfortunately I've had to ask for this to be

warning: #warning "Consider adding the right mmap() syscall definitions here!" [-Wcpp]

Source: systemd Version: 238-2 Severity: important User: debian-mips@lists.debian.org Usertags: mips mipsel mipsel64 There seems to be a missing code block to handle mmap/mmap2 on mips/mipsel & mipsel64: % ninja [263/1470] Compiling C object 'src/shared/systemd-shared-238@sta/seccomp-util.c.o'.

Re: as: out of memory allocating 4072 bytes after a total of 546328576 bytes

ing 4072 bytes after a total of 546328576 bytes to as: out of memory allocating 4072 bytes after a total of 557305856 bytes So I would even be tempted to report a bug to gcc/gas... > > Mathieu Malaterre 于2018年11月9日周五 下午5:14写道： > > > > > > Hi mips guru, > > > >

as: out of memory allocating 4072 bytes after a total of 546328576 bytes

Hi mips guru, Could someone please comment on: https://buildd.debian.org/status/fetch.php?pkg=openvdb=mips=5.2.0-1=1541130852=0 Is there a set of flags to use to reduce memory usage on 32bits system ? For reference I am using : --param ggc-min-expand=10 -O1 Thanks much

Re: as: out of memory allocating 4072 bytes after a total of 546328576 bytes

On Thu, Nov 15, 2018 at 8:07 AM Mathieu Malaterre wrote: > > On Wed, Nov 14, 2018 at 3:35 PM YunQiang Su wrote: > > > > YunQiang Su 于2018年11月14日周三 下午10:29写道： > > > > > > With read as(1), I see > > > > > > --reduce-memory-overhead

Re: Bypassing the 2/3/4GB virtual memory space on 32-bit ports

Aurélien, Thanks for caring about 32bits arches ! On Thu, Aug 8, 2019 at 10:39 PM Aurelien Jarno wrote: [...] > mips and mipsel are more affected by the issue as the virtual address > space is limited to 2GB. Therefore on those architectures, this issue > recently started to also affect core

Re: Dropping mips architecture for bullseye and sid

Salut Aurélien ! On Sat, Jul 20, 2019 at 12:47 PM Aurelien Jarno wrote: > > Dear all, > > The mips architecture, supporting 32-bit big-endian MIPS CPUs, has > been supported in Debian for more than 15 years. Due to the limited 2GB > virtual address space and due to the fact this architecture is

openvdb / mips64el

Hi there, For some reason openvdb keep on FTBFS on mips64el (mipsel-osuosl-01): * https://buildd.debian.org/status/logs.php?pkg=openvdb=mips64el The odd thing is that I did change a think in between the experimental and the unstable upload, the experimental package did build fine : 7.0.0-1

Re: Testsuite failure on mips64el, solved with '-fno-inline'

Dear Håvard, On Mon, Dec 6, 2021 at 1:33 PM Håvard Flaget Aasen wrote: > > Hello, > > I've had some issues with the package c-blosc. The testsuite started > to fail on mips64el. I found a solution, adding '-fno-inline' in > CFLAGS in d/rules. > > Does this seem to be a valid solution or, does

Re: MIPS-specific porting issue

Salut Stéphane, On Fri, Dec 3, 2021 at 10:19 AM Stéphane Glondu wrote: > > Dear MIPS porters, > > I am debugging ocaml-mirage-crypto build on mipsel. > > It uses the following code: > > > #if defined (__i386__) || defined (__x86_64__) > > return Val_long (__rdtsc ()); > > #elif defined

Re: Explicitly linking -latomic

Hi Joachim On Sun, Feb 20, 2022 at 7:24 PM Joachim Reichel wrote: > > Dear mips porters, > > I would like to get your input on bug #1005696. Is every C++ program using > supposed to add architecture-specific code to its build system to > link > with -latomic on mipsel? Yes ! (Which

Re: mipsel out-of-memory building dolfinx 0.4.0

On Mon, Jun 13, 2022 at 10:44 AM Drew Parsons wrote: > > On 2022-06-13 10:01, Mathieu Malaterre wrote: > > On Sun, Jun 12, 2022 at 11:38 PM Drew Parsons > > wrote: > >> > >> Hi MIPS porters, I need helping with the build of fenics-dolfinx on >

Re: mipsel out-of-memory building dolfinx 0.4.0

On Sun, Jun 12, 2022 at 11:38 PM Drew Parsons wrote: > > Hi MIPS porters, I need helping with the build of fenics-dolfinx on > mipsel from experimental, > https://salsa.debian.org/science-team/fenics/fenics-dolfinx/-/tree/experimental > > It previously built fine, but the latest version 1:0.4.1

Re: Do you see any chance to fix the "virtual memory exhausted" for nheko on mipsel VM

On Wed, Sep 28, 2022 at 10:06 PM Andreas Tille wrote: > > Hi mips porters, > > in bug #1017752 a > >FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory > > is reported. This remains for the new upstream version I've just > uploaded to experimental[1]. Do you see any chance to

Re: Do you see any chance to fix the "virtual memory exhausted" for nheko on mipsel VM

On Thu, Sep 29, 2022 at 9:14 AM Mathieu Malaterre wrote: > > On Wed, Sep 28, 2022 at 10:06 PM Andreas Tille wrote: > > > > Hi mips porters, > > > > in bug #1017752 a > > > >FTBFS on mipsel: virtual memory exhausted: Cannot allocate memory >

mips: executable-stack-in-shared-library

[cc me please] Dear mips porter, Upstream of one of my package is trying to provide a fix for the lintian report:executable-stack-in-shared-library (*) Basically the patch is as follow (**): [...] if (HWY_ARCH MATCHES "mips") target_link_options(hwy PUBLIC "LINKER:-z,noexecstack") endif

Playing the giveback lotery

[cc me please] Dear mipsel porter(s), Could someone please confirm that all mipsel buildds are pretty much identical ? I am looking for a beefier machine to compile a multimedia specific package that used to be available on that arch ? For reference: *

Re: Bug#1025203: r-cran-glmmtmb: FTBFS on mipsel

On Fri, Dec 9, 2022 at 10:29 AM Andreas Tille wrote: > > Hi Mathieu, > > Am Tue, Dec 06, 2022 at 08:38:43AM +0100 schrieb Mathieu Malaterre: > > I do not have a clean answer to this, but in my experience it is > > getting more and more difficult to compile anything o

Re: Bug#1025203: r-cran-glmmtmb: FTBFS on mipsel

I do not have a clean answer to this, but in my experience it is getting more and more difficult to compile anything on mipsel with g++-12. The default option `-g -O2` seems to imply `take as much memory as you want to get things to compile` so this end up crossing the 2GB hard-limit. For example

Re: The future of mipsel port

On Tue, Jul 18, 2023 at 6:46 AM YunQiang Su wrote: [...] > Known supported hardwares: > MIPS P5600 > Ingenic X2000 > Loongson 3A4000 Could you confirm that MIPS Creator CI20 (Ingenic JZ4780) would not be supported anymore ? Thanks