From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
Date: Sun, 14 Nov 2021 13:48:55 +0100 [thread overview]
Message-ID: <87o86m9a2w.fsf@Rainer.invalid> (raw)
In-Reply-To: <9b0f1bad-1fde-1ed0-a454-409be5c97c10@SystematicSw.ab.ca> (Brian Inglis's message of "Fri, 12 Nov 2021 10:50:41 -0700")
Brian Inglis writes:
> Got these errors trying to build latest ncurses on my system, so
> retried on scallywag and got same result, with no clue where that is
> coming from!
Unless there is absolutely no other way and you know exactly what you're
doing, never skip the cygautoreconf in src_compile.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf rackAttack V1.04R1:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2021-11-14 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-12 17:50 Brian Inglis
2021-11-12 18:50 ` Duncan Roe
2021-11-12 19:18 ` Ken Brown
2021-11-12 20:25 ` Brian Inglis
2021-11-12 23:42 ` Duncan Roe
2021-11-14 14:18 ` Brian Inglis
2021-11-14 12:48 ` Achim Gratz [this message]
2021-11-14 13:49 ` Brian Inglis
2021-11-14 22:07 ` Brian Inglis
2021-11-15 13:09 ` Achim Gratz
2021-11-16 5:24 ` Brian Inglis
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=87o86m9a2w.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).