Mark, do you still have gcc-2.95.3 available to try? (or see if gcc -V
2.95.3 works)
Out of interest, I ran "imf all" on the 7.4.03.03 sources, and got very
few problems, just some environment issues (PATH, and PYTHON_INCLUDE
path...), and instlsrv in lctools.mac and ls.mac - certainly nothing
that looked compiler related.
That suggests to me, along with your report, that gcc is indeed the
problem. I don't think it's a gcc bug, as such, but they did change some
things around with the 3.x series (made it more "correct" I think), so
we might have to tweak some code, or figure out which compiler switches
to use.
Richard.
On Fri, 2002-09-27 at 07:24, Post, Mark K wrote:
> Using gcc 3.2 to compile the database sources, I'm seeing this error on the
> LVCSim_liveCacheSink.cpp module:
>
> In file included from /usr/include/c++/3.2/string:57,
> from LVCSim_liveCacheSink.cpp:60:
> /usr/include/c++/3.2/bits/basic_string.tcc: In member function
> `_Alloc::size_type std::basic_string<_CharT, _Traits,
> _Alloc>::rfind(const _CharT*, _Alloc::size_type, _Alloc::size_type) const':
> /usr/include/c++/3.2/bits/basic_string.tcc:713: parse error before `(' token
>
> The line at 713 is this:
> __pos = std::min(__size - __n, __pos);
>
> Since the error is reported against
> /usr/include/c++/3.2/bits/basic_string.tcc, I believe this to be a gcc
> problem, and not a sapdb problem. Would I be correct about that?
>
> Mark Post
> _______________________________________________
> sapdb.general mailing list
> [EMAIL PROTECTED]
> http://listserv.sap.com/mailman/listinfo/sapdb.general
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
