From: Mark Geisert <mark@maxrnd.com>
To: Cygwin-Apps <cygwin-apps@cygwin.com>
Subject: Re: can't compile coreutils-9.3 any more after upgrade to cygwin-3.4.8
Date: Fri, 1 Sep 2023 23:51:55 -0700 [thread overview]
Message-ID: <41079333-823e-edc6-d8f5-68aa343050bb@maxrnd.com> (raw)
In-Reply-To: <ZPG/DO3WF5FFzU7f@calimero.vinschen.de>
Corinna Vinschen via Cygwin-apps wrote:
> On Sep 1 03:28, Mark Geisert via Cygwin-apps wrote:
>> I then tried recompiling a CPU affinity test program of mine (that uses
>> cpusets) but it could not link due to missing __cpuset_alloc and
>> __cpuset_free. I think this is likely a local issue of mine in copying
>> newly-built stuff into place, though I've automated that process and do it
>> frequently, so... ?
>
> You missed to copy libcygwin.a to /usr/lib.
That's what I thought at first as well. However nm showed the __cpuset_*
functions present in the newly-created libcygwin.a. Did I mis-copy the new lib
somewhere incorrect? Nope. It turned out I had stale files in
/usr/x86_64-pc-cygwin/lib that's evidently earlier in the link search path than
the directory with newest contents.
I just renamed that directory out of the way and now the test program links and
runs without issues. I should investigate what populated that directory though.
I saw that you've applied your two patches. Excellent!
..mark
next prev parent reply other threads:[~2023-09-02 6:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83C27059-CB24-48F5-AC91-AB0622DF82CD@Denis-Excoffier.org>
[not found] ` <aa38a12e-875a-bfaf-6427-2f8d05c0bc47@maxrnd.com>
[not found] ` <ZOh2lNSnYAJmZqUh@calimero.vinschen.de>
[not found] ` <ff004ecd-0bd7-1886-bf81-88daa6b48f2a@maxrnd.com>
[not found] ` <ZOoFxp0yvqK3ZWxX@calimero.vinschen.de>
2023-08-30 7:29 ` Mark Geisert
2023-08-30 9:34 ` Corinna Vinschen
2023-08-30 9:57 ` Corinna Vinschen
2023-08-30 12:17 ` Corinna Vinschen
2023-08-30 18:04 ` Brian Inglis
2023-08-30 18:10 ` Corinna Vinschen
2023-08-31 8:24 ` Corinna Vinschen
2023-09-01 10:28 ` Mark Geisert
2023-09-01 10:38 ` Corinna Vinschen
2023-09-02 6:51 ` Mark Geisert [this message]
2023-08-31 6:54 ` Mark Geisert
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=41079333-823e-edc6-d8f5-68aa343050bb@maxrnd.com \
--to=mark@maxrnd.com \
--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).