All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Ciccone <jciccone@gmail.com>
To: sparclinux@vger.kernel.org
Subject: Silo 1.4.10
Date: Fri, 10 Feb 2006 21:03:09 +0000	[thread overview]
Message-ID: <43ECFF8D.7050801@gmail.com> (raw)
In-Reply-To: <1136175018.27583.50.camel@grayson>

I have been working on a patch for silo that would enable me to build it in a pure64 bit enviornment. The patch is of my current working tree. The .b files build properly with this patch, It creates a static libext2fs that I put together myself and then uses that instead of the system libext2fs library which is only available in 64bit in this setup. The loaders are built 32bit and the rest of the programs are built 64bit. This is done with a modification to Rules.make by creating a CC (for host tools) and CC-SILO (for always 32bit parts). This setup relies on the fact that you have a working elftoaout binary, this was discussed earlier on this list, if you would like me to provide the patch please let me know. The include directory after this patch is applied is so large because I have copied headers from my 32bit build. CC-SILO is instructed not to use any headers from the system. This fixes and issue in the building of the .b files, which should have never included any of the system headers in the first place. I think I've traced down the problem to silo.c because before I run silo -f the .b files from my successful installation are identical to the loaders in this setup. When the table in the top of second.b is generated with silo -f, it doesn't seem to be right. I have one request, Don't say silo doesn't work on 64bit only systems. I am looking for some assistance in fixing this issue. The patch I have attached is a Major head start for anyone who has tried this in the past. I apreciate any help I can get on making this work, I've spent a lot of time on this already but I don't understand the inner workings of the silo program.

The Silo-1.4.10 patch is http://www.crazyeyesoft.com/Silo-1.4.10-fixes-2.patch



  parent reply	other threads:[~2006-02-10 21:03 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-02  4:10 SILO 1.4.10 Ben Collins
2006-01-02 21:34 ` Jim Gifford
2006-01-02 22:05 ` Ben Collins
2006-01-02 22:05 ` Tom 'spot' Callaway
2006-01-02 22:12 ` Jim Gifford
2006-01-02 22:44 ` Ben Collins
2006-01-02 22:51 ` Jim Gifford
2006-01-02 23:09 ` Ben Collins
2006-01-02 23:58 ` Jim Gifford
2006-01-03  0:55 ` Ben Collins
2006-01-03  2:53 ` Jim Gifford
2006-01-03  3:22 ` Ben Collins
2006-01-03 15:43 ` Jim Gifford
2006-01-03 17:39 ` Jim Gifford
2006-01-03 20:50 ` David S. Miller
2006-01-03 21:38 ` David S. Miller
2006-01-03 21:52 ` Richard Mortimer
2006-01-03 22:08 ` David S. Miller
2006-01-03 22:31 ` Jim Gifford
2006-01-03 22:31 ` Jim Gifford
2006-02-10 21:03 ` Joe Ciccone [this message]
2006-02-10 22:44 ` Silo 1.4.10 David S. Miller
2006-02-11  0:32 ` Joe Ciccone
2006-02-12 13:14 ` Ben Collins
2006-03-07  1:12 ` Joe Ciccone

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=43ECFF8D.7050801@gmail.com \
    --to=jciccone@gmail.com \
    --cc=sparclinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.