Skip to content

Fix configure for FreePGI on OSX #1704

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

Merged
merged 1 commit into from
May 26, 2016
Merged

Fix configure for FreePGI on OSX #1704

merged 1 commit into from
May 26, 2016

Conversation

hpcraink
Copy link
Member

Our checks and the ones of libevent are somewhat flawed.
If adding multiple "-framework" to CXXFLAGS or CFLAGS, we strip
the keyword from the command-line, not good.
libevent however assumes plain gcc without testing properly
that the compiler supports -Wno-deprecated-declarations.

Our checks and the ones of libevent are somewhat flawed.
If adding multiple "-framework" to CXXFLAGS or CFLAGS, we strip
the keyword from the command-line, not good.
libevent however assumes plain gcc without testing properly
that the compiler supports -Wno-deprecated-declarations.
@jsquyres
Copy link
Member

The libevent fix should probably be pushed upstream, too (along with proper indenting -- I assume you didn't re-indent here in OMPI to make the minimal change).

Otherwise, 👍

@jsquyres
Copy link
Member

I hit "submit" too soon -- I meant to mention that libevent's upstream is here on github. You might just want to file a PR with them: https://github.com/libevent/libevent

@jladd-mlnx
Copy link
Member

@hpcraink @jsquyres The Mellanox Jenkins failure is new and legit. It's coming from Libevent. Please do not merge this without fixing.

@jsquyres
Copy link
Member

The problem did not come from this PR; the problem came from #1422, which I asked @bosilca not to merge.

@rhc54
Copy link
Contributor

rhc54 commented May 25, 2016

Agreed - this is a harmless change.

@hppritcha
Copy link
Member

I think the MLNX jenkins failure is owing to PR #1422 which ought not to have been merged till we sorted out why that PR seemed to have broken oshmem hello world.

@hjelmn
Copy link
Member

hjelmn commented May 25, 2016

I would go ahead and merge this one. Looks good to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants