[C++-sig] Slow gcc 3.2 links

greg Landrum greglandrum at mindspring.com
Tue Nov 19 18:24:11 CET 2002

At 09:07 AM 11/19/2002, Ralf W. Grosse-Kunstleve wrote:
>When linking my Boost.Python V2 extension modules with gcc 3.2 under Linux 7.3
>and 8.0 I have to wait up to 10 minutes per link command to finish. gcc <=
>3.0.4 never had this problem. The machine does not run out of core memory when
>linking with 3.2, but uses 99% of a CPU all the time. Do others have similar
>observations, or is it just me doing something stupid?

I've also noticed both long link times and big memory use (>200MB) using 
BPLv2 and g++ 3.2 under RH8.0 (mmm, alphanumeric soup).  Of course, I could 
also be playing in the "something stupid" pool.

However, since I haven't done a build using BPLv1 recently, I'm not sure 
this is BPLv2 specific.


More information about the Cplusplus-sig mailing list