zsh-workers
 help / color / mirror / code / Atom feed
From: Wayne Davison <wayned@users.sourceforge.net>
To: acs@alumni.princeton.edu
Cc: zsh-workers@sunsite.dk
Subject: Re: SunOS build failures for the last 2 days
Date: Wed, 17 Aug 2005 12:16:46 -0700	[thread overview]
Message-ID: <20050817191646.GA25280@blorf.net> (raw)
In-Reply-To: <20a8072105081711525ba950a7@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 480 bytes --]

On Wed, Aug 17, 2005 at 02:52:54PM -0400, Vin Shelton wrote:
> This prints 'No'.

OK.  I also note that the ZLE_UNICODE_SUPPORT define is not defined in
your config.h, which is as it should be for a "No" case.  So, I just
forced multibyte off for my system and I note that those prototypes
are still in the utils.epro file.  Ahh, the #ifdef lines are not
properly marked as needing to be copied into the utils.epro file.
Attached is a patch that I'm about to check in.

..wayne..

[-- Attachment #2: ifdef.patch --]
[-- Type: text/plain, Size: 1531 bytes --]

--- Src/string.c	15 Aug 2005 17:20:29 -0000	1.6
+++ Src/string.c	17 Aug 2005 19:11:55 -0000
@@ -54,6 +54,7 @@ ztrdup(const char *s)
     return t;
 }
 
+/**/
 #ifdef ZLE_UNICODE_SUPPORT
 /**/
 mod_export wchar_t *
@@ -67,6 +68,7 @@ wcs_ztrdup(const wchar_t *s)
     wcscpy(t, s);
     return t;
 }
+/**/
 #endif /* ZLE_UNICODE_SUPPORT */
 
 
--- Src/utils.c	15 Aug 2005 17:20:29 -0000	1.87
+++ Src/utils.c	17 Aug 2005 19:11:55 -0000
@@ -243,6 +243,7 @@ nicechar(int c)
     return buf;
 }
 
+/**/
 #ifdef ZLE_UNICODE_SUPPORT
 /**/
 mod_export wchar_t *
@@ -280,6 +281,7 @@ wcs_nicechar(wint_t c)
     *s = 0;
     return buf;
 }
+/**/
 #endif /* ZLE_UNICODE_SUPPORT */
 
 
@@ -2493,6 +2495,7 @@ zarrdup(char **s)
     return y;
 }
 
+/**/
 #ifdef ZLE_UNICODE_SUPPORT
 /**/
 mod_export wchar_t **
@@ -2506,6 +2509,7 @@ wcs_zarrdup(wchar_t **s)
 
     return y;
 }
+/**/
 #endif /* ZLE_UNICODE_SUPPORT */
 
 /**/
@@ -3106,6 +3110,7 @@ zputs(char const *s, FILE *stream)
     return 0;
 }
 
+/**/
 #ifdef ZLE_UNICODE_SUPPORT
 /**/
 mod_export int
@@ -3127,6 +3132,7 @@ wcs_zputs(wchar_t const *s, FILE *stream
     }
     return 0;
 }
+/**/
 #endif /* ZLE_UNICODE_SUPPORT */
 
 /* Create a visibly-represented duplicate of a string. */
@@ -3215,6 +3221,7 @@ niceztrlen(char const *s)
     return l;
 }
 
+/**/
 #ifdef ZLE_UNICODE_SUPPORT
 /**/
 mod_export size_t
@@ -3236,6 +3243,7 @@ wcs_nicewidth(wchar_t const *s)
     }
     return l;
 }
+/**/
 #endif /* ZLE_UNICODE_SUPPORT */
 
 /* check for special characters in the string */

      reply	other threads:[~2005-08-17 19:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 15:08 Vin Shelton
2005-08-17 16:51 ` Andrey Borzenkov
2005-08-17 17:15 ` Wayne Davison
2005-08-17 17:35   ` Andrey Borzenkov
2005-08-17 17:50     ` Wayne Davison
2005-08-17 18:15       ` Wayne Davison
2005-08-17 18:52   ` Vin Shelton
2005-08-17 19:16     ` Wayne Davison [this message]

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=20050817191646.GA25280@blorf.net \
    --to=wayned@users.sourceforge.net \
    --cc=acs@alumni.princeton.edu \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).