From: David Turner <dturner@twopensource.com>
To: Tuncer Ayaz <tuncer.ayaz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: 745224e0 gcc-4.9 emmintrin.h build error
Date: Thu, 10 Jul 2014 13:53:36 -0700 [thread overview]
Message-ID: <1405025616.3775.6.camel@stross> (raw)
In-Reply-To: <CAOvwQ4hq5AZ0ZhB-1etUZfLfJ4X=11_03syH2pgY_fi=FSLAPQ@mail.gmail.com>
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.
next prev parent reply other threads:[~2014-07-10 20:53 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 [this message]
2014-07-10 21:59 ` Tuncer Ayaz
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=1405025616.3775.6.camel@stross \
--to=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=tuncer.ayaz@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.