From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: [Bug] setup.exe
Date: Sun, 17 Nov 2013 18:07:00 -0000 [thread overview]
Message-ID: <87k3g6x5pg.fsf@Rainer.invalid> (raw)
No good deed goes unpunished… the latest changes to setup.exe to use the
UNC path interfaces break set_cout. This function is only used in
unattended mode and when the help option is used and setup.exe works
correctly when this function does not get called.
The reason for the breakage is the special filename "conout$" that is
used to attach to the console output handle and the override to fopen
that then treats it like any other file name and makes a UNC path
"\\?\conout$" from it. If I remove the override for fopen, things are
working again, but I can't find how to specify "conout$" via a UNC path
and simply setting the string back to "conout$" in the attr structure in
gdb didn't work, either.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptation for Waldorf microQ V2.22R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next reply other threads:[~2013-11-17 18:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 18:07 Achim Gratz [this message]
2013-11-18 10:06 ` Corinna Vinschen
2013-11-18 19:51 ` 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=87k3g6x5pg.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).