From: "Shawn O. Pearce" <spearce@spearce•org>
To: Martin Langhoff <martin.langhoff@gmail•com>
Cc: "Git Mailing List" <git@vger•kernel.org>,
"Basilio Brice–ño H." <bbh@tampico•org.mx>,
gsaldana@gmail•com
Subject: Re: msgmft segfaulting on tiger
Date: Fri, 22 Feb 2008 01:58:36 -0500 [thread overview]
Message-ID: <20080222065836.GE8410@spearce.org> (raw)
In-Reply-To: <46a038f90802211559w457c5460k7447ba8b38352713@mail.gmail.com>
Martin Langhoff <martin.langhoff@gmail•com> wrote:
> On Fri, Feb 22, 2008 at 12:53 PM, Martin Langhoff
> <martin.langhoff@gmail•com> wrote:
> > Today I've debugged a compile of git 1.5.4.2 failing on OSX Tiger (on
> > Basilio's machine). The problem is during the git-gui build, in the PO
> > file handling. Apparently fmtmsg (from fink) segfaults on de.po so the
> > fix is to say
>
> Grumble. It seems like msgfmt that fink provides actually does not
> support the --tcl flag. So perhaps the right thing is to always say
> NO_MSGFMT on OSX?
I'd hate to do this. GNU msgfmt does better checking on the
messages then po2msg.sh does, and its a tiny bit faster. So
I'd rather stick to the standard tool that is widely used.
Currently we are looking to see if msgfmt generates an exit status
of 127, and if so we fallback to po2msg.sh. Apparently however
that test is passing and thus you are using the fink msgfmt.
Did you try building with `make V=1` to look at the full output and
not the prettied up simplified output the Makefile uses by default?
It won't fix your issue but it may be interesting to see if msgfmt
is failing with a particular message or not.
--
Shawn.
next prev parent reply other threads:[~2008-02-22 6:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 23:53 msgmft segfaulting on tiger Martin Langhoff
2008-02-21 23:59 ` Martin Langhoff
2008-02-22 6:58 ` Shawn O. Pearce [this message]
2008-02-22 17:57 ` Martin Langhoff
2008-02-27 18:18 ` Gabriel Saldaña
2008-02-27 18:26 ` Johannes Schindelin
2008-02-27 18:42 ` Gabriel Saldaña
2008-02-27 22:04 ` Johannes Schindelin
2008-02-27 22:14 ` Junio C Hamano
2008-02-28 0:32 ` Shawn O. Pearce
2008-03-04 7:02 ` msgmft segfaulting on ubuntu gutsy (clean) Gabriel Saldaña
2008-03-04 7:07 ` Shawn O. Pearce
2008-02-28 18:40 ` msgmft segfaulting on tiger Gabriel Saldaña
2008-03-05 7:19 ` Shawn O. Pearce
2008-03-06 8:40 ` Junio C Hamano
2008-03-12 5:29 ` [PATCH] Simplify MSGFMT setting in Makefile Junio C Hamano
2008-03-12 5:51 ` Shawn O. Pearce
2008-03-12 10:19 ` Charles Bailey
2008-03-14 4:44 ` Paul Mackerras
2008-03-14 4:50 ` Junio C Hamano
2008-03-14 13:07 ` Andreas Ericsson
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=20080222065836.GE8410@spearce.org \
--to=spearce@spearce$(echo .)org \
--cc=bbh@tampico$(echo .)org.mx \
--cc=git@vger$(echo .)kernel.org \
--cc=gsaldana@gmail$(echo .)com \
--cc=martin.langhoff@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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