all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: failing packages
Date: Sat, 17 Oct 2015 23:40:48 +0300	[thread overview]
Message-ID: <20151017234048.7fbd92b9@debian-netbook> (raw)
In-Reply-To: <20151017195605.GA16011@debian>

[-- Attachment #1: Type: text/plain, Size: 1901 bytes --]

On Sat, 17 Oct 2015 21:56:05 +0200
Andreas Enge <andreas@enge.fr> 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   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  parent reply	other threads:[~2015-10-17 20:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06  9:48 failing packages Efraim Flashner
2015-10-06 11:38 ` Ludovic Courtès
2015-10-06 11:47   ` Pjotr Prins
2015-10-06 12:25 ` Ricardo Wurmus
2015-10-06 12:56   ` Andreas Enge
2015-10-06 15:30   ` Alex Kost
2015-10-06 16:47     ` Ludovic Courtès
     [not found] ` <5613B60C.6050901@uq.edu.au>
2015-10-14 10:41   ` Ben Woodcroft
2015-10-14 13:29     ` Andreas Enge
2015-10-14 13:37       ` Ben Woodcroft
2015-10-14 17:03         ` Efraim Flashner
2015-10-16 20:11 ` Andreas Enge
2015-10-16 21:02   ` Andreas Enge
2015-10-17  8:11     ` Ricardo Wurmus
2015-10-17 16:24       ` Andreas Enge
2015-10-17 10:52     ` Pjotr Prins
2015-10-17 19:56       ` Andreas Enge
2015-10-17 20:04         ` Ricardo Wurmus
2015-10-17 20:34           ` Andreas Enge
2015-10-18  5:32             ` Ricardo Wurmus
2015-10-17 20:37           ` Andreas Enge
2015-10-17 21:01           ` Andreas Enge
2015-10-17 20:40         ` Efraim Flashner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-10-17 11:14 Federico Beffa
2015-10-17 15:20 ` Federico Beffa
2015-10-17 16:18   ` Federico Beffa
2015-10-17 16:21 ` Andreas Enge
2015-10-17 16:33   ` Andreas Enge
2015-10-17 16:45     ` Federico Beffa
2015-10-17 16:53       ` Andreas Enge
2015-10-17 17:55         ` Federico Beffa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151017234048.7fbd92b9@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.