autotools fails to find /lib/liblz.a

[Achim Gratz]

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