-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Apr 2, 2006, at 12:57 AM, Aaron Sloman wrote:
> Brent writes:
>
>> What's more troubling is the failure to compile certain pop11 files
>> that make use of the syntax: "1.0s0" (single-precision float). The
>> v15.53e compiler supplied in the tarball
>
> Is that the OSX tarball?
Yes.
>> can process these files, but
>> if I rebuild poplog v15.53 from the tarball, or build a poplog v15.6
>> runtime,
>
> Is this cross-compiling from v15.6 on linux, or bootstrapping on OSX
> using a working $popsys/corepop on OSX?
This is bootstrapping v15.53e on OSX using the OSX tarball.
>> it gets stuck processing arith2.p (due to the single-
>> precision float syntax).
>
> I can't work out what's going on here. Is this the history:
>
> cross compile poplog to get a corepop executable that works on OSX
>
> use $popsrc/mksyscomp to create popc.psv (and other .psv files)
> the system saved images in $popsys are built on corepop
>
> run pgcomp (which uses corepop +popc.psv) to compile sources
>
> this gets stuck compiling $popsrc/arith2.p
>
> Does it compile everything else?
I'm sorry. Let me give a better description of my steps:
1. I took the original OSX tarball from your site and unpacked it on
my OSX machine.
2. I then walked through the steps to rebuild corepop and the entire
system, following the steps in http://www.cs.bham.ac.uk/research/
poplog/sysdoc/rebuilding and http://www.cs.bham.ac.uk/research/poplog/
sysdoc/rebuilding-corepop.
3. The only problem I had on this step was the I had to switch to
gcc 3.3, from the gcc 4.0 that is "standard" on OS X 10.4.
4. I was able to rebuild all tools (popc, poplink, poplibr, pop11,
pml, prolog). The poplisp build failed as I mentioned in an earlier
e-mail.
I next tried to update everything to the 15.6 level as follows:
1. I took the 15.6 Linux tarball from the Birmingham site, and
unpacked it on my OSX machine, in a sibling directory to my working
15.53 installation.
2. I ran a recursive diff on the two directories, and merged the OSX-
specific changes into the 15.6 tree.
3. I copied the Mac OS X (PPC) assembly files into the 15.6 directory.
4. I used the 15.53 poplog runtime to rebuild the *.p and *.s files
in v15.6/pop/src (for the 15.6 directory).
5. I used the 15.53 poplog runtime to build the src.[ow]lb files.
6. I used the 15.53 poplog runtime to link the newpop executable
(pglink -safe).
This should give me an approximation of a v15.6 corepop executable
(though it reports as 15.53).
I next built the compiler and tools:
1. I reset my environment variables to point at the v15.6 directories.
2. I then ran "$popsrc/mksyscomp popc". This succeeded.
3. I then did the same for "poplibr" and "poplink". Both succeeded.
Let's call this the end of "Stage 1" bootstrap.
Next, I attempted to use the newly-compiled corepop and popc to build
the system:
1. I rebuilt the *.p/*.s files in v15.6/pop/src (using the v15.6
newpop11 build in the previous section).
2. I attempted to run pglibr, which failed with:
ar: $popobjlib/src.olb: No such file or directory
;;; MISHAP - POPLIBR: ERRORS RUNNING AR/RANLIB (see above)
3. At this point, I can't generate a newpop11, so I copy the
poplink_*.o files over from the 15.53e build (since these aren't
being generated in the v15.6 build) and manually run the
"poplink_cmnd" file.
4. This generates a newpop11, which does not run.
I'll try two things:
1. Check differences that might be affecting the pathing in the OSX
build.
2. The additional build suggestions from your last e-mail.
Thanks,
- -Brent
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (Darwin)
iD8DBQFEMJ1jzGDdrzfvUpURAtyBAJ9oFnZ3EeQN2exBdhq3s6+/ut4LXQCbBq8q
Imiv2LyUs2+LAVjHHwfES98=
=3sle
-----END PGP SIGNATURE-----
|