From: Vincent Legoll <vincent.legoll@gmail.com>
To: Charles Direg <carloshujara@gmail.com>, help-guix <help-guix@gnu.org>
Subject: Re: How to compile native?
Date: Wed, 14 Apr 2021 20:45:31 +0200 [thread overview]
Message-ID: <CAEwRq=r7P_PEJDmSe3r2mB+OS+8zLF=Z-of+TwVxX6H4zTB2Mg@mail.gmail.com> (raw)
In-Reply-To: <87v98o90pv.fsf@dismail.de>
Hello,
On Wed, Apr 14, 2021 at 8:32 PM Joshua Branson <jbranso@dismail.de> wrote:
>
> Charles Direg <carloshujara@gmail.com> writes:
>
> > Hi,
> >
> > How can I do a compilation of the packages natively?
>
> Yes this is possible! You can disable substitutes to compile all
> packages natively.
I think Charles meant compilation optimized for his actual processor
instead of being compatible with all x86_64. Like with the following
CFLAGS:
> > What I mean is that, for example in Gentoo it can be used inside
> > /etc/portage/make.conf: CFLAGS="-O2 -march=native -mtune=native"
I think there's no use of giving "-mtune" when you have "-march", c.f.:
https://gcc.gnu.org/onlinedocs/gcc/x86-Options.html#index-march-14
> > Is that possible in guix?
I've heard it is, but not seen the recipe.
> Currently guix does not support gentoo style flags..yet. Though there
> are talks to do something like that.
Gentoo use flags are something different, used to disable things in
packages.
> If you wanted to compile packages
> with specific compile flags, then you'll need to make custom package
> definitions.
That's probably what Charles wants, but in a global way, settings CFLAGS once
for the whole distro.
--
Vincent Legoll
next prev parent reply other threads:[~2021-04-14 18:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 23:10 How to compile native? Charles Direg
2021-04-14 18:31 ` Joshua Branson
2021-04-14 18:45 ` Vincent Legoll [this message]
2021-04-14 19:18 ` Xinglu Chen
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='CAEwRq=r7P_PEJDmSe3r2mB+OS+8zLF=Z-of+TwVxX6H4zTB2Mg@mail.gmail.com' \
--to=vincent.legoll@gmail.com \
--cc=carloshujara@gmail.com \
--cc=help-guix@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.
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).