Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Description of problem: The released source package, mingw32-boost-1.41.0-3, fails to rebuild using mock/koji. The system fails when trying to build complaining about assembler errors. How reproducible: 100% Actual results: [ 96%] Building CXX object libs/wave/src/CMakeFiles/boost_wave-mt-shared-debug.dir/instantiate_predef_macros.cpp.obj cd /builddir/build/BUILD/boost-1.41.0.cmake0/build/libs/wave/src && /usr/bin/i686-pc-mingw32-g++ -Dboost_wave_mt_shared_debug_EXPORTS -DBOOST_ALL_NO_LIB=1 -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions --param=ssp-buffer-size=4 -mms-bitfields -I/builddir/build/BUILD/boost-1.41.0.cmake0 -g -DBOOST_ALL_DYN_LINK=1 -o CMakeFiles/boost_wave-mt-shared-debug.dir/instantiate_predef_macros.cpp.obj -c /builddir/build/BUILD/boost-1.41.0.cmake0/libs/wave/src/instantiate_predef_macros.cpp In file included from /builddir/build/BUILD/boost-1.41.0.cmake0/libs/wave/src/instantiate_cpp_exprgrammar.cpp:24: /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp: In static member function 'static bool boost::wave::grammars::expression_grammar_gen<TokenT>::evaluate(const typename std::list<TokenT, boost::fast_pool_allocator<TokenT, boost::default_user_allocator_new_delete, boost::details::pool::win32_mutex, 32u> >::const_iterator&, const typename std::list<TokenT, boost::fast_pool_allocator<TokenT, boost::default_user_allocator_new_delete, boost::details::pool::win32_mutex, 32u> >::const_iterator&, const typename TokenT::position_type&, bool, boost::wave::grammars::value_error&) [with TokenT = boost::wave::cpplexer::lex_token<boost::wave::util::file_position<boost::wave::util::flex_string<char, std::char_traits<char>, std::allocator<char>, boost::wave::util::CowString<boost::wave::util::AllocatorStringStorage<char, std::allocator<char> >, char*> > > >]': /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:652: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:658: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:1211: note: initialized from here /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:652: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:727: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:725: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:1211: note: initialized from here /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:652: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:727: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:725: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:1211: note: initialized from here /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:652: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:658: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:1211: note: initialized from here /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:652: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:727: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:725: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:1211: note: initialized from here /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:652: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:727: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:725: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:1211: note: initialized from here cc1plus: warning: dereferencing pointer 'p' does break strict-aliasing rules cc1plus: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:1211: note: initialized from here cc1plus: warning: dereferencing pointer 'p' does break strict-aliasing rules cc1plus: warning: dereferencing pointer 'p' does break strict-aliasing rules /builddir/build/BUILD/boost-1.41.0.cmake0/boost/wave/util/flex_string.hpp:1211: note: initialized from here {standard input}: Assembler messages: {standard input}:266841: Error: junk at end of line, first unrecognized character is `:' Expected results: A clean compile of the package Additional info: Attched is a full build log.