From: Austin Gonyou <austin@digitalroadkill.net>
To: Shanti Katta <katta@csee.wvu.edu>
Cc: sparclinux@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Reg. segmentation fault on sparc with gcc-3.0 (ld)
Date: 07 Jul 2002 17:49:22 -0500 [thread overview]
Message-ID: <1026082162.11740.1.camel@UberGeek> (raw)
In-Reply-To: <1026081797.7057.10.camel@indus>
I would have to recommend you try 3.1. I've had issues compiling lots of
stuff with 3.0, until 3.0.4, but still 3.1 has been much better. The
issues were just odd, and I can't really say what fixed them exactly,
but rebuilding problematic programs, with gcc 3.1, made my problems go
away. Usual things were spurious segfaults for no apparent reason. GDB
couldn't even help, not really.
On Sun, 2002-07-07 at 17:43, Shanti Katta wrote:
> Hi,
> When I try to compile user-mode-linux on UltraSparc-I, I get the
> following error message during linking:
>
> gcc-3.0 -o mk_task mk_task_user.o mk_task_kern.o
> collect2: ld terminated with signal 11 [Segmentation fault], core dumped
>
> I could not get any help regarding this error on the web. Is it because
> of some sparc 32/64 oddities or it has something to do with the
> compiler?
>
> Any pointers will be appreciated
>
> Thank you,
> -Regards
> -Shanti
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Austin Gonyou <austin@digitalroadkill.net>
prev parent reply other threads:[~2002-07-07 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-07 22:43 Reg. segmentation fault on sparc with gcc-3.0 (ld) Shanti Katta
2002-07-07 22:49 ` Austin Gonyou [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1026082162.11740.1.camel@UberGeek \
--to=austin@digitalroadkill.net \
--cc=katta@csee.wvu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox