Your message dated Wed, 26 Nov 2014 22:37:25 +0000
with message-id
<capq4b8kfzdqo3smi+dbl8jv87ts8nq5gqasp6xs9t7hslqm...@mail.gmail.com>
and subject line Re: gcc-4.2: Appears to enter infinite loop, claiming more and
more memory
has caused the Debian Bug report #475546,
regarding gcc-4.2: Appears to enter infinite loop, claiming more and more memory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
475546: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475546
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gcc-4.2
Version: 4.2.3-3
Severity: normal
While trying to compile a program called tomoe (can be downloaded at
http://sourceforge.net/project/showfiles.php?group_id=193138&package_id=227469
), gcc stops working properly in that it fails to complete the
following operation, as generated by the configure script without any
options in the Makefile:
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../bindings/ruby -I/usr/include/glib-2.0
-I/usr/lib/glib-2.0/include -DCONFDIR=\"/usr/local/etc/tomoe\"
-DDATADIR=\"/usr/local/share/tomoe\"
-DDICT_DATADIR=\"/usr/local/share/tomoe/dict\"
-DRECOGNIZER_DATADIR=\"/usr/local/share/tomoe/recognizer\"
-DDICT_MODULEDIR=\"/usr/local/lib/tomoe/module/dict\"
-DRECOGNIZER_MODULEDIR=\"/usr/local/lib/tomoe/module/recognizer\" -I../../lib
-I/subversion-1 -DG_LOG_DOMAIN=\"Tomoe/Dict:Unihan\" -DRUBY_EXTDIR=\"\"
-DRUBY_LIBDIR=\"\" -g -O2 -Wall -Wmissing-declarations -Wmissing-prototypes
-Wpointer-arith -Wcast-align -MT unihan_la-tomoe-unihan.lo -MD -MP -MF
.deps/unihan_la-tomoe-unihan.Tpo -c tomoe-unihan.c -fPIC -DPIC -o
.libs/unihan_la-tomoe-unihan.o
This was reproducible (after "make clean" and then "make" again). It
is possible that it would have completed sometime, but not after a
sane amount of time and approximately 1.5 GB of memory allocation
(after which I used Ctrl+C to stop the build process). Leaving -O2
away in the command line causes the file to be compiled properly.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-k7 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages gcc-4.2 depends on:
ii binutils 2.18.1~cvs20080103-4 The GNU assembler, linker and bina
ii cpp-4.2 4.2.3-3 The GNU C preprocessor
ii gcc-4.2-base 4.2.3-3 The GNU Compiler Collection (base
ii libc6 2.7-10 GNU C Library: Shared libraries
ii libgcc1 1:4.3.0-1 GCC support library
Versions of packages gcc-4.2 recommends:
ii libc6-dev 2.7-10 GNU C Library: Development Librari
-- no debconf information
--- End Message ---
--- Begin Message ---
2012-11-18 14:59 GMT+00:00 Manuel A. Fernandez Montecelo
<[email protected]>:
> 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
Since the package gcc-4.2 was removed ~5 years ago, the bug reports
are orphan (not assigned to any maintainer/package) and didn't see any
activity for more than 2 years (after the last messsage above), I
think that it makes sense to close the reports now.
Please reassign against the relevant packages present nowadays in the
archive, if the issues are still present.
Regards.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
