SourceMage Grimoire Bug List

[bugzilla-daemon AT bugs.sourcemage.org]

http://bugs.sourcemage.org/show_bug.cgi?id=15712

           Summary: Stage 1/3 of eglibc based sorcery
           Product: New Spells
           Version: unspecified
          Platform: x86
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Spell Submission
        AssignedTo: sm-grimoire-bugs AT lists.ibiblio.org
        ReportedBy: seanm1 AT iastate.edu



seanm1 AT iastate.edu changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
               Flag|                            |must_fix_before_release+


What this is is a stable cross-compiler that can compile gcc executables using
eglibc. What this isn't is a stable eglibc that can build sorcery-compatible
executeables. There is a plan to get to point B (see below), but I don't have
the time.

I'd attempted to get an eglibc spell using a new grimoire, which when cast in 
a
fresh copy of sourcemage, would allow stable grimoire spells to be cast on top
of it. I was doing it primarily to help myself, as it would allow me to take
advantage of sourcemage spells on the system I'm already using.

I was doing it using the instructions here,
http://trac.cross-lfs.org/

from the SVN-20100103 version, slightly modified as follows:

-no /tools or /cross-tools directories, everything built in /usr/src
-instead of making a new chroot/system, overwriting or "possessing" the build
environment with a new core system using the eglibc c library

Essentially, I was going to go through chapters 5 and 6, and then build the 
new
C library, and then cast enough stable grimoire spells (modified however I had
to to make them work) to be able to use the stable grimoire without
modification.

In reality, I got as far as completing chapter 5. The temporary version of GMP
won't build, and summer semester is starting at school, so I just don't have
the time. I want the fruits of my labor to help other people with the same
goal, so I'm posting my progress.

The problem it's facing right now is really simple: the C compiler works 
great,
and the C++ compiler works, but doesn't have access to any of the C++ headers
(iostream, etc). They don't even get built.

Basically, this was the planned workflow

-Build a static C compiler with its library built-in
-Use it to build a temporary eglibc
-Use that temporary eglibc and the static compiler to build a cross compiler
-Use that cross compiler to build a temporary toolchain
-Use the temporary toolchain to replace the host system's C library (the
temporary toolchain is necessary because this step breaks EVERY SINGLE ONE of
the host's tools)
-Use the new C library to build a new "native" compiler
-Use the new compiler and new library to build the core system to the point
where it's stable enough to build sourcemage

I got up to step 3 before giving up.

-- 
Configure bugmail: http://bugs.sourcemage.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.