Hello David, Thanks for the detailed bug report, I am sorry that it was left unattended for so long. I'm just doing some cleanup, I am not a maintainer of the GCC package in Debian.
The package version is not present in Debian, and the bug is orphan now (without assigned package/maintainer), which it means that, even if not closed, people probably will not pay any attention to it anymore (unless it's reassigned to a package existing in the active releases of Debian). According to the following URL, the package was removed from official repositories back in 2009: http://packages.qa.debian.org/g/gcc-4.2.html I tried to reproduce the problem myself, but It's building fine for me (gcc (Debian 4.7.2-4) 4.7.2, default compiler at this time for unstable and testing), although I don't have some of the options enabled (Python and Ruby bindings or backends). Some "cc1" processes top at about 500MB of resident memory, but nothing seems out of the ordinary. Can you please try to reproduce the bug and give more details, at least the configuration options? If so, we should reassign the bug to the current package names/versions. Otherwise, I think that it's better to close the bug report. Configure Result: * Language Bindings Ruby : no Python : no * Dictionary Backends Unihan Database : yes Hyper Estraier : no Subversion : no MySQL : no Ruby : no * Other Features gtk-doc : no Cheers. -- Manuel A. Fernandez Montecelo <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
