-
Notifications
You must be signed in to change notification settings - Fork 882
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
configure: assembler stdout incorrect (cosmetic issue only) #3036
Comments
ggouaillardet
added a commit
to ggouaillardet/ompi
that referenced
this issue
Feb 27, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used Fixes open-mpi#3032 Refs open-mpi#3036 Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
ggouaillardet
added a commit
to ggouaillardet/ompi
that referenced
this issue
Feb 27, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used Fixes open-mpi#3032 Refs open-mpi#3036 Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp> (cherry picked from commit open-mpi/ompi@2f4013c)
ggouaillardet
added a commit
to ggouaillardet/ompi
that referenced
this issue
Feb 27, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used Fixes open-mpi#3032 Refs open-mpi#3036 Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp> (cherry picked from commit open-mpi/ompi@2f4013c)
This was referenced Feb 27, 2017
Per the discussion on #3039, this feels like a cosmetic issue, not something that is actually doing the Wrong Thing on the back-end. Defer to v2.1.1. |
bosilca
pushed a commit
to bosilca/ompi
that referenced
this issue
Mar 7, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used Fixes open-mpi#3032 Refs open-mpi#3036 Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
markalle
pushed a commit
to markalle/ompi
that referenced
this issue
Apr 5, 2017
there is no need to look for an assembly file when BUILTIN_GCC is used Fixes open-mpi#3032 Refs open-mpi#3036 Signed-off-by: Gilles Gouaillardet <gilles@rist.or.jp>
resolved by @ggouaillardet |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm seeing an incorrect identification of the hardware architecture (similar to issue reported on master #3032):
This was on an Intel x86_64 box.
The text was updated successfully, but these errors were encountered: