From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: autotools fails to find /lib/liblz.a
Date: Sat, 31 Oct 2020 22:52:23 +0100 [thread overview]
Message-ID: <87r1pef4h4.fsf@Rainer.invalid> (raw)
In-Reply-To: <bd25f18b-cc4d-aa1b-7afb-13407e51e741@SystematicSw.ab.ca> (Brian Inglis's message of "Sat, 31 Oct 2020 13:27:45 -0600")
Brian Inglis writes:
>> Looking at the logs in your issue report… please cut all the extra
>> nonsense from your PATH when building Cygwin packages. At best it just
>> slows things down further. Also, I wouldn't recommend to build in $HOME
>> if you can help it, Windows likes to "protect" files there. Last but
>> not least, since this is obviously a machine that you use for other
>> things you might want to separate the Cygwin instance you are typically
>> using from the two you are building with.
>
> What's set up in my profile has been added to since SunOS, Solaris, AIX, etc.
> days across many systems including corps' Windows systems running (DJGPP then)
> Cygwin, with customizations and variations by SHELL, TYPE, and HOST, running
> integrated, interoperable tool sets, across VMs, local, and remote systems at
> times.
[…]
That is all fine for your daily work, I'd just not pollute the build
environment with it.
> Is there a good and easy way to run multiple term windows from separate
> instances while sharing the infrastructure to consolidate maintenance?
I typically run an SSH daemon on each instance (on separate ports of
course) and remotely work over SSH more or less exclusively. From Linux
I just use multiple tabs in konsole, from MinTTY I usually work in tmux.
It's easy enough to create MinTTY shortcuts for each instance of Cygwin
if you'd rather go that route. As long as these reside on the same
machine or share a filesystem it's not much of a problem to share things
you want to share (via fstab and nsswitch.conf). But the build
instances I use with a dedicated account (that shares its setup between
the two architectures).
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
DIY Stuff:
http://Synth.Stromeko.net/DIY.html
prev parent reply other threads:[~2020-10-31 21:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 18:24 Brian Inglis
2020-10-30 19:32 ` Achim Gratz
2020-10-30 19:42 ` Ken Brown
2020-10-30 20:05 ` Brian Inglis
2020-10-30 19:57 ` Brian Inglis
2020-10-30 21:03 ` Achim Gratz
2020-10-30 21:51 ` Brian Inglis
2020-10-31 7:43 ` ASSI
2020-10-31 19:27 ` Brian Inglis
2020-10-31 21:52 ` 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=87r1pef4h4.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).