unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: 19708@debbugs.gnu.org
Subject: bug#19708: Bowtie fails to build
Date: Wed, 28 Jan 2015 17:57:35 +0100	[thread overview]
Message-ID: <20150128165735.GA14986@debian.math.u-bordeaux1.fr> (raw)
In-Reply-To: <idjwq476lmt.fsf@bimsb-sys02.mdc-berlin.net>

On Wed, Jan 28, 2015 at 03:11:06PM +0100, Ricardo Wurmus wrote:
> Whether or not a platform is 64-bit is determined with uname.  Both
> these errors relate to using uname.

Clearly, only x86_64 is supported. Citing from Makefile:
BITS=32
ifeq (x86_64,$(shell uname -m))
        BITS=64
endif
# msys will always be 32 bit so look at the cpu arch instead.
ifneq (,$(findstring AMD64,$(PROCESSOR_ARCHITEW6432)))
        ifeq (1,$(MINGW))
                BITS=64
        endif
endif
ifeq (32,$(BITS))
  $(error bowtie2 compilation requires a 64-bit platform )
endif

So we should disable mips and i686.


> This is odd.  The Makefile only adds this option on MacOS:
>     MACOS = 0
>     ifneq (,$(findstring Darwin,$(shell uname)))
>             MACOS = 1
>             ifneq (,$(findstring 13,$(shell uname -r)))
>                     CPP = clang++
>                     CC = clang
>                     EXTRA_FLAGS += -stdlib=libstdc++
>             endif
>     endif

I see the following in my Makefile:
MACOS = 0
ifneq (,$(findstring Darwin,$(shell uname)))
        MACOS = 1
endif

ifneq (,$(findstring 13,$(shell uname -r)))
        CPP = clang++
        CC = clang
        EXTRA_FLAGS += -stdlib=libstdc++
endif

Notice the different placements of the "endif". Are we talking about different
versions of bowtie? I looked at the top Makefile from the result of
"guix build bowtie -S".

Andreas

  reply	other threads:[~2015-01-28 16:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-27 21:47 bug#19708: Bowtie fails to build Andreas Enge
2015-01-28 14:11 ` Ricardo Wurmus
2015-01-28 16:57   ` Andreas Enge [this message]
2015-01-29 10:01     ` Ricardo Wurmus
2015-01-30 16:07       ` Mark H Weaver

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=20150128165735.GA14986@debian.math.u-bordeaux1.fr \
    --to=andreas@enge.fr \
    --cc=19708@debbugs.gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).