Hello, With regards to the FTBFS below, is Debian mipsel always 64 bit, always 32 bit, or a mix?
How would I test that? Thanks! ---------- Forwarded message --------- From: Andreas Tille <andr...@an3as.eu> Date: Wed, May 27, 2015, 10:09 Subject: Re: [nore...@buildd.debian.org: failed mipsel build of parafly 0.0.2013.01.21-1] To: Michael R. Crusoe <mcru...@msu.edu> Cc: Debian Med Packaging Team <debian-med-packag...@lists.alioth.debian.org> Hi Michael, On Wed, May 27, 2015 at 01:37:30PM +0000, Michael R. Crusoe wrote: > I interpret '-m64' as a signal that the developer only supports 64 bit > OSes/hardware. From what I can find, mipsel can be 32 or 64bit. So I would > suggest removing mipsel from the supported architecture series. > > Does that make sense? Not really since it also fails on arm64 with the same error. I have learned that there are upstream authors out there who are adding options according "good feeling" (no idea whether parafly authors belong to this group). I'd recommend asking on debian-mentors@lists.debian.org since I'm not an expert in this myself. Kind regards Andreas. > On Wed, May 27, 2015 at 8:36 AM Andreas Tille <andr...@an3as.eu> wrote: > > > Hi Michael, > > > > perhaps simply droping the option -m64 would solve this (same for > > arm64). I vaguely remember that it is redundant for all architectures > > but please double check this. > > > > Kind regards > > > > Andreas. > > > > ----- Forwarded message from Debian buildds <nore...@buildd.debian.org> > > ----- > > > > Date: Wed, 27 May 2015 09:45:01 +0000 > > From: Debian buildds <nore...@buildd.debian.org> > > To: para...@packages.qa.debian.org > > Subject: failed mipsel build of parafly 0.0.2013.01.21-1 > > > > * Source package: parafly > > * Version: 0.0.2013.01.21-1 > > * Architecture: mipsel > > * State: failed > > * Suite: sid > > * Builder: mayer.debian.org > > * Build log: > > https://buildd.debian.org/fetch.cgi?pkg=parafly&arch=mipsel&ver=0.0.2013.01.21-1&stamp=1432719507&file=log > > > > Please note that these notifications do not necessarily mean bug reports > > in your package but could also be caused by other packages, temporary > > uninstallabilities and arch-specific breakages. A look at the build log > > despite this disclaimer would be appreciated however. > > > > > > > > > > ----- End forwarded message ----- > > > > -- > > http://fam-tille.de > > -- http://fam-tille.de