[M3devel] building CM3 on a Raspberry Pi?

mika at async.caltech.edu mika at async.caltech.edu
Mon Oct 14 19:14:08 CEST 2013


upgrade.py , OK...

not great.  

== package /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-sys/mklib ==

 +++ /nfs/site/home/mnystroe/work/cm3/bin/cm3    -build -DROOT=/nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3 +++
--- building in AMD64_LINUX ---

ignoring ../src/m3overrides

new source -> compiling Main.m3
"../src/Main.m3", line 659: incompatible types (b)
"../src/Main.m3", line 660: incompatible types (b)
"../src/Main.m3", line 661: incompatible types (b)
"../src/Main.m3", line 662: incompatible types (b)
"../src/Main.m3", line 663: incompatible types (b)
"../src/Main.m3", line 664: incompatible types (b)
"../src/Main.m3", line 665: incompatible types (b)
7 errors encountered
compilation failed => not building program "mklib"
Fatal Error: package build failed
 *** execution of [<function _BuildGlobalFunction at 0x2aaaab56b938>, <function _ShipFunction at 0x2aaaab56b9b0>] failed ***
(892)tsvnc06:...cm3-anon-cvs/cm3/scripts/python>

This is now on a Linux system, figured it's going to be more recent and easier to work with overall:

(893)tsvnc06:...cm3-anon-cvs/cm3/scripts/python>gcc -v
Reading specs from /nfs/ts/itools/em64t_SLES10/pkgs/gcc/4.7.0/.bin/../lib64/gcc/x86_64-suse-linux/4.7.0/specs
COLLECT_GCC=/usr/intel/pkgs/gcc/4.7.0/.bin/gcc
COLLECT_LTO_WRAPPER=/nfs/ts/itools/em64t_SLES10/pkgs/gcc/4.7.0/.bin/../libexec/gcc/x86_64-suse-linux/4.7.0/lto-wrapper
Target: x86_64-suse-linux
Configured with: ./configure --prefix=/usr/intel/pkgs/gcc/4.7.0 --libdir=/usr/intel/pkgs/gcc/4.7.0/lib64 --libexecdir=/usr/intel/pkgs/gcc/4.7.0/libexec --bindir=/usr/intel/pkgs/gcc/4.7.0/bin --with-ppl=/usr/intel/pkgs/gcc/4.7.0 --enable-cloog-backend=ppl --with-cloog=/usr/intel/pkgs/gcc/4.7.0 --with-libelf=/usr/intel/pkgs/gcc/4.7.0 --with-mpfr=/usr/intel/pkgs/gcc/4.7.0 --with-gmp=/usr/intel/pkgs/gcc/4.7.0 --with-mpc=/usr/intel/pkgs/gcc/4.7.0 --enable-lto --enable-languages=c,c++,objc,fortran,java --build=x86_64-suse-linux --host=x86_64-suse-linux --target=x86_64-suse-linux
Thread model: posix
gcc version 4.7.0 (GCC) 

The code it's complaining about is:

PROCEDURE WriteHeader (nm: TEXT;  mode: TEXT;  time: Time.T;  size: INTEGER)
  RAISES {Wr.Failure, Thread.Alerted} =
  TYPE HdrChars = ARRAY [0..BYTESIZE(Header)-1] OF CHAR;
  VAR hdr: Header;
  BEGIN
    StuffT (hdr.Name,      nm);                                            (* line 659 *)
    StuffI (hdr.Date,      ROUND (time - CoffTime.EpochAdjust));
    StuffT (hdr.UserID,    "");
    StuffT (hdr.GroupID,   "");
    StuffT (hdr.Mode,      mode);
    StuffI (hdr.Size,      size);
    StuffT (hdr.EndHeader, EndHeader);

    Wr.PutString (lib_wr, LOOPHOLE (hdr, HdrChars));
  END WriteHeader;

where:

PROCEDURE StuffT (VAR b: ARRAY OF UINT8;  txt: TEXT) =
  VAR len := Text.Length (txt);
  BEGIN
    FOR i := 0 TO MIN (len - 1, LAST (b)) DO
      b[i] := ORD (Text.GetChar (txt, i));
    END;
    FOR i := len TO LAST (b) DO
      b[i] := ORD (' ');
    END;
  END StuffT;

