From: Tarkin on
Hey folks,
After poking around for a fair bit, I am unable to find anyone with
a kernel source
tree and/or toolchain source tree that has the following properties:
-- x86 or ia32 ONLY.
-- No Polish, Swahili, Korean, etc files.

I am looking into to picking through the kernel, and creating a build
environment
which is slim, manageable, and hackable.

As I am a native US-EN speaker, and don't yet need to develop for
other languages,
and don't yet need to build for other architectures, I'd like to
eliminate as much
unnecessary material possible.

Has anyone come across a project, website, or source tree with even
remotely
similar traits?

TIA,
Tarkin
From: Douglas Mayne on
On Sun, 28 Mar 2010 08:08:49 -0700, Tarkin wrote:

> Hey folks,
> After poking around for a fair bit, I am unable to find anyone with
> a kernel source
> tree and/or toolchain source tree that has the following properties:
> -- x86 or ia32 ONLY.
> -- No Polish, Swahili, Korean, etc files.
>
> I am looking into to picking through the kernel, and creating a build
> environment
> which is slim, manageable, and hackable.
>
> As I am a native US-EN speaker, and don't yet need to develop for
> other languages,
> and don't yet need to build for other architectures, I'd like to
> eliminate as much
> unnecessary material possible.
>
> Has anyone come across a project, website, or source tree with even
> remotely
> similar traits?
>
> TIA,
> Tarkin
>
AFAIK, almost all GNU/Linux distributions are available with precompile
binaries for ia32. It remains the most popular architecture. Likewise,
the us-en language is the most prominent language used. Also, IMO, you
won't save much space by attempting to "simplify" by reducing language
choice.

Therefore, your questions may be simplified by first picking a
distribution that you'd like to use. Personally, I use Slackware. It has
a very minimal footprint (by today's standards). If you are trying to
limit the storage requirements, then consider that Slackware consumes
less than 4G when installing _all_ of the packages from the main package
groups (a,ap,d,l,n,x,xap). BTW, these "absolute" minimum discussions come
up fairly often, but are less relevent with the progression of Moore's
law. If you want a command-line based development environment, the
(a,ap,d) package groups would most likely suffice and fit within about
1G.

Another approach which may be more to your liking is the "Linux from
Scratch" project.

--
Douglas Mayne
From: Mark Hobley on
Tarkin <tarkin000(a)gmail.com> wrote:
> After poking around for a fair bit, I am unable to find anyone with
> a kernel source
> tree and/or toolchain source tree that has the following properties:
> -- x86 or ia32 ONLY.
> -- No Polish, Swahili, Korean, etc files.

I am working on a fork of the kernel and toolchain for the IA32. These are in
development stages, due to bugs in the toolchain

For the kernel:

http://markhobley.yi.org/k486/index.html

This removes processor supplementary instructions incompatible with IA32.

I have also forked the compiler instruction table to trap non-IA32 instructions
at compile time, and the autotools are being forked to produce more compact
scripts in portable shell syntax format.

Revised compiler:

ftp://markhobley.yi.org/packages/mgcc/

Revised autoconf:

ftp://markhobley.yi.org/packages/autoconf/

There are some invalid instructions in glibc, but I have not yet manged to fix
those, but I have not yet worked out the purpose of these.

> Has anyone come across a project, website, or source tree with even
> remotely similar traits?

The Naked Lady project will provide all of these traits, but I have not yet
managed to build a release.

http://markhobley.yi.org/nakedlady/index.html

Mark.

--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/

From: Mark Hobley on
Douglas Mayne <doug(a)localhost.localnet> wrote:
> AFAIK, almost all GNU/Linux distributions are available with precompile
> binaries for ia32.

Linux does not actually build properly for IA32, and crashes with a Bug Int 6
(invalid opcode) error on some IA32 machines, due to invalid instructions
being embedded within the kernel. (These are not trapped at compile time
on a traditional system, causing a hard crash when the kernel become
deployed on some machines.)

Mark.

--
Mark Hobley
Linux User: #370818 http://markhobley.yi.org/