From: Daniel Jacobowitz <drow@false.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: php compilation fix
Date: Tue, 8 Aug 2000 18:48:21 -0700 [thread overview]
Message-ID: <20000808184821.A20816@drow.them.org> (raw)
In-Reply-To: <00080818110803.04184@localhost.localdomain>; from mpeters@omnilinux.com on Tue, Aug 08, 2000 at 05:29:19PM -0700
On Tue, Aug 08, 2000 at 05:29:19PM -0700, Michael A. Peters wrote:
>
> I created a patch that makes the changes suggest to php-4.0.1pl2/main/main.c
>
> replace
> args = orig_args;
> by:
> memcpy(args, orig_args, sizeof(orig_args));
I suspect you're looking for va_copy().
Dan
/--------------------------------\ /--------------------------------\
| Daniel Jacobowitz |__| SCS Class of 2002 |
| Debian GNU/Linux Developer __ Carnegie Mellon University |
| dan@debian.org | | dmj+@andrew.cmu.edu |
\--------------------------------/ \--------------------------------/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-08-09 1:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-09 0:29 php compilation fix Michael A. Peters
2000-08-09 1:48 ` Daniel Jacobowitz [this message]
2000-08-09 5:45 ` Edwin Tam
2000-08-09 15:16 ` David Edelsohn
2000-08-09 17:38 ` Michael A. Peters
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=20000808184821.A20816@drow.them.org \
--to=drow@false.org \
--cc=linuxppc-dev@lists.linuxppc.org \
/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 NNTP newsgroup(s).