all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Build C++ cross-compiler by default.
Date: Wed, 13 Jan 2016 21:52:14 +0100	[thread overview]
Message-ID: <87fuy12oe9.fsf@gnu.org> (raw)
In-Reply-To: <8760z03q9v.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 11 Jan 2016 19:49:32 +0100")

Ricardo Wurmus <rekado@elephly.net> skribis:

> the configure flags defined in “cross-gcc-arguments” disabled the C++
> compiler to prevent an error that happens when building libstdc++-v3.
> Since I needed a C++ cross-compiler for ARM I added “c++” to the list of
> enabled languages and added the configure flag
> “--disable-libstdc++-v3”.  This is now the same as what is done in
> “gcc-boot0” in “commencement.scm”.

Cool.

> Will this cause a rebuild of every package on ARM?  Is it okay to push
> this to core-updates?

AFAICS, this causes a rebuild of the cross-compilation infrastructure
only (for Hydra, that’s several times GCC plus a bunch of packages that
we cross-build to make sure the basic functionality is alright.)

So it could even go to ‘master’, but since Hydra is now building all of
‘core-updates’, it’s more energy-efficient to push it to ‘core-updates’
as well.

> From 021febc7f7f35ccffe381af798e0b20d7687c94e Mon Sep 17 00:00:00 2001
> From: Ricardo Wurmus <rekado@elephly.net>
> Date: Mon, 11 Jan 2016 19:43:25 +0100
> Subject: [PATCH] gnu: cross-gcc-arguments: Enable C++, disable building of
>  libstdc++-v3.
>
> * gnu/packages/cross-base.scm (cross-gcc-arguments)[arguments]: Disable
>   building libstdc++-v3 and enable building C++ compiler.

LGTM!

Thanks,
Ludo’.

      reply	other threads:[~2016-01-13 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-11 18:49 [PATCH] Build C++ cross-compiler by default Ricardo Wurmus
2016-01-13 20:52 ` Ludovic Courtès [this message]

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=87fuy12oe9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.