From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: cygport build injecting /usr/lib/gcc/x86_64-pc-cygwin/7.4.0/ paths
Date: Fri, 12 Nov 2021 14:18:55 -0500 [thread overview]
Message-ID: <f5bdb2ab-c057-6b72-3b39-53aa0f5b8a32@cornell.edu> (raw)
In-Reply-To: <9b0f1bad-1fde-1ed0-a454-409be5c97c10@SystematicSw.ab.ca>
On 11/12/2021 12:50 PM, Brian Inglis wrote:
> 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!
> There are no files in the tarball, repo, or build dirs containing 7.4.0
Those paths come from /usr/bin/libtool. There's some discussion of this issue in
https://mingw-users.narkive.com/Mx8FQPRf/libtool-hard-coded-paths ,
which even mentions the ncurses problem. I don't know enough about libtool to
suggest the best solution, but probably others on the list do.
Ken
next prev parent reply other threads:[~2021-11-12 19:19 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 [this message]
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
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=f5bdb2ab-c057-6b72-3b39-53aa0f5b8a32@cornell.edu \
--to=kbrown@cornell.edu \
--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).