From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: autotools fails to find /lib/liblz.a
Date: Sat, 31 Oct 2020 13:27:45 -0600 [thread overview]
Message-ID: <bd25f18b-cc4d-aa1b-7afb-13407e51e741@SystematicSw.ab.ca> (raw)
In-Reply-To: <87sg9ux2l6.fsf@Otto.invalid>
On 2020-10-31 01:43, ASSI wrote:
> Brian Inglis writes:
>> I have now put the packages up on Google Drive for review in another post.
>
> Can you leave that Google stuff out here please?
That is my only online shared storage available, as my cableco ISP decided there
was little customer demand for any, like they decided there was little customer
demand for Usenet News feeds, and may yet decide there is little demand for
their email services!
> 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.
It runs Cygwin services and I work under X with PCmanFM, etc.
If PATH ever becomes a problem, I save it and shorten it.
I run a number of customizations that trips up poorly written code that makes
unjustified assumptions.
A lot of what you see is from a log sanitizing script I keep adding to: builds
are actually under Cygwin /home/$USER/src/cygwin/$PKG/ or /home/$USER/src/$PKG/
for packages from other sources.
Is there a good and easy way to run multiple term windows from separate
instances while sharing the infrastructure to consolidate maintenance?
The Cygwin Setup program has an annoying habit of breaking or deleting certain
high level symlinks and converting them into directories! ;^>
Ideally I should run 4 extra instances to separate package builds and
newlib-winsup builds on both arches.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-10-31 19:27 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 [this message]
2020-10-31 21:52 ` Achim Gratz
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=bd25f18b-cc4d-aa1b-7afb-13407e51e741@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).