From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: gcc / gfortran 5.x
Date: Mon, 27 Nov 2017 20:30:00 -0000 [thread overview]
Message-ID: <87374zwjlx.fsf@Rainer.invalid> (raw)
In-Reply-To: <038a3376-cdd4-6f4e-ded8-7ea65fdb75bd@molconn.com> (LMH's message of "Mon, 27 Nov 2017 15:11:19 -0500")
LMH writes:
> You can have as many cygwin installations on your system as you want, just name the
> root folder and install folder something different for each one. There are potential
> problems if you try to run more than one version at the same time.
As long as they don't see each other via PATH or try to run daemons on
the same port you'll have no trouble running them all in parallel.
> I start the older cygwin terminals using a .bat file that configures the /cygwin/bin
> PATH environment variable for the version of cygwin I are running.
Well, I'd rather suggest to modify system settings and create a system
or user variable CYGWIN_NOWINPATH=1. That keeps the Windows PATH out of
Cygwin entirely, if you need to graft something back that you need, you
can do that in Cygwin by inspecting $ORIGINAL_PATH. Provide a shortcut
to mintty in each of your Cygwin installations that uses the respective
installation directory as the CWD and have it start a login shell; you
need to use an absolute path, so '/usr/bin/bash -l'. You might want to
give each shortcut a different foreground/background color in mintty so
you can tell them apart more easily.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2017-11-27 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 5:52 Hans Horn
2017-11-27 6:47 ` Yaakov Selkowitz
2017-11-27 19:29 ` Keith Christian
2017-11-27 20:09 ` Marco Atzeri
2017-11-27 20:11 ` LMH
2017-11-27 20:30 ` Achim Gratz [this message]
2017-11-27 20:58 ` Achim Gratz
2017-12-04 16:05 ` Hans Horn
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=87374zwjlx.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin@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).