From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, pmuldoon@redhat.com
Subject: Re: [PATCH 4/4] compile: Add 'set compile-gcc'
Date: Fri, 24 Apr 2015 06:19:00 -0000 [thread overview]
Message-ID: <20150424061944.GA1796@host1.jankratochvil.net> (raw)
In-Reply-To: <83h9s6yrsz.fsf@gnu.org>
On Fri, 24 Apr 2015 08:16:28 +0200, Eli Zaretskii wrote:
> > I do not think it would work on MS-Windows host as gcc/libcc1/ uses:
> > # If any of these functions are missing, simply don't bother building
> > # this plugin.
> > GCC_ENABLE_PLUGINS
> > AC_CHECK_FUNC(socketpair, , enable_plugin=no)
> > AC_CHECK_FUNC(select, , enable_plugin=no)
> > AC_CHECK_FUNC(fork, , enable_plugin=no)
> > AM_CONDITIONAL(ENABLE_PLUGIN, test $enable_plugin = yes)
>
> You underestimate the hacker power ;-) Trust me, soon enough this
> will work on Windows, and these conditions will then change. So I
> still think we should qualify the above logic by saying that it is
> specific to Posix systems.
Yes, I have changed the text so in the updated patch.
Jan
next prev parent reply other threads:[~2015-04-24 6:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 21:36 [PATCH 1/4] compile: Use libcc1.so->libcc1.so.0 Jan Kratochvil
2015-04-21 21:36 ` [PATCH 3/4] compile: set debug compile: Display GCC driver filename Jan Kratochvil
2015-04-23 20:40 ` cancel: " Jan Kratochvil
2015-04-21 21:36 ` [PATCH 2/4] compile: Use libcc1.so.0->libcc1.so.1 Jan Kratochvil
2015-04-23 20:40 ` cancel: " Jan Kratochvil
2015-04-21 21:37 ` [PATCH 4/4] compile: Add 'set compile-gcc' Jan Kratochvil
2015-04-22 7:21 ` Eli Zaretskii
2015-04-23 21:09 ` Jan Kratochvil
2015-04-24 6:16 ` Eli Zaretskii
2015-04-24 6:19 ` Jan Kratochvil [this message]
2015-04-23 20:40 ` cancel: " Jan Kratochvil
2015-04-23 20:40 ` cancel: [PATCH 1/4] compile: Use libcc1.so->libcc1.so.0 Jan Kratochvil
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=20150424061944.GA1796@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pmuldoon@redhat.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