From: Ferris McCormick <fmccor@gentoo.org>
To: Ned Ludd <solar@gentoo.org>
Cc: gentoo-hardened@lists.gentoo.org, gentoo-dev@lists.gentoo.org,
anthony@ectrolinux.com, dmonnier@iu.edu, markusle@gmail.com,
mtindal@paradoxpoint.com, webkiller71@trsn.be, ps.m@gmx.net,
bgb@itcnv.com, co@kevquinn.com, tocharian@trilug.org
Subject: Re: [gentoo-dev] Not considering dropping the hardened toolchain
Date: Tue, 21 Sep 2004 18:25:42 +0000 (UTC) [thread overview]
Message-ID: <Pine.LNX.4.60.0409211822120.22429@lacewing.inforead.com> (raw)
In-Reply-To: <1095789660.8317.1590.camel@simple>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Tue, 21 Sep 2004, Ned Ludd wrote:
> Good afternoon gentlemen. Thanks for your feedback to the other thread.
>
> -----------------------------------------------------------------------
> 8) Supporting new arches.
>
> Currently only x86/amd64/sparc64 are supported by the hardened
> toolchain.
>
My hardened SS20 (sparc32) feels neglected... :)
> Thanks for your time and I look fwd to working with you guys (gals?).
> --
> Ned Ludd <solar@gentoo.org>
> Gentoo (hardened,security,infrastructure,embedded,toolchain) Developer
>
Regards,
- --
Ferris McCormick (P44646, MI) <fmccor@gentoo.org>
Developer, Gentoo Linux (Sparc)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFBUHIqQa6M3+I///cRAqGNAJ4l+buPHXOxJfZ8l7Ue1gcLJ+8fawCfSPtN
R2SzM65x4Vr43qOmbSNwWrI=
=WL22
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-21 18:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-21 18:01 [gentoo-dev] Not considering dropping the hardened toolchain Ned Ludd
2004-09-21 18:25 ` Ferris McCormick [this message]
2004-09-21 21:19 ` [gentoo-dev] Re: [gentoo-hardened] " Dave Monnier, IT Security Office, Indiana University
2004-09-21 23:06 ` [gentoo-dev] " Duncan
2004-10-02 21:40 ` Michael Tindal
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=Pine.LNX.4.60.0409211822120.22429@lacewing.inforead.com \
--to=fmccor@gentoo.org \
--cc=anthony@ectrolinux.com \
--cc=bgb@itcnv.com \
--cc=co@kevquinn.com \
--cc=dmonnier@iu.edu \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-hardened@lists.gentoo.org \
--cc=markusle@gmail.com \
--cc=mtindal@paradoxpoint.com \
--cc=ps.m@gmx.net \
--cc=solar@gentoo.org \
--cc=tocharian@trilug.org \
--cc=webkiller71@trsn.be \
/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