From: Jeff King <peff@peff.net>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Renato Botelho <garga@freebsd.org>,
Junio C Hamano <gitster@pobox.com>,
Git List <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git v2.7.4 (and updates to older maintenance tracks)
Date: Sun, 20 Mar 2016 15:43:13 -0400 [thread overview]
Message-ID: <20160320194313.GB6288@sigill.intra.peff.net> (raw)
In-Reply-To: <CAPig+cSOjFqcKGaZC1HWGdp7aCg7Dog1GvFYPYRbShARPm9ODQ@mail.gmail.com>
On Sun, Mar 20, 2016 at 01:07:52PM -0400, Eric Sunshine wrote:
> On Sun, Mar 20, 2016 at 11:32 AM, Renato Botelho <garga@freebsd.org> wrote:
> >> On Mar 17, 2016, at 18:07, Junio C Hamano <gitster@pobox.com> wrote:
> >> Git v2.7.4 Release Notes
> >>
> >> Junio C Hamano (4):
> >> Git 2.4.11
> >> Git 2.5.5
> >> Git 2.6.6
> >> Git 2.7.4
> >
> > FYI,
> >
> > 2.7.4 fails to build on FreeBSD 9.x, that uses by default gcc 4.2.1. I’ve fixed it adding an extra dependency to make force it to require gcc 4.8+. Here is the output:
> >
> > cc -o combine-diff.o -c -MF ./.depend/combine-diff.o.d -MQ combine-diff.o -MMD -MP -isystem/usr/local/include -O2 -pipe -fstack-protector -fno-strict-aliasing -I. -I/usr/local/include -I/usr/local/include -DUSE_CURL_FOR_IMAP_SEND -I/usr/include -DUSE_ST_TIMESPEC -pthread -DHAVE_PATHS_H -DHAVE_STRINGS_H -DGMTIME_UNRELIABLE_ERRORS -DHAVE_CLOCK_GETTIME -DHAVE_CLOCK_MONOTONIC -DHAVE_BSD_SYSCTL -DHAVE_GETDELIM -DSHA1_HEADER='<openssl/sha.h>' -DDIR_HAS_BSD_GROUP_SEMANTICS -DSHELL_PATH='"/bin/sh"' combine-diff.c
> > combine-diff.c: In function 'diff_tree_combined':
> > combine-diff.c:1391: internal compiler error: Segmentation fault: 11
> > Please submit a full bug report,
> > with preprocessed source if appropriate.
> > See <URL:http://gcc.gnu.org/bugs.html> for instructions.
> > Makefile:1924: recipe for target 'combine-diff.o' failed
> > gmake: *** [combine-diff.o] Error 1
> > *** [do-build] Error code 1
>
> Interesting. This appears to be the same bug as [1].
>
> [1]: http://thread.gmane.org/gmane.comp.version-control.git/287486/focus=287789
Yes. AFAICT that version of gcc is simply buggy, and we are not doing
anything illegal or even particularly exotic. Given how old it is, I'm
not sure it's worth worrying too much about it, but I am happy to work
around it if somebody can figure out how to do so.
I spent some time trying to bisect gcc, but had trouble getting a
working build for a gcc that old.
-Peff
next prev parent reply other threads:[~2016-03-20 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 21:07 [ANNOUNCE] Git v2.7.4 (and updates to older maintenance tracks) Junio C Hamano
2016-03-18 8:29 ` Torsten Bögershausen
2016-03-20 15:32 ` Renato Botelho
2016-03-20 17:07 ` Eric Sunshine
2016-03-20 19:43 ` Jeff King [this message]
2016-03-21 4:41 ` Eric Sunshine
2016-03-21 13:33 ` Renato Botelho
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=20160320194313.GB6288@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=garga@freebsd.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.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 NNTP newsgroup(s).