From: Andrew Schulman <schulman.andrew@epa.gov>
To: cygwin@cygwin.com
Subject: Re: ld randomly assigns wrong user and group IDs to executable
Date: Tue, 26 Apr 2016 19:46:00 -0000 [thread overview]
Message-ID: <imgvhbhlgq3unbgemhdqettdjq5d31v0bm@4ax.com> (raw)
In-Reply-To: <uqmkhb9kmv244kd755urqpunns6qk6gbe2@4ax.com>
> During configure, a particular c++ program compiles fine, but the generated
> executable has the wrong user and group IDs and permissions, so the
> configure test fails and my build fails.
Seems to be a BLODA problem. The problem is inconsistent/intermittent, and
happens only on one of my three Windows hosts. The bad machine has
Symtantec Endpoint Protection running (I can't disable it), and
CYGWIN=detect_bloda also finds C:\windows\system32\privman64.dll, the
"BeyondTrust Power Broker for Windows DLL". Seems a likely suspect.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-04-26 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-22 18:08 Andrew Schulman
2016-04-22 19:28 ` Andrew Schulman
2016-04-26 19:46 ` Andrew Schulman [this message]
2016-04-26 19:50 ` 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=imgvhbhlgq3unbgemhdqettdjq5d31v0bm@4ax.com \
--to=schulman.andrew@epa.gov \
--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).