From: sjhill@realitydiluted.com
To: Bryan Althouse <bryan.althouse@3phoenix.com>
Cc: "'Daniel Jacobowitz'" <dan@debian.org>,
"'Stephen P. Becker'" <geoman@gentoo.org>,
macro@blysk.ds.pg.gda.pl,
"'Linux/MIPS Development'" <linux-mips@linux-mips.org>
Subject: Re: Seg fault when compiled with -mabi=64 and -lpthread
Date: Fri, 1 Jul 2005 09:54:09 -0500 (CDT) [thread overview]
Message-ID: <E1DoMu9-0007J0-62@real.realitydiluted.com> (raw)
In-Reply-To: <20050701150938Z8226157-3678+821@linux-mips.org>
> Looks like I should upgrade glibc, and possibly gcc. When you say that I
> should try CVS HEAD of glibc, I'm not sure what you mean. I have looked in
> the linux-mips.org CVS and the closest thing I can find is libc, and it
> looks really old. I have also found a glibc CVS at
> :pserver:anoncvs@sources.redhat.com:/cvs/glibc. If I get libc from here is
> this the "CVS HEAD"?
>
> Should I get GCC from the generic GCC site, or should get it from the
> linux-mips CVS?
>
> I apologize for the simple questions. I have not built a tool chain before.
> I've been using the one supplied by PMC-Sierra. Will I need to patch any of
> these sources for MIPs?
>
Also, stay away from the HEAD of GCC CVS. GCC-4.1.0 compilers cannot
build Linux kernels.
-Steve
next prev parent reply other threads:[~2005-07-01 15:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-30 17:33 Seg fault when compiled with -mabi=64 and -lpthread Bryan Althouse
2005-06-30 19:08 ` Stephen P. Becker
2005-06-30 19:31 ` Bryan Althouse
2005-06-30 20:21 ` Ralf Baechle
2005-06-30 21:03 ` Daniel Jacobowitz
2005-06-30 22:09 ` Stephen P. Becker
2005-07-01 3:51 ` Daniel Jacobowitz
2005-07-01 4:44 ` Kumba
2005-07-01 8:49 ` Maciej W. Rozycki
2005-07-01 13:39 ` Daniel Jacobowitz
2005-07-01 14:10 ` Maciej W. Rozycki
2005-07-01 14:46 ` Daniel Jacobowitz
2005-07-01 15:04 ` Maciej W. Rozycki
2005-07-01 14:56 ` Stephen P. Becker
2005-07-01 15:22 ` Maciej W. Rozycki
2005-07-01 16:39 ` Stephen P. Becker
2005-07-01 17:02 ` Daniel Jacobowitz
2005-07-01 17:15 ` Stephen P. Becker
2005-07-01 15:09 ` Bryan Althouse
2005-07-01 15:09 ` Bryan Althouse
2005-07-01 14:54 ` sjhill [this message]
2005-07-01 15:29 ` Maciej W. Rozycki
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=E1DoMu9-0007J0-62@real.realitydiluted.com \
--to=sjhill@realitydiluted.com \
--cc=bryan.althouse@3phoenix.com \
--cc=dan@debian.org \
--cc=geoman@gentoo.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@blysk.ds.pg.gda.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.