From: Keith Seitz <keiths@redhat.com>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: insight <insight@sourceware.org>
Subject: Re: [tcl] Undefined NULL in tcl/compat/strstr.c
Date: Wed, 23 Apr 2008 18:10:00 -0000 [thread overview]
Message-ID: <480F7A05.4050005@redhat.com> (raw)
In-Reply-To: <EE8EE936-F2AD-41D0-9C29-5DB98D3AE80C@monami-software.com>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
[Moving to correct list]
Masaki Muranaka wrote:
> Hello,
>
> This is obvious. Could anyone commit my patch?
>
>
> 2008-04-24 Masaki Muranaka <monaka@monami-software.com>
>
> * compat/strstr.c : Add include stddef.h to get NULL define.
Having seen this patch, I took a peek at what the upstream Tcl group has
done. They've taken a slightly different tack, which I have committed:
tcl/ChangeLog
2008-04-23 Keith Seitz <keiths@redhat.com>
Based on patch from Masaki Muranaka <monaka@monami-software.com>:
* compat/strstr.c: Include tcl.h and define NULL if it is
not already defined.
[-- Attachment #2: tcl-strstr-NULL.patch --]
[-- Type: text/x-patch, Size: 526 bytes --]
Index: tcl/compat/strstr.c
===================================================================
RCS file: /cvs/src/src/tcl/compat/strstr.c,v
retrieving revision 1.5
diff -u -p -r1.5 strstr.c
--- tcl/compat/strstr.c 21 Jan 2003 19:39:57 -0000 1.5
+++ tcl/compat/strstr.c 23 Apr 2008 18:07:50 -0000
@@ -12,6 +12,11 @@
* RCS: @(#) $Id: strstr.c,v 1.3 2002/01/26 01:10:08 dgp Exp $
*/
+#include "tcl.h"
+#ifndef NULL
+#define NULL 0
+#endif
+
/*
*----------------------------------------------------------------------
*
next parent reply other threads:[~2008-04-23 18:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EE8EE936-F2AD-41D0-9C29-5DB98D3AE80C@monami-software.com>
2008-04-23 18:10 ` Keith Seitz [this message]
2008-04-23 18:14 ` Keith Seitz
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=480F7A05.4050005@redhat.com \
--to=keiths@redhat.com \
--cc=insight@sourceware.org \
--cc=monaka@monami-software.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).