From: Kai Tietz <Kai.Tietz@onevision.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sourceware.org,
binutils@sourceware.org
Subject: patch: libiberty pex for _WIN64
Date: Fri, 03 Aug 2007 15:01:00 -0000 [thread overview]
Message-ID: <OFBC37A0BE.2EE7D628-ONC125732C.00517EE3-C125732C.0052837E@onevision.de> (raw)
In-Reply-To: <m3y7gwkoz0.fsf@localhost.localdomain>
Ian,
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.
Cheers,
i.A. Kai Tietz
| (\_/) This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.
------------------------------------------------------------------------------------------
OneVision Software Entwicklungs GmbH & Co. KG
Dr.-Leo-Ritter-Straße 9 - 93049 Regensburg
Tel: +49.(0)941.78004.0 - Fax: +49.(0)941.78004.489 - www.OneVision.com
Commerzbank Regensburg - BLZ 750 400 62 - Konto 6011050
Handelsregister: HRA 6744, Amtsgericht Regensburg
Komplementärin: OneVision Software Entwicklungs Verwaltungs GmbH
Dr.-Leo-Ritter-Straße 9 – 93049 Regensburg
Handelsregister: HRB 8932, Amtsgericht Regensburg - Geschäftsführer:
Ulrike Döhler, Manuela Kluger
next parent reply other threads:[~2007-08-03 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3y7gwkoz0.fsf@localhost.localdomain>
2007-08-03 15:01 ` Kai Tietz [this message]
2007-08-03 15:32 Kai Tietz
2007-08-03 16:03 ` Ian Lance Taylor
2007-08-07 14:18 ` Kai Tietz
2007-08-03 23:16 ` Christopher Faylor
2007-08-04 8:44 ` Eli Zaretskii
2007-08-04 16:35 ` Christopher Faylor
2007-08-06 7:07 ` 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=OFBC37A0BE.2EE7D628-ONC125732C.00517EE3-C125732C.0052837E@onevision.de \
--to=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).