Re: failing packages

[Efraim Flashner]

On Sat, 17 Oct 2015 21:56:05 +0200
Andreas Enge <address@hidden> wrote:

> On Sat, Oct 17, 2015 at 12:52:53PM +0200, Pjotr Prins wrote:
> > Anything bioinformatics is not really used on non Intel architectures.
> > It may change later but, yes, defaulting to x86_64 is the quick option
> > for failing packages. I prefer we change them that way.  
> 
> How about ngs-sdk, which fails on armhf with the slightly surprising error
> message:
> Configuring NGS-SDK package
> checking system type... Linux
> checking machine architecture... armv7l
> configure: error: unsupported architecture 'Linux'
> (and similarly on mips).
 
I checked the source over at github
(https://github.com/ncbi/ngs/blob/master/ngs-sdk/setup/konfigure.perl), and in
the configure script is (at line 205):

print "checking machine architecture... " unless ($AUTORUN);
println $MARCH unless ($AUTORUN);
unless ($MARCH =~ /x86_64/i || $MARCH =~ /i?86/i) {
    println "configure: error: unsupported architecture '$OSTYPE'";
    exit 1;
}

and then at 292:

print "checking for supported architecture... " unless ($AUTORUN);

my $BITS;

if ($MARCH =~ /x86_64/i) {
    $BITS = 64;
} elsif ($MARCH eq 'fat86') {
    $BITS = '32_64';
} elsif ($MARCH =~ /i?86/i) {
    $BITS = 32;
} else {
    die "unrecognized Architecture '$ARCH'";
}
println "$MARCH ($BITS bits) is supported" unless ($AUTORUN);

so it looks like x86_64 and i686 are pretty much hardcoded in.

> Is it okay to take out mips and arm from the supported architectures?

I'm curious if they would build with modifications to the configure files,
but I don't have a machine to test it on.

> Andreas
> 

-- 
Efraim Flashner   <address@hidden>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

pgpdZNDG4q79U.pgp
Description: OpenPGP digital signature