From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: Ian Lance Taylor <iant@google.com>,
gdb-patches@sourceware.org, binutils@sourceware.org,
gcc-patches@gcc.gnu.org, Kai Tietz <Kai.Tietz@onevision.com>
Subject: Re: patch: libiberty pex for _WIN64
Date: Fri, 03 Aug 2007 23:16:00 -0000 [thread overview]
Message-ID: <20070803231642.GC11438@ednor.casa.cgf.cx> (raw)
In-Reply-To: <OFA3E07890.9C33ABB6-ONC125732C.005538AD-C125732C.00554DE4@onevision.de>
On Fri, Aug 03, 2007 at 05:31:39PM +0200, Kai Tietz wrote:
>Ian,
>
>Sorry, I missed to attach the patch 8)
>
>I prepared a patch for pex using pid_t instead of the type 'long' for
>system handles. This is necessary for _WIN64, because the long type isn't
>wide enougth to hold a pointer for this ABI The type pid_t is always
>defined by the configure in config.h if not defined by the header-set.
>Therefore it seems to be the best way to make this run.
>
>ChangeLog:
>
>2007-08-03 Kai Tietz <kai.tietz@onevision.com>
>
> * pex-common.h: (pex_funcs): Retyped wait and exec_child to pid_t.
> * pex-djgpp.c: Likewise.
> * pex-msdos.c: Likewise.
> * pex-unix.c: Likewise.
> * pex-win32.c: Likewise.
If long isn't long enough what is pid_t defined to be on _WIN64?
cgf
next prev parent reply other threads:[~2007-08-03 23:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 15:32 Kai Tietz
2007-08-03 16:02 ` Ian Lance Taylor
2007-08-07 14:18 ` Kai Tietz
2007-08-03 23:16 ` Christopher Faylor [this message]
2007-08-04 8:44 ` Eli Zaretskii
2007-08-04 16:35 ` Christopher Faylor
2007-08-06 7:07 ` Kai Tietz
-- strict thread matches above, loose matches on Subject: below --
2007-08-01 1:45 PING: Re: patch: libiberty adjustments " Ian Lance Taylor
2007-08-03 15:01 ` patch: libiberty pex " Kai Tietz
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=20070803231642.GC11438@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--cc=Kai.Tietz@onevision.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=iant@google.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).