From: Tuncer Ayaz <tuncer.ayaz@gmail.com>
To: David Turner <dturner@twopensource.com>
Cc: git@vger.kernel.org
Subject: Re: 745224e0 gcc-4.9 emmintrin.h build error
Date: Thu, 10 Jul 2014 23:59:00 +0200 [thread overview]
Message-ID: <CAOvwQ4h=uFCN36dQt4uqwJv8393iVhiCh09+71DhhzyWrbCfUA@mail.gmail.com> (raw)
In-Reply-To: <1405025616.3775.6.camel@stross>
On Thu, Jul 10, 2014 at 10:53 PM, David Turner wrote:
> On Thu, 2014-07-10 at 22:44 +0200, Tuncer Ayaz wrote:
> > On Thu, Jul 10, 2014 at 10:33 PM, David Turner wrote:
> > > On Thu, 2014-07-10 at 21:59 +0200, Tuncer Ayaz wrote:
> > > > The changes in 745224e0 don't seem to build here with gcc-4.9 on
> > > > linux x64_64. Any idea what's wrong?
> > > >
> > > > CC credential-store.o
> > > > In file included from /usr/lib/.../xmmintrin.h:31:0,
> > >
> > > What's in the ...?
> > >
> > > Because if you're using headers from a different version of gcc, that
> > > might explain it.
> >
> > /usr/lib/gcc/x86_64-unknown-linux-gnu/4.9.0/include/emmintrin.h
>
> That seems fine to me.
>
> It looks like the error messages are coming from inside the system's
> header files (but this is sometimes misleading). If you just try to
> compile
>
> #include <emmintrin.h>
> int main() { }
>
> with whatever options you use for git, does that work? If not, I would
> say that you have a compiler setup problem.
The above test works on the same machine, so I'll
investigate what's going on when building git. Thanks.
next prev parent reply other threads:[~2014-07-10 21:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 19:59 745224e0 gcc-4.9 emmintrin.h build error Tuncer Ayaz
2014-07-10 20:06 ` Tuncer Ayaz
2014-07-10 20:23 ` Jeff King
2014-07-10 20:43 ` Tuncer Ayaz
2014-07-10 20:33 ` David Turner
2014-07-10 20:44 ` Tuncer Ayaz
2014-07-10 20:53 ` David Turner
2014-07-10 21:59 ` Tuncer Ayaz [this message]
2014-07-10 22:12 ` Tuncer Ayaz
2014-07-10 22:58 ` David Turner
2014-07-12 4:56 ` Jeff King
2014-07-12 8:47 ` Tuncer Ayaz
2014-07-14 6:00 ` Jeff King
2014-07-12 8:53 ` Tuncer Ayaz
2014-07-14 6:04 ` Jeff King
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='CAOvwQ4h=uFCN36dQt4uqwJv8393iVhiCh09+71DhhzyWrbCfUA@mail.gmail.com' \
--to=tuncer.ayaz@gmail.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.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).