Bug 1943729 - excluded on ppc64le due to configure issue
Summary: excluded on ppc64le due to configure issue
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: mcrouter
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Davide Cavalca
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: PPCTracker
TreeView+ depends on / blocked
 
Reported: 2021-03-26 23:13 UTC by Davide Cavalca
Modified: 2022-07-19 14:28 UTC (History)
3 users (show)

Fixed In Version: mcrouter-0.41.0.20220314-3.fc37
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-07-19 14:28:40 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Davide Cavalca 2021-03-26 23:13:59 UTC
On ppc64le-test.fedorainfracloud.org

configure:14605: checking for boostlib >= 1.65.1
configure:14685: g++ -c -DLIBMC_FBTRACE_DISABLE -DDISABLE_COMPRESSION  -Wno-missing-field-initializers -Wno-deprecated -W -Wall -Wextra -Wno-unused-parameter -fno-strict-aliasing -std=c++17 -g -O2  -I/usr/include conftest.cpp >&5
configure:14685: $? = 0
configure:14687: result: yes
configure:14867: checking whether the Boost::Context library is available
configure:14905: g++ -c -DLIBMC_FBTRACE_DISABLE -DDISABLE_COMPRESSION  -Wno-missing-field-initializers -Wno-deprecated -W -Wall -Wextra -Wno-unused-parameter -fno-strict-aliasing -std=c++17 -g -O2  -I/usr/include conftest.cpp >&5
conftest.cpp: In function 'int main()':
conftest.cpp:40:38: warning: unused variable 'fc' [-Wunused-variable]
   40 |   boost::context::detail::fcontext_t fc = boost::context::detail::make_fcontext(0, 0, 0);
      |                                      ^~
configure:14905: $? = 0
configure:14920: result: yes
configure:15080: error: Could not find a version of the library!

Host has boost-context-1.73.0-9.fc33.ppc64le

Comment 1 Davide Cavalca 2021-03-26 23:15:15 UTC
Relevant configure.ac is

# check for boost libs
AX_BOOST_BASE([1.65.1], [], [AC_MSG_ERROR(
              [Please install boost >= 1.65.1 (context, filesystem, program_options, regex and system)])])
# TODO: also check boost::ctx, not only boost::context
AX_BOOST_CONTEXT
AX_BOOST_FILESYSTEM
AX_BOOST_PROGRAM_OPTIONS
AX_BOOST_REGEX
AX_BOOST_SYSTEM
AX_BOOST_THREAD

Comment 2 Dan Horák 2021-03-27 10:55:09 UTC
In theory upstream could be using an outdated ax_boost autoconf macro. Can you try refreshing it from autoconf-archive?

Comment 3 Davide Cavalca 2021-03-27 16:10:17 UTC
I tried that yesterday and it didn't seem to help. I also skimmed the generated 'configure' script and it looked overall sane, though these things are pretty hard to spot in my experience.

Comment 4 Fedora Admin user for bugzilla script actions 2022-03-26 12:31:29 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 5 Fedora Admin user for bugzilla script actions 2022-03-29 00:30:24 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 6 Dan Horák 2022-03-30 10:57:57 UTC
I am pretty sure the problem here is with the bundled (and outdated) mcrouter/m4/ax_boost_base.m4 file. There is a check for arches that use "lib64" directory and it lacks ppc64le (see line 97). It has been fixed in later ax_boost_base.m4 releases.

Comment 7 Fedora Admin user for bugzilla script actions 2022-07-09 00:18:38 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 8 Fedora Admin user for bugzilla script actions 2022-07-09 12:19:00 UTC
This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Comment 9 Mamoru TASAKA 2022-07-19 14:28:40 UTC
(In reply to Dan Horák from comment #6)
> I am pretty sure the problem here is with the bundled (and outdated)
> mcrouter/m4/ax_boost_base.m4 file. There is a check for arches that use
> "lib64" directory and it lacks ppc64le (see line 97). It has been fixed in
> later ax_boost_base.m4 releases.

Applied in mcrouter-0.41.0.20220314-3.fc37


Note You need to log in before you can comment on or make changes to this bug.