Skip to content
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

configury: add portals4 include path to osc-monitoring component build #4521

Conversation

tkordenbrock
Copy link
Member

The osc-monitoring component didn't add the Portals4 include directory to AM_CPPFLAGS which causes a build failure if Portals4 is installed in a location that isn't in the compiler's default search path.

The PR clarifies the OPAL_CHECK_PORTALS4() prefix name, exports the Portals4 variables and adds the Portals4 CPPFLAGS to AM_CPPFLAGS.

Signed-off-by: Todd Kordenbrock thkgcode@gmail.com

@bosilca @jsquyres Please review.

# substitute in the things needed to build portals4
AC_SUBST([osc_monitoring_portals4_CPPFLAGS])
AC_SUBST([osc_monitoring_portals4_LDFLAGS])
AC_SUBST([osc_monitoring_portals4_LIBS])
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't look like the LDFLAGS and LIBS values are used.

Signed-off-by: Todd Kordenbrock <thkgcode@gmail.com>
Signed-off-by: Todd Kordenbrock <thkgcode@gmail.com>
@tkordenbrock tkordenbrock force-pushed the topic/master/osc.monitoring.portals4.build.failure branch from 41410c1 to cba8b7f Compare November 21, 2017 17:54
@bosilca
Copy link
Member

bosilca commented Nov 21, 2017

We do not need to interact with the other OSC modules. We are working on a fix.

@tkordenbrock
Copy link
Member Author

@jsquyres PR updated to remove unused variables.

@tkordenbrock
Copy link
Member Author

@bosilca So you are going to take out all the Portals4 references?

@bosilca
Copy link
Member

bosilca commented Nov 21, 2017

@tkordenbrock yes all references to other OSC components.

@jsquyres
Copy link
Member

@bosilca So should this PR be closed / replaced by a different PR?

@bosilca
Copy link
Member

bosilca commented Nov 27, 2017

A more generic approach is under development in #4527 .

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

Successfully merging this pull request may close these issues.

4 participants