<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>
> gmp/mpfr<br><br>Go ahead and either:<br>cm3 -DM3CC_CONFIG="...lots..." which should circument a bunch of the m3makefile content,<br>or edit the m3makefile to probe for your location. /Presumably/ nobody is going to have anything there, that they don't mind getting used in this way. ?<br><br>The whole m3-sys/m3cc/m3makefile could be considered "optional".<br>It's a "thin" wrapper over just building gcc.<br>It tries to do the right thing in "all" situations, but I'm sure it often fails or<br>is incomplete, such as for cross builds.<br><br>This is my newfound wisdom from just this week, still subject to sinking in and being wrong. :)<br><br>> bash syntax<br><br>Sorry I really don't know what is sh vs. ksh vs. bash.<br>Does anyone know of an implementation that adheres closely to sh that I can use to stop regressing stuff?<br>Preferably that runs on one or more of:<br> MacOS X (PowerPC for now)<br> x86 or AMD64 or PowerPC Linux<br> x86 or AMD64 NT<br><br>Kubuntu (that I'm using) has "dash" for /bin/sh. Good?<br><br>Or some flag I should use for bash?<br>I can check the docs, but, next two points:<br><br>I do usually use the Python stuff, partly to avoid this problem.<br><br>Oh, but this about boot*.sh. I never looked at, ran, or changed that, sorry.<br>Really...writing scripts/python and quake/m3makefile is usually relatively fun and productive but not this *.sh :)<br><br> - Jay<br><br><br><br>> From: hosking@cs.purdue.edu<br>> To: alexb@juniper.net<br>> Date: Fri, 18 Apr 2008 10:15:51 -0400<br>> CC: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] TOT CM3 compile.<br>> <br>> I haven't touched that portion of things (bash syntax). Jay may be <br>> the culprit. :-)<br>> <br>> On Apr 18, 2008, at 1:37 AM, Alex Bochannek wrote:<br>> <br>> > Tony Hosking <hosking@cs.purdue.edu> writes:<br>> ><br>> >> Because there is now a new target, you need to first build a <br>> >> bootstrap<br>> >> compiler that understands the new target specs. To build a bootstrap<br>> >> compiler, compile and ship the following packages:<br>> ><br>> > That's what happens when I can't pay attention to the mailing list <br>> > for a<br>> > while. Suddenly everything changes :-) Building right now...<br>> ><br>> > Couple of related things.<br>> ><br>> > I happened to be looking at script/boot-cm3-core.sh and noticed that<br>> > there some Bash syntax crept in. You touched that file more recently <br>> > and<br>> > since it is a bit late for me, I thought maybe you can check if I've <br>> > got<br>> > the logic right in the replacement for the -ot operator<br>> ><br>> > Index: boot-cm3-core.sh<br>> > ===================================================================<br>> > RCS file: /usr/cvs/cm3/scripts/boot-cm3-core.sh,v<br>> > retrieving revision 1.9<br>> > diff -u -r1.9 boot-cm3-core.sh<br>> > --- boot-cm3-core.sh 13 Apr 2008 18:22:32 -0000 1.9<br>> > +++ boot-cm3-core.sh 18 Apr 2008 05:37:02 -0000<br>> > @@ -25,7 +25,7 @@<br>> > BUILDARGS="${BUILDARGS:--DM3_BOOTSTRAP=TRUE -keep}"<br>> > M3CONFIG_SRC=${ROOT}/m3-sys/cm3/src/config/${CROSS_TARGET}<br>> > M3CONFIG=${ROOT}/scripts/${TARGET}-${CROSS_TARGET}.cfg<br>> > -if [ ! -f "${M3CONFIG}" -o "${M3CONFIG}" -ot "${M3CONFIG_SRC}" ] ; <br>> > then<br>> > +if [ ! -f "${M3CONFIG}" -o -z `find "${M3CONFIG}" -prune -newer "$ <br>> > {M3CONFIG_SRC}"` ] ; then<br>> > sed -e "s;m3back.*=.*;m3back = \"@${ROOT}/m3-sys/m3cc/${TARGET}-$ <br>> > {CROSS_TARGET}/cm3cg\";" \<br>> > ${M3CONFIG_SRC} > ${M3CONFIG}<br>> > fi<br>> ><br>> ><br>> > I noticed that the new GCC needs GMP and MPFR. I can't install <br>> > anything<br>> > in /usr on my machine (it's a zone on a Solaris server) and instead <br>> > use<br>> > Blastwave, which puts things into /opt/csw. The only way to tell the<br>> > build process where to pick up the libraries is by modifying line <br>> > 319 in<br>> > m3-sys/m3cc/src/m3makefile. Is there a better way?<br>> ><br>> > Thanks,<br>> ><br>> > Alex.<br>> <br></body>
</html>