From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: cygport: distinguish between x86 and x86_64
Date: Wed, 24 Aug 2016 17:22:00 -0000 [thread overview]
Message-ID: <87lgzmoze7.fsf@Rainer.invalid> (raw)
In-Reply-To: <20160824083323.GA26058@calimero.vinschen.de> (Corinna Vinschen's message of "Wed, 24 Aug 2016 10:33:23 +0200")
Corinna Vinschen writes:
>> What is the official way to conditionalize .cygport files for
>> differences in x86 and x86_64 architectures ?
>
> "${ARCH}" is either "i686" or "x86_64"
For tests in the cygport file it is usually easier to use the ARCH_i686
or ARCH_x86_64 variables.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
prev parent reply other threads:[~2016-08-24 17:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 8:09 Dr. Volker Zell
2016-08-24 8:33 ` Corinna Vinschen
2016-08-24 17:22 ` Achim Gratz [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=87lgzmoze7.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@cygwin.com \
/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).