From: Jay <jay.krell@cornell.edu>
To: Daniel Kasak <d.j.kasak.dk@gmail.com>
Cc: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Re: Disable CPU detection
Date: Sun, 17 May 2015 21:15:00 -0000 [thread overview]
Message-ID: <A9940D6E-E9EB-4577-A137-08F538E884E8@gmail.com> (raw)
In-Reply-To: <CAF73Y=TF76Fe_skOnrQ3=w9J4_cQiUwxu7dgLsBo3L644zK7xQ@mail.gmail.com>
Can you set CFLAGS to empty or other at the start?
CFLAGS=... configure ...
This aspect of autoconf and such has always bothered me, as if every specific machine builds its own very specific binaries. But some amount of sniffing machine is useful.
- Jay
On May 16, 2015, at 8:47 PM, Daniel Kasak <d.j.kasak.dk@gmail.com> wrote:
> Hi all.
>
> I'm building some libraries for distribution on Windows ( shudder ),
> using a Windows 7 VM. I see that the configure script for libffi
> detects my CPU ( Opteron ) and sets up CFLAGS to match. Is there an
> easy way of disabling this detection so I can safely redistribute to
> people who don't have Opterons? For now, I've grepped for the
> offending -march entries and manually edited then out ...
>
> Thanks :)
>
> Dan
prev parent reply other threads:[~2015-05-17 21:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-17 3:47 Daniel Kasak
2015-05-17 21:15 ` Jay [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=A9940D6E-E9EB-4577-A137-08F538E884E8@gmail.com \
--to=jay.krell@cornell.edu \
--cc=d.j.kasak.dk@gmail.com \
--cc=libffi-discuss@sourceware.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).