From: spbecker <spbecker@vt.edu>
To: gentoo-mips@lists.gentoo.org
Subject: RE: [gentoo-mips] shmem
Date: Thu, 11 Aug 2005 15:01:41 -0400 [thread overview]
Message-ID: <430B082C@zathras> (raw)
>This is n32. I recall at least one of the apps working with o32. What
>would be the issue with n32?
How many warnings have you ignored so far about using n32? I've lost count by
now. I've sent at least 3 or 4 to the list, and I know hardave has warned you
also.
Seriously, n32 doesn't work properly yet. It has major bugs and really should
not be used by anyone but developers. We aren't supporting n32 until these
problems have been worked out, and that may be a long time yet. That is all.
-Steve
--
gentoo-mips@gentoo.org mailing list
next reply other threads:[~2005-08-11 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 19:01 spbecker [this message]
2005-08-11 19:12 ` [gentoo-mips] shmem David Cummings
2005-08-11 19:23 ` Ciaran McCreesh
-- strict thread matches above, loose matches on Subject: below --
2005-08-11 23:49 spbecker
2005-08-31 5:28 ` Kumba
2005-08-31 13:36 ` Stephen P. Becker
[not found] <dbce9302050810121728becc46@mail.gmail.com>
2005-08-10 19:52 ` David Cummings
2005-08-11 0:41 ` Stuart Longland
2005-08-11 4:32 ` David Cummings
2005-08-11 18:10 ` David Cummings
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=430B082C@zathras \
--to=spbecker@vt.edu \
--cc=gentoo-mips@lists.gentoo.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