Opened 21 years ago

Closed 19 years ago

#22 closed Support Requests (Wont Fix)

compilation failure on Linux RH 7.1

Reported by: nobody Owned by: John Maddock
Milestone: Component: None
Version: None Severity:
Keywords: Cc:

Description

OS: RH7.1
gcc: 2.96.85

The following defect stops the compilation:

user@host> jam -sBOOST_ROOT=. -sTOOLS="gcc"

traits_type, Allocator> &) [with iterator =
boost::re_detail::mapfile_iterator, charT = char, 
traits_type =
boost::regex_traits<char>, Allocator = 
allocator<char>]':
boost/regex/detail/regex_match.hpp:566:   instantiated 
from `boost::re_detail::query_match_aux (iterator, 
iterator, boost::match_results<iterator, Allocator> &, 
const boost::reg_expression<charT, traits, Allocator2> 
&, unsigned int, 
boost::re_detail::_priv_match_data<iterator, 
Allocator> &, iterator *) [with iterator = 
boost::re_detail::mapfile_iterator, Allocator = 
allocator<char>, charT = char, traits = 
boost::regex_traits<char>, Allocator2 = 
allocator<char>]'
boost/regex/detail/regex_match.hpp:1114:   
instantiated from `boost::re_detail::reg_grep2 
(Predicate, I, I, const boost::reg_expression<charT, 
traits, Allocator2> &, unsigned int, A2) [with 
Predicate = boost::re_detail::pred4, I = 
boost::re_detail::mapfile_iterator, charT = char, 
traits = boost::regex_traits<char>, A = 
allocator<char>, A2 = allocator<char>]'
boost/regex/detail/regex_match.hpp:1773:   
instantiated from `boost::regex_grep (Predicate, 
iterator, iterator, const boost::reg_expression<charT, 
traits, Allocator2> &, unsigned int) [with Predicate = 
boost::re_detail::pred4, iterator = 
boost::re_detail::mapfile_iterator, charT = char, 
traits = boost::regex_traits<char>, Allocator = 
allocator<char>]'
libs/regex/build/../src/cregex.cpp:387:   instantiated 
from here
boost/regex.hpp:244: Internal compiler error in 
scan_region, at
except.c:2809
Please submit a full bug report.
See <URL:http://bugzilla.redhat.com/bugzilla/> for 
instructions.

    g++  -c -Wall -ftemplate-depth-100  -DNDEBUG -
DBOOST_RE_BUILD_DLL=1  -O4 -finline-functions -Wno-
inline -fPIC   -I"libs/regex/build" -I"."   -
o "libs/regex/build/bin/libboost_regex.so/gcc/release/r
untime-link-dynamic/shared-linkable-
true/cregex.o"  "libs/regex/build/../src/cregex.cpp"

...failed gcc-C++-action 
libs/regex/build/bin/libboost_regex.so/gcc/release/runt
ime-link-dynamic/shared-linkable-true/cregex.o ...
gcc-C++-action 
libs/regex/build/bin/libboost_regex.so/gcc/release/runt
ime-link-dynamic/shared-linkable-true/fileiter.o
gcc-C++-action 
libs/regex/build/bin/libboost_regex.so/gcc/release/runt
ime-link-dynamic/shared-linkable-true/posix_api.o
gcc-C++-action 
libs/regex/build/bin/libboost_regex.so/gcc/release/runt
ime-link-dynamic/shared-linkable-true/regex.o
gcc-C++-action 
libs/regex/build/bin/libboost_regex.so/gcc/release/runt
ime-link-dynamic/shared-linkable-true/regex_debug.o
gcc-C++-action 
libs/regex/build/bin/libboost_regex.so/gcc/release/runt
ime-link-dynamic/shared-linkable-true/regex_synch.o
gcc-C++-action 
libs/regex/build/bin/libboost_regex.so/gcc/release/runt
ime-link-dynamic/shared-linkable-
true/w32_regex_traits.o
gcc-C++-action 
libs/regex/build/bin/libboost_regex.so/gcc/release/runt
ime-link-dynamic/shared-linkable-true/wide_posix_api.o
...skipped <libs!regex!
build/libboost_regex.so/gcc/release/runtime-link-
dynamic/shared-linkable-true>libboost_regex.so for 
lack of <libs!regex!
build/libboost_regex.so/gcc/release/runtime-link-
dynamic/shared-linkable-true>cregex.o...
...failed updating 2 targets...
...skipped 2 targets...
...updated 117 targets...


Can someone please help me identify the cause of the 
problem. Is this really a compiler error as mentioned 
above.

thanks,

-Syed.

Change History (2)

comment:1 by pberndt, 20 years ago

Logged In: YES 
user_id=26829

I have a very similar problem under SuSE 8.1 (gcc3.2)
Also an Internal compiler error in cregex.cpp.
But my gcc3.2 is completely different from your gcc2.96.85.
Please let me know if you have found anything out.

comment:2 by John Maddock, 19 years ago

Status: assignedclosed
Logged In: YES 
user_id=14804

Yes, it is a compiler bug - upgrading to gcc 3.3 will fix the 
issue.  If you have a patch that fixes the problem for 2.96 
then I will apply it, but I'm not going to spend time looking for 
one given that this is a non-official gcc release.

John Maddock
Note: See TracTickets for help on using tickets.