From: solar <solar@gentoo.org>
To: gentoo-embedded <gentoo-embedded@lists.gentoo.org>
Subject: [gentoo-embedded] [Fwd: stage4-{mips,mipsel,amd64,i686}-uclibc-{vanilla,hardened} on experimental]
Date: Mon, 09 Jul 2012 07:42:38 -0700 [thread overview]
Message-ID: <1341844958.25763.1.camel@here> (raw)
[-- Attachment #1: Type: text/plain, Size: 46 bytes --]
FYI
--
solar <solar@gentoo.org>
Gentoo Linux
[-- Attachment #2: Forwarded message - stage4-{mips,mipsel,amd64,i686}-uclibc-{vanilla,hardened} on experimental --]
[-- Type: message/rfc822, Size: 2868 bytes --]
From: "Anthony G. Basile" <blueness@gentoo.org>
To: mips@gentoo.org, hardened@gentoo.org, embedded@gentoo.org
Subject: stage4-{mips,mipsel,amd64,i686}-uclibc-{vanilla,hardened} on experimental
Date: Sun, 08 Jul 2012 12:51:54 -0400
Message-ID: <4FF9BAAA.8040300@gentoo.org>
Hi everyone,
I just wanted to let everyone know that I've put some experimental
uclibc stage4's on the mirror. They're in
experimental/{amd64,i686,mips}/uclibc and here's what they are:
1. I call them stage4 because they have more than stage3 in them and
they are not built with catalyst nor by cross compiling. The mips were
initially seeded via cross compiling with buildroot, but then I used
that environment to bootstrap into a full system on native hardware via
something like ROOT=rootfs emerge -e world. ie. I did what catalyst
does manually.
2. They are uclibc so they are aimed at embedded systems. The mips are
aimed at boards like the mikrotik rb450g's, ubiquity's routerstations or
other similar.
3. The mips are mips = big endian and mipsel = little endian. They are
MIPS III (in uclibc's config CONFIG_MIPS_ISA_3=y) for maximum compat.
4. The mips are abi = o32. The amd64 and i686 are their classical
abi's. No x32.
5. They have full hardening = PIE and SSP like glibc that the hardened
team takes care of. I've also include the vanilla stage4 counterparts
for completeness.
6. They are not fully in tree yet. The mips make use of the profiles
and gcc-4.6.3-r99 from the hardened-dev::uclibc overlay. The
{amd64,i686} make use of the profiles from the same overlay. I'm in the
process of moving everything to the tree. The next iteration of
{amd64,i686} will be 100% in tree.
7. They are not hack-ish in that if you do an emerge -q world the entire
chroot will rebuild cleanly.
This is work that Zorry and I have been at for years. The pieces are
finally starting to come together for something polished enough for the
community. Hopefully I'll have arm and ppc by the end of summer.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 8040 5A4D 8709 21B1 1A88 33CE 979C AF40 D045 5535
GnuPG ID : D0455535
reply other threads:[~2012-07-09 15:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1341844958.25763.1.camel@here \
--to=solar@gentoo.org \
--cc=gentoo-embedded@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