New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 719736 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Sep 2017
Cc:
Components:
EstimatedDays: 2
NextAction: 2017-05-09
OS: Linux , Chrome
Pri: 2
Type: Bug



Sign in to add a comment

nfs-ganesha ebuild uses system libntirpc, should use bundled lib

Project Member Reported by abiusx@chromium.org, May 8 2017

Issue description

Chrome Version: 60.0.3077.0 unknown (64-bit)
OS: Chromium OS

What steps will reproduce the problem?
Attempting to build nfs-ganesha with the current ebuild fails when linking, because nfs-ganesha uses several symbols that are not available in the standard libntirpc.

The bundled libntirpc should be used instead.

What is the expected result?
Linker should use the bundled lib and resolve the symbols.

What happens instead?
Link error.
 
the only package using net-libs/ntirpc is nfs-ganesha, and we're telling it to use our own copy of the tree, so changing nfs-ganesha to use its bundled version doesn't make much sense.  we control both, so they should be in sync.
Ganesha's build is tightly coupled with that of libntirpc.
We separated them into two repos. ganesha still looks into its 'libntirpc' folder for everything. Even using the option 'NTIRPC_BASE_DIR' doesn't seem to appease it.

The only solution I can think of is symlinking the folder to the libntirpcs src before configuring. Otherwise, major refactoring in the cmake process would be needed.
Owner: slavamn@chromium.org
please close if stale.
Status: WontFix (was: Started)
Ganesha appears to be working reliably with current build configuration. Please reopen if I missed other reasons to make the switch.
Components: OS>Systems>Containers

Sign in to add a comment