public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: nobodyO@web.de
To: cygwin@cygwin.com
Subject: Aw: Re: Strange errors with gcc and top, even after rebaseall
Date: Sat, 26 Aug 2017 21:51:00 -0000	[thread overview]
Message-ID: <trinity-7b987106-f557-41b8-870b-b254245f3676-1503784312569@3c-app-webde-bap64> (raw)
In-Reply-To: <877exqtfmn.fsf@Rainer.invalid>

Hi,

> I guess I don't understand why you thoink you'd need two installations
> for two build environments. 
 
I have installed one Cygwin installation package from department A, for
building software a, and another from department B and which has some
tools which were developed here, for building software b.
 
Regards,

Rolf

Gesendet: Samstag, 26. August 2017 um 17:15 Uhr
Von: "Achim Gratz" <Stromeko@nexgo.de>
An: cygwin@cygwin.com
Betreff: Re: Strange errors with gcc and top, even after rebaseall
nobodyO@web.de writes:
> ok, then i need at work two 32bit versions, one for building software
> A and one for software B, and a 64bit version for working with Cygwin,
> e. g. locate, backups etc..

I guess I don't understand why you thoink you'd need two installations
for two build environments.

> For switching between the versions i use
> moving (renaming) the directories of the other versions and replacing
> them with junction points to the active version.

You do what?

> Is there a better way for switching?

Yes, how about not switching at all? As long as you keep the PATH clean
so that these installations don't see each other there is no problem
having multiple versions of Cygwin active on the same machine. If you
have daemons running then of course you need to set them up to use
different ports on each instance as well.


Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

--
Problem reports: http://cygwin.com/problems.html[http://cygwin.com/problems.html]
FAQ: http://cygwin.com/faq/[http://cygwin.com/faq/]
Documentation: http://cygwin.com/docs.html[http://cygwin.com/docs.html]
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple[http://cygwin.com/ml/#unsubscribe-simple]
 

--
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

  reply	other threads:[~2017-08-26 21:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-23 21:39 nobodyO
2017-08-24  2:16 ` cyg Simple
2017-08-24  7:16   ` Aw: " nobodyO
2017-08-24 11:16     ` Eliot Moss
2017-08-25 19:07       ` nobodyO
2017-08-26  3:50         ` Andrey Repin
2017-08-26 17:16         ` Achim Gratz
2017-08-26 21:51           ` nobodyO [this message]
2017-08-27 13:43             ` Aw: " cyg Simple
2017-08-29  2:49       ` Kaz Kylheku

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=trinity-7b987106-f557-41b8-870b-b254245f3676-1503784312569@3c-app-webde-bap64 \
    --to=nobodyo@web.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).