Jay K writes:
>--_0e9e017a-7bf6-48f0-afbe-640bab935860_
>Content-Type: text/plain; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
> > Fatal Error: unrecognized backend mode: C
>
>
>Make sure you ./update.py your main toolset first.
>Also=2C while the C backend was working a year ago=2C for quite
>a while I did not change the builder to know about it directly.
>I was going via m3cgcat.
>So you need to be fairly current=2C or else modify the
>config files a different way=2C and have it be slower.
>
>
> - Jay
>
>
>> To: jay.krell at cornell.edu
>> CC: m3devel at elegosoft.com
>> Subject: Re: [M3devel] building CM3 on a Raspberry Pi?
>> Date: Mon=2C 14 Oct 2013 09:40:08 -0700
>> From: mika at async.caltech.edu
>>=20
>> Jay writes:
>> >./../gcc-4.7/libiberty/stack-limit.c:52: error: `u_quad_t' undeclared (f=
>irst=3D
>> > use in this function)if [ x"" !=3D3D x ]=3B then \
>> >
>> >
>> >Maybe I removed too much. I.e. libquadmath. That should be easy to fix a=
>nd/o=3D
>> >r switch to C backend.
>> >
>> >
>> >I forgot: besides switching the config file: add the parameter "c" to bo=
>ot1.=3D
>> >py.
>> >
>> >
>>=20
>> If I put in config-no-install/ARMEL_LINUX
>>=20
>> M3_BACKEND_MODE=3D"C"
>>=20
>> and run
>>=20
>> ./boot1.py c ARMEL_LINUX
>>=20
>> the following happens:
>>=20
>> ...
>> rm -f /nfs/site/home/mnystroe/work/cm3/bin/cm3.cfg
>> rm -f /nfs/site/home/mnystroe/work/cm3/bin/cm3cfg.common
>> rm -f /nfs/site/home/mnystroe/work/cm3/bin/gnuld.common
>> cp -Pv /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-sys/cminsta=
>ll/src/config-no-install/cm3.cfg /nfs/site/home/mnystroe/work/cm3/bin/cm3.c=
>fg
>> =3D=3D package /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-win=
>/import-libs =3D=3D
>>=20
>>  +++ /nfs/site/home/mnystroe/work/cm3/bin/cm3    -build -override -DROOT=
>=3D/nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3 -boot -keep -DM3CC_T=
>ARGET=3DARMEL_LINUX +++
>> --- building in ARMEL_LINUX ---
>>=20
>>  =3D=3D> /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-win/impor=
>t-libs done
>>=20
>> =3D=3D package /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-lib=
>s/m3core =3D=3D
>>=20
>>  +++ /nfs/site/home/mnystroe/work/cm3/bin/cm3    -build -override -DROOT=
>=3D/nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3 -boot -keep -DM3CC_T=
>ARGET=3DARMEL_LINUX +++
>> --- building in ARMEL_LINUX ---
>>=20
>>=20
>> Fatal Error: unrecognized backend mode: C
>>=20
>>  *** execution of [<function _BuildLocalFunction at 0x2aaaab5728c0>] fail=
>ed ***
>>=20
>>=20
>> But if I remove M3_BACKEND_MODE from ARMEL_LINUX and run the same command=
>=2C the following:
>>=20
>> ...
>> rm -f /nfs/site/home/mnystroe/work/cm3/bin/cm3cfg.common
>> rm -f /nfs/site/home/mnystroe/work/cm3/bin/gnuld.common
>> cp -Pv /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-sys/cminsta=
>ll/src/config-no-install/cm3.cfg /nfs/site/home/mnystroe/work/cm3/bin/cm3.c=
>fg
>> =3D=3D package /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-win=
>/import-libs =3D=3D
>>=20
>>  +++ /nfs/site/home/mnystroe/work/cm3/bin/cm3    -build -override -DROOT=
>=3D/nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3 -boot -keep -DM3CC_T=
>ARGET=3DARMEL_LINUX +++
>> --- building in ARMEL_LINUX ---
>>=20
>>  =3D=3D> /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-win/impor=
>t-libs done
>>=20
>> =3D=3D package /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-lib=
>s/m3core =3D=3D
>>=20
>>  +++ /nfs/site/home/mnystroe/work/cm3/bin/cm3    -build -override -DROOT=
>=3D/nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3 -boot -keep -DM3CC_T=
>ARGET=3DARMEL_LINUX +++
>> --- building in ARMEL_LINUX ---
>>=20
>>=20
>> Fatal Error: unrecognized target machine: TARGET =3D ARMEL_LINUX
>>=20
>>  *** execution of [<function _BuildLocalFunction at 0x2aaaab5728c0>] fail=
>ed ***
>>=20
>>=20
> 		 	   		  =
>
>--_0e9e017a-7bf6-48f0-afbe-640bab935860_
>Content-Type: text/html; charset="iso-8859-1"
>Content-Transfer-Encoding: quoted-printable
>
><html>
><head>
><style><!--
>.hmmessage P
>{
>margin:0px=3B
>padding:0px
>}
>body.hmmessage
>{
>font-size: 12pt=3B
>font-family:Calibri
>}
>--></style></head>
><body class=3D'hmmessage'><div dir=3D'ltr'><pre> &gt=3B Fatal Error: unreco=
>gnized backend mode: C<br><br><br>Make sure you ./update.py your main tools=
>et first.<br>Also=2C while the C backend was working a year ago=2C for quit=
>e<br>a while I did not change the builder to know about it directly.<br>I w=
>as going via m3cgcat.<br>So you need to be fairly current=2C or else modify=
> the<br>config files a different way=2C and have it be slower.<br><br><br> =
>- Jay<br></pre><br><br><div>&gt=3B To: jay.krell at cornell.edu<br>&gt=3B CC: =
>m3devel at elegosoft.com<br>&gt=3B Subject: Re: [M3devel] building CM3 on a Ra=
>spberry Pi?<br>&gt=3B Date: Mon=2C 14 Oct 2013 09:40:08 -0700<br>&gt=3B Fro=
>m: mika at async.caltech.edu<br>&gt=3B <br>&gt=3B Jay writes:<br>&gt=3B &gt=3B=
>./../gcc-4.7/libiberty/stack-limit.c:52: error: `u_quad_t' undeclared (firs=
>t=3D<br>&gt=3B &gt=3B use in this function)if [ x"" !=3D3D x ]=3B then \<br=
>>&gt=3B &gt=3B<br>&gt=3B &gt=3B<br>&gt=3B &gt=3BMaybe I removed too much. I=
>.e. libquadmath. That should be easy to fix and/o=3D<br>&gt=3B &gt=3Br swit=
>ch to C backend.<br>&gt=3B &gt=3B<br>&gt=3B &gt=3B<br>&gt=3B &gt=3BI forgot=
>: besides switching the config file: add the parameter "c" to boot1.=3D<br>=
>&gt=3B &gt=3Bpy.<br>&gt=3B &gt=3B<br>&gt=3B &gt=3B<br>&gt=3B <br>&gt=3B If =
>I put in config-no-install/ARMEL_LINUX<br>&gt=3B <br>&gt=3B M3_BACKEND_MODE=
>=3D"C"<br>&gt=3B <br>&gt=3B and run<br>&gt=3B <br>&gt=3B ./boot1.py c ARMEL=
>_LINUX<br>&gt=3B <br>&gt=3B the following happens:<br>&gt=3B <br>&gt=3B ...=
><br>&gt=3B rm -f /nfs/site/home/mnystroe/work/cm3/bin/cm3.cfg<br>&gt=3B rm =
>-f /nfs/site/home/mnystroe/work/cm3/bin/cm3cfg.common<br>&gt=3B rm -f /nfs/=
>site/home/mnystroe/work/cm3/bin/gnuld.common<br>&gt=3B cp -Pv /nfs/site/dis=
>ks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-sys/cminstall/src/config-no-insta=
>ll/cm3.cfg /nfs/site/home/mnystroe/work/cm3/bin/cm3.cfg<br>&gt=3B =3D=3D pa=
>ckage /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-win/import-lib=
>s =3D=3D<br>&gt=3B <br>&gt=3B  +++ /nfs/site/home/mnystroe/work/cm3/bin/cm3=
>    -build -override -DROOT=3D/nfs/site/disks/wdisk.133/mnystroe/cm3-anon-c=
>vs/cm3 -boot -keep -DM3CC_TARGET=3DARMEL_LINUX +++<br>&gt=3B --- building i=
>n ARMEL_LINUX ---<br>&gt=3B <br>&gt=3B  =3D=3D&gt=3B /nfs/site/disks/wdisk.=
>133/mnystroe/cm3-anon-cvs/cm3/m3-win/import-libs done<br>&gt=3B <br>&gt=3B =
>=3D=3D package /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-libs/=
>m3core =3D=3D<br>&gt=3B <br>&gt=3B  +++ /nfs/site/home/mnystroe/work/cm3/bi=
>n/cm3    -build -override -DROOT=3D/nfs/site/disks/wdisk.133/mnystroe/cm3-a=
>non-cvs/cm3 -boot -keep -DM3CC_TARGET=3DARMEL_LINUX +++<br>&gt=3B --- build=
>ing in ARMEL_LINUX ---<br>&gt=3B <br>&gt=3B <br>&gt=3B Fatal Error: unrecog=
>nized backend mode: C<br>&gt=3B <br>&gt=3B  *** execution of [&lt=3Bfunctio=
>n _BuildLocalFunction at 0x2aaaab5728c0&gt=3B] failed ***<br>&gt=3B <br>&gt=
>=3B <br>&gt=3B But if I remove M3_BACKEND_MODE from ARMEL_LINUX and run the=
> same command=2C the following:<br>&gt=3B <br>&gt=3B ...<br>&gt=3B rm -f /n=
>fs/site/home/mnystroe/work/cm3/bin/cm3cfg.common<br>&gt=3B rm -f /nfs/site/=
>home/mnystroe/work/cm3/bin/gnuld.common<br>&gt=3B cp -Pv /nfs/site/disks/wd=
>isk.133/mnystroe/cm3-anon-cvs/cm3/m3-sys/cminstall/src/config-no-install/cm=
>3.cfg /nfs/site/home/mnystroe/work/cm3/bin/cm3.cfg<br>&gt=3B =3D=3D package=
> /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-win/import-libs =3D=
>=3D<br>&gt=3B <br>&gt=3B  +++ /nfs/site/home/mnystroe/work/cm3/bin/cm3    -=
>build -override -DROOT=3D/nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm=
>3 -boot -keep -DM3CC_TARGET=3DARMEL_LINUX +++<br>&gt=3B --- building in ARM=
>EL_LINUX ---<br>&gt=3B <br>&gt=3B  =3D=3D&gt=3B /nfs/site/disks/wdisk.133/m=
>nystroe/cm3-anon-cvs/cm3/m3-win/import-libs done<br>&gt=3B <br>&gt=3B =3D=
>=3D package /nfs/site/disks/wdisk.133/mnystroe/cm3-anon-cvs/cm3/m3-libs/m3c=
>ore =3D=3D<br>&gt=3B <br>&gt=3B  +++ /nfs/site/home/mnystroe/work/cm3/bin/c=
>m3    -build -override -DROOT=3D/nfs/site/disks/wdisk.133/mnystroe/cm3-anon=
>-cvs/cm3 -boot -keep -DM3CC_TARGET=3DARMEL_LINUX +++<br>&gt=3B --- building=
> in ARMEL_LINUX ---<br>&gt=3B <br>&gt=3B <br>&gt=3B Fatal Error: unrecogniz=
>ed target machine: TARGET =3D ARMEL_LINUX<br>&gt=3B <br>&gt=3B  *** executi=
>on of [&lt=3Bfunction _BuildLocalFunction at 0x2aaaab5728c0&gt=3B] failed *=
>**<br>&gt=3B <br>&gt=3B <br></div> 		 	   		  </div></body>
></html>=
>
>--_0e9e017a-7bf6-48f0-afbe-640bab935860_--



More information about the M3devel mailing list