public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* No luck building GCC on sparc-linux using --with-gc=zone
@ 2004-03-25  0:05 Art Haas
  2004-03-30  8:18 ` Jim Wilson
  0 siblings, 1 reply; 2+ messages in thread
From: Art Haas @ 2004-03-25  0:05 UTC (permalink / raw)
  To: gcc

Hi.

I've started using a SparcStation20 running Debian, and am playing with
building GCC-3.5 on this machine. After several failed builds, I removed
the '--with-gc=zone' configure option, and the build lacking this option
has built well past the point builds with the option in place have
failed. Is the '--with-gc=zone' option something that non-X86 builds
should avoid? I build GCC on my i586-pc-linux-gnu with this option
without difficulty. If this option should work on sparc-linux, I'd be
glad to test patches to fix the problem(s). I tried to begin to
debug things, but even after setting my environment so core files should
appear, which I failed to do earlier, my failing builds never produced a
core file that I could at least try to debug.  I'm sure I've overlooked
something obvious here, but so far the obvious eludes me ...

Art Haas
-- 
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.

-Thomas Jefferson to James Smith, 1822

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: No luck building GCC on sparc-linux using --with-gc=zone
  2004-03-25  0:05 No luck building GCC on sparc-linux using --with-gc=zone Art Haas
@ 2004-03-30  8:18 ` Jim Wilson
  0 siblings, 0 replies; 2+ messages in thread
From: Jim Wilson @ 2004-03-30  8:18 UTC (permalink / raw)
  To: Art Haas; +Cc: gcc

Art Haas wrote:
> failed. Is the '--with-gc=zone' option something that non-X86 builds
> should avoid?

It should work for any target with mmap I think.  However, it is fairly 
new, so it may still have some portability problems.

The default is for gcc to not dump core when it ICEs.  Core files just 
confuse average users.  We only generate a core file if we have an 
unhandled signal that causes a core dump.  To debug the problem, you 
need to run cc1 (or cc1plus or whatever) under gdb, and put a breakpoint 
on fancy_abort.  The gcc .gdbinit file will do this for you 
automatically if you run gdb in the build tree.
-- 
Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2004-03-30  1:44 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-03-25  0:05 No luck building GCC on sparc-linux using --with-gc=zone Art Haas
2004-03-30  8:18 ` Jim Wilson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).