Skip to Content.
Sympa Menu

sm-sorcery-bugs - [SM-Sorcery-Bugs] [Bug 7472] bi-arch support

sm-sorcery-bugs AT lists.ibiblio.org

Subject: Bugs for Sorcery are reported here

List archive

Chronological Thread  
  • From: bugzilla-daemon AT metalab.unc.edu
  • To: sm-sorcery-bugs AT lists.ibiblio.org
  • Subject: [SM-Sorcery-Bugs] [Bug 7472] bi-arch support
  • Date: Fri, 8 Oct 2004 20:01:33 -0400

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





------- Additional Comments From acedit AT armory.com 2004-10-08 20:01 -------
Thanks for the summary, very concise and informative for an ignoramous
like myself :)

So just to clarify, if BI_ARCH_SPELL is set to yes, sorcery repeats
the build process with different variables set? What steps
do we repeat? Should we make BUILD_SUB and INSTALL_SUB files?
The alternative is for spells that have problems on some
arches but not others is to inspect the ARCH variable
(or whatever it is). Maybe we should set a global variable
for spells to test if they need certain things in BUILD/INSTALL
to be idempotent, the variable could indicate whether or not
this is the native architecture.

What about generalizing to a more scalable solution? Im
considering the case where a platform gets three arch's or
more. Consider transmeta processors, which may embody several
cpu classes.

Would it be more advantageous to have SUBFOO be arrays?

SUBARCH[0]="x86_32"
SUBLIB[0]="/lib32"
SUBARCH[1]="whiz-bang"
SUBLIB[1]="/lib-wb"

We could run BUILD/INSTALL once for each sub-architecture.

SHould the looping be as follows:

native: BUILD
PRE_INSTALL
native: INSTALL
non-native: BUILD
non-native: INSTALL
(repeat previous 2)

or
native:BUILD
non-native: BUILD
(repeat previous)
PRE_INSTALL
native:INSTALL
non-native: INSTALL
(repeat previous)

I prefer the second as it maintains the phased approach.


Do spells that over-ride default_build (and use ./configure) need
work done? should bugs be filed on the grimoire side? If the default
build always uses -libdir=$LIB then shouldnt all the arch's get a
LIB variable? We may want to get that in sooner rather than later
if we are to be migrating spells over the next six months.

What release is all this planned for? 1.12? post-1.0?




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.




Archive powered by MHonArc 2.6.24.

Top of Page