From: sc843@bard.edu
To: ultralinux@vger.kernel.org
Subject: Re: More sparc64-libc questions
Date: Mon, 01 Oct 2001 01:36:07 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-100190023621389@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-100187097332030@msgid-missing>
Thanks Ben!
Indeed it _is_ ld-linux.so.2 which segfaults (I'm using a recent CVS.)
I'm seriously considering creating a pure 64-bit Sparc distribution of Linux.
Everyting that can be would be native 64-bit (init, shells, X, etc...). Having
the compiler working is a good thing, and I'll test glibc 2.2.4 and see whether
that fixes my segfault problem.
I understand that this will provide only marginal performance benefits, and
that Debian has a solid distro out with 64-bit support, but I'm doing this as
much for the adventure as for the performance benefits. How is a distribution
usually begun? I'd take the next release of GCC (3.0.2) and the latest release
of libc.
This would probably be a personal project; I don't want to spend the kind of
time required to keep packages up-to-date, etc. Would there any interest at all
out there in a Sparc-bootable ISO with some tarballs that unpack to a bare-
bones distro that could be used as a base to compile everything else? I'd
probably use http://www.linuxfromscratch.org as a guide.
Sincerely,
Sean Callanan
next prev parent reply other threads:[~2001-10-01 1:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-30 17:20 More sparc64-libc questions Sean Callanan
2001-09-30 18:06 ` Ben Collins
2001-10-01 1:36 ` sc843 [this message]
2001-10-01 1:52 ` Ben Collins
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=marc-linux-ultrasparc-100190023621389@msgid-missing \
--to=sc843@bard.edu \
--cc=ultralinux@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