--- Comment #6 from paulbeard at gmail dot com 2008-05-24 20:16 ---
(In reply to comment #5)
> GCC is running out of memory.
>
> Oh. I'll add a swapfile and see how that goes.
>
It still just grinds until I kill the process. I have since worked around this
problem
--- Comment #5 from paulbeard at gmail dot com 2008-05-22 23:18 ---
GCC is running out of memory.
Oh. I'll add a swapfile and see how that goes.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36294
--- Comment #3 from paulbeard at gmail dot com 2008-05-22 14:31 ---
Created an attachment (id=15670)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15670&action=view)
gtk.i file
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36294
--- Comment #1 from paulbeard at gmail dot com 2008-05-22 03:06 ---
Here is a more complete report:
gcc -v -save-temps -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/local/include/python2.5
-I/usr/local/include/pygtk-2.0 -I/usr/local/include/glib-2.0
-I/usr/local/lib/glib-2.0/include -I./gtk -I
Severity: blocker
Priority: P3
Component: c
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: paulbeard at gmail dot com
GCC target triplet: i386-undermydesk-freebsd
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36294
