Definitely making progress, but not quite there I don't think. Now I'm
getting a segfault:

```
cc -g -Wall -Wreturn-type -Wno-array-bounds -fno-common -fwrapv -arch i486
-g           -I../stage1//include -DNDEBUG -DSYSARCH=\"i386\"
-DSYSOS=\"darwin\"  -fno-strict-aliasing -g
-DPREFIX='"/usr/local/lib/idc/i386-apple-darwin16.1.0/"' libid.c -c -o
../stage1/libid_g.o
/bin/sh -ec '( cd st80;
/Applications/Xcode.app/Contents/Developer/usr/bin/make IDC="../boot/idc
-B../boot/ -O" BIN="../stage1/" )'
../boot/idc -B../boot/ -O  -k -c _object.st -o ../stage1/_object.o
../boot/idc: line 300: 80920 Segmentation fault: 11  $run ${prefix}idc1
-I$prefix $idopts $idflags $infile -o $ccfile
make[2]: *** [../stage1/_object.o] Error 139
make[1]: *** [stage1/st80.so] Error 2
make: *** [all] Error 2
```

By the way I get this both when I try to build for `i386` AND `x86_64`. The
reason I'm trying both is because I have a newer MacBook and, well, I'm
just not sure which one to use. I've learned that Apple has muddied the
waters here. For example:
Running `arch` gives you `i386`
But running `uname -m` gives you `x86_64`.

Now the segfault there might be related to not having these parts
configured properly, but I tried every combination I could think of that
made sense when editing `object/boot/configuration` and I always get this
segfault.

On Fri, Dec 9, 2016 at 3:27 PM, Tim Olson <tim.olson.m...@gmail.com> wrote:

> Ok, it looks like the changes required are limited to the boot/configure
> file and a simple change in gc-7.0/mach_dep.c
>
> I’ve put diff files for these on my Google drive:
>
>         https://drive.google.com/open?id=0B4_HuTz-3Kw0Y3hfTTMxZUZEQkk
>
> You should be able to download those and use them with “patch”, like:
>
>         cd object/boot
>         patch < configure.diff.txt
>
>         cd object/gc-7.0
>         patch < mach_dep.c.diff.txt
>
>         — tim
>
>


-- 
Eric
_______________________________________________
Fonc mailing list
Fonc@mailman.vpri.org
http://mailman.vpri.org/mailman/listinfo/fonc_mailman.vpri.org

Reply via email to