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


Andreas Enge writes:
> bowtie currently fails to build on all three architectures on hydra.
>
> On i686, the error message is:
> Makefile:146: *** bowtie2 compilation requires a 64-bit platform .  Stop.
>
> Surprisingly, the same error message is shown on mip64el (!).
> From its description, I do not expect users to run the program on mips,
> so it might be the safest option to disable the build of these two
> architectures.
>
> On x86_64, the error message is
> g++: error: unrecognized command line option '-stdlib=libstdc++'
> See http://hydra.gnu.org/build/204787 .

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

Whether or not a platform is 64-bit is determined with uname.  Both
these errors relate to using uname.

Is it not available at build time?

I can build the package just fine with:

    guix build -S bowtie
    ...
    guix enviroment --pure bowtie
    make


~~ Ricardo

  reply	other threads:[~2015-01-28 14:12 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 [this message]
2015-01-28 16:57   ` Andreas Enge
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=idjwq476lmt.fsf@bimsb-sys02.mdc-berlin.net \
    --to=ricardo.wurmus@mdc-berlin.de \
    --cc=19708@debbugs.gnu.org \
    --cc=andreas@enge.fr \
    /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).