From: Jon Turney <jon.turney@dronecode.org.uk>
To: cygwin-developers@cygwin.com
Subject: Re: Small problem building cygserver from source
Date: Sun, 27 Jun 2021 12:38:22 +0100 [thread overview]
Message-ID: <d76ad0e9-3ea8-b2d8-d6b1-9bcbd4cfb823@dronecode.org.uk> (raw)
In-Reply-To: <d248a3e0-59a5-d04d-b5cc-d00623423ae8@maxrnd.com>
On 27/06/2021 09:01, Mark Geisert wrote:
> Jon Turney wrote:
>> On 24/06/2021 08:10, Mark Geisert wrote:
>>> Hi folks,
>>> I'm seeing this build problem while building the whole Cygwin ball of
>>> wax for local testing...
>>>
>>> Making all in cygserver
>>> make[3]: Entering directory
>>> '/c/staging/newlib-cygwin/build/x86_64-pc-cygwin/winsup/cygserver'
>>> CXXLD cygserver.exe
>>> /usr/lib/gcc/x86_64-pc-cygwin/10/../../../../x86_64-pc-cygwin/bin/ld:
>>> /usr/lib/w32api/libadvapi32.a(daltbs00499.o):(.idata$5+0x0): multiple
>>> definition of `__imp_LsaStorePrivateData';
>>> /oss/build/x86_64-pc-cygwin/winsup/cygwin/libcygwin.a(d000097.o):(.idata$5+0x0):
>>> first defined here
>>> /usr/lib/gcc/x86_64-pc-cygwin/10/../../../../x86_64-pc-cygwin/bin/ld:
>>> /usr/lib/w32api/libadvapi32.a(daltbs00471.o):(.idata$5+0x0): multiple
>>> definition of `__imp_LsaOpenPolicy';
>>> /oss/build/x86_64-pc-cygwin/winsup/cygwin/libcygwin.a(d000093.o):(.idata$5+0x0):
>>> first defined here
>>> /usr/lib/gcc/x86_64-pc-cygwin/10/../../../../x86_64-pc-cygwin/bin/ld:
>>> /usr/lib/w32api/libadvapi32.a(daltbs00437.o):(.idata$5+0x0): multiple
>>> definition of `__imp_LsaClose';
>>> /oss/build/x86_64-pc-cygwin/winsup/cygwin/libcygwin.a(d000084.o):(.idata$5+0x0):
>>> first defined here
>>> collect2: error: ld returned 1 exit status
>>> make[3]: *** [Makefile:534: cygserver.exe] Error 1
>>>
>>> I was not able to determine why libadvapi32.a is apparently being
>>> pulled in here or what was doing that.
>>
>> Not reproducible in CI or locally.
>>
>> You might need to do a clean and/or use a fresh build directory if you
>> haven't rebuilt successfully since the automakification changes.
>
> I did a 'git pull' then configure + make just to be sure I'm up to
> date. Errors still occur. Hmm. I suppose it's some local issue then.
>
> I read the error msgs as double defs of imports in w32api/libadvapi32.a
> vs libcygwin.a. I don't understand why the linker cares. Is it that
> there are no defs of the corresponding Lsa* functions among the linker
No, remember that import stubs are statically linked.
I'm pretty sure there shouldn't be a definition of _imp_Lsa* in
libcygwin.a at all, since the only import stubs it should be providing
are for the cygwin.dll.
prev parent reply other threads:[~2021-06-27 11:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 7:10 Mark Geisert
2021-06-26 14:27 ` Jon Turney
2021-06-27 8:01 ` Mark Geisert
2021-06-27 11:38 ` Jon Turney [this message]
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=d76ad0e9-3ea8-b2d8-d6b1-9bcbd4cfb823@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin-developers@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).