I just merged my makefile-refactor branch into master.

The changes are pretty extensive:

   - The "toolchain" compilation is gone, as is the bulk of the contents of
   host-adapter. Compilation now makes a single pass through everything. In
   general, cross compilation is now achieved by a two-stage compilation with
   separate build directories.
   - The top-level run-build script and the --with-scheme-build
   configuration flag make it easy to do multi-stage compilations.
   - Building from 9.2 now takes two stages: the first stage must be
   configured using --disable-default-plugins. The second stage is built
   normally except that it specifies the first stage using --with-scheme-build.
   - There's a new option to set the compiler's target separately from the
   host. This is to support cross compilation: first build a compiler for the
   target that runs on the host, then use that to cross compile the whole
   system (in a separate build).
   - The cross-compilation targets have been divorced from the main flow.
   When cross compiling, only cross-host is run on the host machine.
   cross-target must be run separately on the target machine.
   - The plugins have been integrated into the top-level configuration. By
   default, edwin, imail, x11, and x11-screen are built. I'm going to do some
   additional work to build x11 and x11-screen only if X support is available.
   The other plugins are not built by default. Plugins are configured using
   --enable/--disable flags to configure.
   - It is possible to run most things, including Edwin, from a build
   directory. Installation is not required.
   - The svm implementation works, with a two-stage compilation.
   - The liarc implementation doesn't work (yet). There's some kind of
   issue with linking the modules.



On Sun, Oct 21, 2018 at 10:22 AM Matt Birkholz <[email protected]>
wrote:

> On Sun, 2018-10-21 at 16:25 +0000, Taylor R Campbell wrote:
> > Fails to build in x11.  Am I doing something wrong?  I see several .h
> > files with `typedef unsigned long SCM;', which doesn't seem right.
>
> I compared the command lines libtool chose for each of us and they are
> identical (modulo whitespace and the placement of the -I/usr/X11R7/
> include option).
>
> Maybe your gcc is newer than my old Ubuntu 18.04 gcc (7.3.0), and now
> redefinition to the same type is an error, not a consistency check.
>
>
_______________________________________________
MIT-Scheme-devel mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/mit-scheme-devel

Reply via email to