From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
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: Sat, 23 Feb 2008 06:57:49 +1300 [thread overview]
Message-ID: <46a038f90802220957y7db67d8nb6b7ad784124546a@mail.gmail.com> (raw)
In-Reply-To: <20080222065836.GE8410@spearce.org>
On Fri, Feb 22, 2008 at 7:58 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> 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.
I'll track down Basilio (it's his laptop) today and try, I think he's
still at the conference. I also suspect that OSX's own build tools may
include a different msgfmt, but the fink one is earlier in the path.
cheers,
m
next prev parent reply other threads:[~2008-02-22 17:58 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
2008-02-22 17:57 ` Martin Langhoff [this message]
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=46a038f90802220957y7db67d8nb6b7ad784124546a@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=bbh@tampico.org.mx \
--cc=git@vger.kernel.org \
--cc=gsaldana@gmail.com \
--cc=spearce@spearce.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).