git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Sixt <j.sixt@viscovery.net>
To: "H.Merijn Brand" <h.m.brand@xs4all.nl>
Cc: Junio C Hamano <gitster@pobox.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Andreas Ericsson <ae@op5.se>,
	git@vger.kernel.org, Sam Vilain <sam@vilain.net>
Subject: Re: Building git-1.5.3.7 on HP-UX 11.00
Date: Tue, 11 Dec 2007 12:01:27 +0100	[thread overview]
Message-ID: <475E6E07.60904@viscovery.net> (raw)
In-Reply-To: <20071211114251.78ae357a@pc09.procura.nl>

H.Merijn Brand schrieb:
> On Tue, 11 Dec 2007 10:20:55 +0100, Johannes Sixt <j.sixt@viscovery.net>
> wrote:
> 
>> Junio C Hamano schrieb:
>>> "H.Merijn Brand" <h.m.brand@xs4all.nl> writes:
>>>> 3 I am willing to believe that HP_UX' vsnprintf () is broken, or
>>>>   at least does not conform to the expectations in the GNU world,
>>>>   but chickening out like the way strbuf_addf () does is maybe a
>>>>   bit too rude, so I forced a minimum of 64bytes available. That
>>>>   fixes a lot!
>>>>
>>>>   but it still breaks t4013 :(
>>> I think Shawn had something similar for Solaris, and if it is a small
>>> cost to help portability, it does not feel so bad.
>> Windows's vsnprintf() is broken in two regards: (1) It returns -1 if the
>> buffer is too small; (2) the size parameter is not the size of the buffer,
>> but the max. number of chars to write (i.e. does not count the NUL). How
>> broken is HP-UX's?
> 
> Do you have a simple test program to show how `broken' it is?
> I have 10.20, 11.00, 11.11, 11.23/PA and 11.23/IPF and both
> HP C-ANSI-C and gcc

Sorry, no. vsnprintf's behavior on Windows is actually documented, so to be
fair it is not "broken", but "unwanted".

-- Hannes

  reply	other threads:[~2007-12-11 11:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04 13:09 Building git-1.5.3.7 on HP-UX 11.00 H.Merijn Brand
2007-12-04 13:44 ` Johannes Schindelin
2007-12-04 14:03   ` H.Merijn Brand
2007-12-04 14:40     ` Johannes Schindelin
2007-12-04 15:01       ` H.Merijn Brand
2007-12-04 15:14         ` Andreas Ericsson
2007-12-04 15:22           ` H.Merijn Brand
2007-12-04 15:39             ` Johannes Schindelin
2007-12-04 15:56               ` H.Merijn Brand
2007-12-04 16:28                 ` Johannes Schindelin
2007-12-05 10:49                   ` H.Merijn Brand
2007-12-04 18:05                 ` Junio C Hamano
2007-12-04 22:25                   ` H.Merijn Brand
2007-12-04 22:46                     ` Johannes Schindelin
2007-12-05  8:08                       ` H.Merijn Brand
2007-12-04 22:45                   ` [PATCH] Do not rely on the exit status of "unset" for unset variables Johannes Schindelin
2007-12-05  8:01                     ` H.Merijn Brand
2007-12-10 14:51                   ` Building git-1.5.3.7 on HP-UX 11.00 H.Merijn Brand
2007-12-11  8:26                     ` Junio C Hamano
2007-12-11  8:54                       ` Shawn O. Pearce
2007-12-11 12:57                         ` H.Merijn Brand
2007-12-11  9:20                       ` Johannes Sixt
2007-12-11 10:42                         ` H.Merijn Brand
2007-12-11 11:01                           ` Johannes Sixt [this message]
2007-12-11 13:33                       ` H.Merijn Brand
2007-12-11 13:53                         ` Johannes Sixt
2007-12-04 15:11       ` H.Merijn Brand

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=475E6E07.60904@viscovery.net \
    --to=j.sixt@viscovery.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=h.m.brand@xs4all.nl \
    --cc=sam@vilain.net \
    /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).