https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61577
--- Comment #114 from dave.anglin at bell dot net --- On 2020-01-22 7:18 p.m., peter.bisroev at groundlabs dot com wrote: > >From what I can see in my other tests, we need C++ compiler built with GCC > 4.7.4 to bootstrap GCC 6.1.0 and above. This is due to the fact that using C++ > compiler from 4.1.2 generates errors due to poisoned functions errors such as > this one: > -------------------- > <dstpath>/opt/gcc-4.1.2/32/gcc-4.1.2/lib/gcc/ia64-hp-hpux11.31/4.1.2/include/stdlib.h:233: > error: attempt to use poisoned "calloc" > -------------------- > > I specifically pointed version 6.1.0 out as it was the first version where > C++14 standard was enabled by default. So to get GCC 4.7.4 working we can > either try and figure out how to bootstrap it with HP's compiler or to work > from GCC 4.1.2 and figure out what broke with 4.2.0 and go from there. > > What are your thoughts? I would try to build 4.7.4 directly with aCC or gcc 3.3.6 (i.e., skip intermediates). Maybe just build C in your first attempt at 4.7.4. If I recall this thread correctly, the issue with C++ relates to linkonce and one-only support for C++. There are patches in this thread that fix some problems but not all... On my parisc build system, I have maxtsize set at 134217728. Maybe you should double your current value but that should be enough. This size command should show the actually text size of cc1 and cc1plus. A log of the size of cc1 is debug info. 4.1.2 is probably broken and has miscompiled 4.2.0. If you hit the same issue building 4.7.4, then it's worthwhile trying to debug the stack overflow. Getting this going is not likely to be easy... Dave
