From: Efraim Flashner <efraim@flashner.co.il>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: guix-devel@gnu.org
Subject: Re: 05/06: gnu: rust: Don't build for "native" arch on ARM.
Date: Tue, 17 Apr 2018 10:45:33 +0300 [thread overview]
Message-ID: <20180417074533.GG30951@macbook41> (raw)
In-Reply-To: <20180417091712.48219a77@scratchpost.org>
[-- Attachment #1: Type: text/plain, Size: 1138 bytes --]
On Tue, Apr 17, 2018 at 09:17:12AM +0200, Danny Milosavljevic wrote:
> Hi Mark,
>
> On Mon, 16 Apr 2018 16:05:04 -0400
> Mark H Weaver <mhw@netris.org> wrote:
>
> > If it would be beneficial, you might consider using gcc-7 to compile
> > 'rust', by adding 'gcc-7' to native-inputs. We're already using gcc-7
> > to compile a few other packages, including linux-libre on x86_64.
>
> Yeah, it would be possible.
>
<snip>
>
> Also, AFAIK "-march=native" autodetects the CPU in the build machine
> and then optimizes for exactly that CPU. Arguably that's not what
> we want in general.
This was my original intent with commenting out the '-march=native', it
just seemed that it cropped up as a build error more often with arm*
processors.
As far as aarch64 goes, it doesn't build fully in either case, but the
error I experienced with '-march=native' is gone when I add gcc-7 as a
native-input.
--
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: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-17 7:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180416175951.28242.65069@vcs0.savannah.gnu.org>
[not found] ` <20180416175952.9458420373@vcs0.savannah.gnu.org>
2018-04-16 20:05 ` 05/06: gnu: rust: Don't build for "native" arch on ARM Mark H Weaver
2018-04-17 7:17 ` Danny Milosavljevic
2018-04-17 7:45 ` Efraim Flashner [this message]
2018-04-17 20:49 ` Joshua Branson
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=20180417074533.GG30951@macbook41 \
--to=efraim@flashner.co.il \
--cc=dannym@scratchpost.org \
--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 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).