- cmucl-cvs - mailman3.common-lisp.net

[Git][cmucl/cmucl][master] 2 commits: Fix some incorrect markdown markup
by Raymond Toy 17 Dec '18

17 Dec '18

Raymond Toy pushed to branch master at cmucl / cmucl Commits: 15655145 by Raymond Toy at 2018-12-10T15:02:13Z Fix some incorrect markdown markup - - - - - d9487768 by Raymond Toy at 2018-12-10T15:55:54Z More markup fixes - - - - - 1 changed file: - BUILDING.md Changes: ===================================== BUILDING.md ===================================== @@ -12,13 +12,13 @@ General Requirements In order to build CMU CL, you will need: -a. A working CMU CL binary. There is no way around this requirement! +1. A working CMU CL binary. There is no way around this requirement! This binary can either be for the platform you want to target, in that case you can either recompile or cross-compile, or for another supported platform, in that case you must cross-compile, obviously. -a. A supported C compiler for the C runtime code. +1. A supported C compiler for the C runtime code. Most of the time, this means GNU gcc, though for some ports it means the vendor-supplied C compiler. The compiler must be @@ -27,13 +27,13 @@ a. A supported C compiler for the C runtime code. Note for FreeBSD 10 and above: The build requires gcc (Clang will not work) and the lib32 compatiblity package. -a. GNU make +1. GNU make This has to be available either as gmake or make in your PATH, or the MAKE environment variable has to be set to point to the correct binary. -a. The CMU CL source code +1. The CMU CL source code Here you can either use one of the release source tarballs, or check out the source code directly from the public CMUCL git @@ -48,16 +48,19 @@ Setting up a build environment ------------------------------ 1. Create a base directory and change to it - +``` mkdir cmucl ; cd cmucl - -2.) Fetch the sources and put them into the base directory - +``` +2. Fetch the sources and put them into the base directory +``` tar xzf /tmp/cmucl-source.tar.gz +``` or, if you want to use the git sources directly: +``` git clone https://gitlab.common-lisp.net/cmucl/cmucl.git +``` Whatever you do, the sources must be in a directory named src inside the base directory. Since the build tools keep all @@ -81,7 +84,9 @@ quick guide. Use this to build from a version of CMUCL that is very close to the sources you are trying to build now: +``` bin/build.sh -C "" -o "<name-of-old-lisp> <options-to-lisp>" +``` This will build CMUCL 3 times, each time with the result of the previous build. The last time, the additional libraries like CLX, @@ -100,7 +105,9 @@ quick guide. For these, you can use this: +``` bin/build.sh -C "" -o "<old-lisp>" -B boot1.lisp -B boot2.lisp +``` The bootstrap files listed with the -B option (as many as needed) are loaded in order, so be sure to get them right. @@ -121,9 +128,9 @@ file date of a boot file is later than the version of CMUCL you are building from, then you need to use b) or c) above. You may need to read the bootfiles for additional instructions, if any. -If there are no bootfiles, then you can use a) above. +If there are no bootfiles, then you can use 1. above. -The build.sh script supports other options, and bin/build.sh -? +The `build.sh` script supports other options, and `bin/build.sh -?` will give a quick summary. Read bin/build.sh for more information. @@ -247,195 +254,197 @@ Overview of the included build scripts * bin/build.sh [-123obvuBCU?] -This is the main build script. It essentially calls the other build -scripts described below in the proper sequence to build cmucl from an -existing binary of cmucl. + This is the main build script. It essentially calls the other build + scripts described below in the proper sequence to build cmucl from an + existing binary of cmucl. * bin/create-target.sh target-directory [lisp-variant [motif-variant]] -This script creates a new target directory, which is a shadow of the -source directory, that will contain all the files that are created by -the build process. Thus, each target's files are completely separate -from the src directory, which could, in fact, be read-only. Hence you -can simultaneously build CMUCL for different targets from the same -source directory. - -The first argument is the name of the target directory to create. The -remaining arguments are optional. If they are not given, the script -tries to determine the lisp variant and motif variant from the system -the script is running on. - -The lisp-variant (i.e. the suffix of the src/lisp/Config.* to use as -the target's Config file), and optionally the motif-variant (again the -suffix of the src/motif/server/Config.* file to use as the Config file -for the target's CMUCL/Motif server code). If the lisp-variant is -given but the motif-variant is not, the motif-variant is determined -from the lisp-variant. - -The script will generate the target directory tree, link the relevant -Config files, and generate place-holder files for various files, in -order to ensure proper operation of the other build-scripts. It also -creates a sample setenv.lisp file in the target directory, which is -used by the build and load processes to set up the correct list of -*features* for your target lisp core. - -IMPORTANT: You will normally NOT have to modify the sample setenv.lisp -file, if you are building from a binary that has the desired features. -In fact, the sample has all code commented out, If you want to add or -remove features, you need to include code that puts at least a minimal -set of features onto the list (use PUSHNEW and/or REMOVE). You can -use the current set of *features* of your lisp as a first guide. The -sample setenv.lisp includes a set of features that should work for the -intended configuration. Note also that some adding or removing some -features may require a cross-compile instead of a normal compile. + This script creates a new target directory, which is a shadow of the + source directory, that will contain all the files that are created by + the build process. Thus, each target's files are completely separate + from the src directory, which could, in fact, be read-only. Hence you + can simultaneously build CMUCL for different targets from the same + source directory. + + The first argument is the name of the target directory to create. The + remaining arguments are optional. If they are not given, the script + tries to determine the lisp variant and motif variant from the system + the script is running on. + + The lisp-variant (i.e. the suffix of the src/lisp/Config.* to use as + the target's Config file), and optionally the motif-variant (again the + suffix of the src/motif/server/Config.* file to use as the Config file + for the target's CMUCL/Motif server code). If the lisp-variant is + given but the motif-variant is not, the motif-variant is determined + from the lisp-variant. + + The script will generate the target directory tree, link the relevant + Config files, and generate place-holder files for various files, in + order to ensure proper operation of the other build-scripts. It also + creates a sample setenv.lisp file in the target directory, which is + used by the build and load processes to set up the correct list of + *features* for your target lisp core. + + IMPORTANT: You will normally NOT have to modify the sample setenv.lisp + file, if you are building from a binary that has the desired features. + In fact, the sample has all code commented out, If you want to add or + remove features, you need to include code that puts at least a minimal + set of features onto the list (use PUSHNEW and/or REMOVE). You can + use the current set of *features* of your lisp as a first guide. The + sample setenv.lisp includes a set of features that should work for the + intended configuration. Note also that some adding or removing some + features may require a cross-compile instead of a normal compile. * bin/clean-target.sh [-l] target-directory [more dirs] -Cleans the given target directory, so that all created files will be -removed. This is useful to force recompilation. If the -l flag is -given, then the C runtime is also removed, including all the lisp -executable, any lisp cores, all object files, lisp.nm, internals.h, -and the config file. + Cleans the given target directory, so that all created files will be + removed. This is useful to force recompilation. If the -l flag is + given, then the C runtime is also removed, including all the lisp + executable, any lisp cores, all object files, lisp.nm, internals.h, + and the config file. * bin/build-world.sh target-directory [build-binary] [build-flags...] -Starts a complete world build for the given target, using the lisp -binary/core specified as a build host. The recompilation step will -only recompile changed files, or files for which the fasl files are -missing. It will also not recompile the C runtime code (the lisp -binary). If a (re)compilation of that code is needed, the genesis -step of the world build will inform you of that fact. In that case, -you'll have to use the rebuild-lisp.sh script, and then restart the -world build process with build-world.sh + Starts a complete world build for the given target, using the lisp + binary/core specified as a build host. The recompilation step will + only recompile changed files, or files for which the fasl files are + missing. It will also not recompile the C runtime code (the lisp + binary). If a (re)compilation of that code is needed, the genesis + step of the world build will inform you of that fact. In that case, + you'll have to use the rebuild-lisp.sh script, and then restart the + world build process with build-world.sh * bin/rebuild-lisp.sh target-directory -This script will force a complete recompilation of the C runtime code -of CMU CL (aka the lisp executable). Doing this will necessitate -building a new kernel.core file, using build-world.sh. + This script will force a complete recompilation of the C runtime code + of CMU CL (aka the lisp executable). Doing this will necessitate + building a new kernel.core file, using build-world.sh. * bin/load-world.sh target-directory version -This will finish the CMU CL rebuilding process, by loading the -remaining compiled files generated in the world build process into the -kernel.core file, that also resulted from that process, creating the -final lisp.core file. + This will finish the CMU CL rebuilding process, by loading the + remaining compiled files generated in the world build process into the + kernel.core file, that also resulted from that process, creating the + final lisp.core file. -You have to pass the version string as a second argument. The dumped -core will anounce itself using that string. Please don't use a string -consisting of an official release name only, (e.g. "18d"), since those -are reserved for official release builds. Including the build-date in -ISO8601 format is often a good idea, e.g. "18d+ 2002-05-06" for a -binary that is based on sources current on the 6th May, 2002, which is -post the 18d release. + You have to pass the version string as a second argument. The dumped + core will anounce itself using that string. Please don't use a string + consisting of an official release name only, (e.g. "18d"), since those + are reserved for official release builds. Including the build-date in + ISO8601 format is often a good idea, e.g. "18d+ 2002-05-06" for a + binary that is based on sources current on the 6th May, 2002, which is + post the 18d release. * bin/build-utils.sh target-directory -This script will build auxiliary libraries packaged with CMU CL, -including CLX, CMUCL/Motif, the Motif debugger, inspector, and control -panel, and the Hemlock editor. It will use the lisp executable and -core of the given target. + This script will build auxiliary libraries packaged with CMU CL, + including CLX, CMUCL/Motif, the Motif debugger, inspector, and control + panel, and the Hemlock editor. It will use the lisp executable and + core of the given target. -Note: To build with Motif (clm), you need to have the Motif libraries -available and headers available to build motifd, the clm Motif server. -OpenMotif is known to work. + Note: To build with Motif (clm), you need to have the Motif libraries + available and headers available to build motifd, the clm Motif server. + OpenMotif is known to work. -You may need to adjust the include paths and library paths in -src/motif/server/Config.* to match where Motif is installed if the -paths therein are incorrect. + You may need to adjust the include paths and library paths in + src/motif/server/Config.* to match where Motif is installed if the + paths therein are incorrect. -Unless you intend to use clm and motifd, you can safely ignore the -build failure. Everything else will have been compiled correctly; you -just can't use clm. + Unless you intend to use clm and motifd, you can safely ignore the + build failure. Everything else will have been compiled correctly; you + just can't use clm. * bin/make-dist.sh [-bg] [-G group] [-O owner] target-directory version arch os -This script creates both main and extra distribution tarballs from the -given target directory, using the make-main-dist.sh and -make-extra-dist.sh scripts. The result will be two tar files. One -contains the main distribution including the runtime and lisp.core -with PCL (CLOS); the second contains the extra libraries such as -Gray-streams, simple-streams, CLX, CLM, and Hemlock. + This script creates both main and extra distribution tarballs from the + given target directory, using the make-main-dist.sh and + make-extra-dist.sh scripts. The result will be two tar files. One + contains the main distribution including the runtime and lisp.core + with PCL (CLOS); the second contains the extra libraries such as + Gray-streams, simple-streams, CLX, CLM, and Hemlock. -Some options that are available: + Some options that are available: - -b Use bzip2 compression - -g Use gzip compression - -G group Group to use - -O owner Owner to use + -b Use bzip2 compression + -g Use gzip compression + -G group Group to use + -O owner Owner to use -If you specify both -b and -g, you will get two sets of tarfiles. The --G and -O options will attempt to set the owner and group of the files -when building the tarfiles. This way, when you extract the tarfiles, -the owner and group will be set as specified. You may need to be root -to do this because many Unix systems don't normally let you change the -owner and group of a file. + If you specify both -b and -g, you will get two sets of tarfiles. The + -G and -O options will attempt to set the owner and group of the files + when building the tarfiles. This way, when you extract the tarfiles, + the owner and group will be set as specified. You may need to be root + to do this because many Unix systems don't normally let you change the + owner and group of a file. -The remaining arguments used to create the name of the tarfiles. The -names will have the form: + The remaining arguments used to create the name of the tarfiles. The + names will have the form: +``` cmucl-<version>-<arch>-<os>.tar.bz2 cmucl-<version>-<arch>-<os>.extras.tar.bz2 +``` -Of course, the "bz2" will be "gz" if you specified gzip compression -instead of bzip. + Of course, the "bz2" will be "gz" if you specified gzip compression + instead of bzip. * /bin/make-main-dist.sh target-directory version arch os -This is script is not normally invoked by the user; make-dist will do -it appropriately. + This is script is not normally invoked by the user; make-dist will do + it appropriately. -This script creates a main distribution tarball (both in gzipped and -bzipped variants) from the given target directory. This will include -all the stuff that is normally included in official release tarballs -such as lisp.core and the PCL libraries, including Gray streams and -simple streams. + This script creates a main distribution tarball (both in gzipped and + bzipped variants) from the given target directory. This will include + all the stuff that is normally included in official release tarballs + such as lisp.core and the PCL libraries, including Gray streams and + simple streams. -This is intended to be run from make-dist.sh. + This is intended to be run from make-dist.sh. * bin/make-extra-dist.sh target-directory version arch os -This is script is not normally invoked by the user; make-dist will do -it appropriately. + This is script is not normally invoked by the user; make-dist will do + it appropriately. -This script creates an extra distribution tarball (both in gzipped and -bzipped variants) from the given target directory. This will include -all the stuff that is normally included in official extra release -tarballs, i.e. the auxiliary libraries such as CLX, CLM, and Hemlock. + This script creates an extra distribution tarball (both in gzipped and + bzipped variants) from the given target directory. This will include + all the stuff that is normally included in official extra release + tarballs, i.e. the auxiliary libraries such as CLX, CLM, and Hemlock. -This is intended to be run from make-dist.sh. + This is intended to be run from make-dist.sh. * cross-build-world.sh target-directory cross-directory cross-script [build-binary] [build-flags...] -This is a script that can be used instead of build-world.sh for -cross-compiling CMUCL. In addition to the arguments of build-world.sh -it takes two further required arguments: The name of a directory that -will contain the cross-compiler backend (the directory is created if -it doesn't exist, and must not be the same as the target-directory), -and the name of a Lisp cross-compilation script, which is responsible -for setting up, compiling, and loading the cross-compiler backend. -The latter argument is needed because each host/target combination of -platform's needs slightly different code to produce a working -cross-compiler. - -We include a number of working examples of cross-compiler scripts in -the cross-scripts directory. You'll have to edit the features section -of the given scripts, to specify the features that should be removed -from the current set of features in the host lisp, and those that -should be added, so that the backend features are correct for the -intended target. - -You can look at Eric Marsden's collection of build scripts for the -basis of more cross-compiler scripts. + This is a script that can be used instead of build-world.sh for + cross-compiling CMUCL. In addition to the arguments of build-world.sh + it takes two further required arguments: The name of a directory that + will contain the cross-compiler backend (the directory is created if + it doesn't exist, and must not be the same as the target-directory), + and the name of a Lisp cross-compilation script, which is responsible + for setting up, compiling, and loading the cross-compiler backend. + The latter argument is needed because each host/target combination of + platform's needs slightly different code to produce a working + cross-compiler. + + We include a number of working examples of cross-compiler scripts in + the cross-scripts directory. You'll have to edit the features section + of the given scripts, to specify the features that should be removed + from the current set of features in the host lisp, and those that + should be added, so that the backend features are correct for the + intended target. + + You can look at Eric Marsden's collection of build scripts for the + basis of more cross-compiler scripts. Step-by-Step Example of recompiling CMUCL for OpenBSD ----------------------------------------------------- Set up everything as described in the setup section above. Then execute: - +``` # Create a new target directory structure/config for OpenBSD: bin/create-target.sh openbsd OpenBSD_gencgc OpenBSD @@ -487,10 +496,12 @@ bin/load-world.sh openbsd "18d+ 2002-05-06" # core will announce. Please always put the build-date and some # other information in there, to make it possible to differentiate # those builds from official builds, which only contain the release. +``` Now you should have a new lisp.core, which you can start with - +``` ./openbsd/lisp/lisp -core ./openbsd/lisp/lisp.core -noinit -nositeinit +``` Compiling sources that contain disruptive changes ------------------------------------------------- @@ -693,4 +704,4 @@ In particular steps 3, 4, and 5 can be combined into one by using the -c, -r, and -l options for cross-build-world.sh. The -c option cleans out the targe and cross directories; -r does step 4; and -l does step 5. -=============== + View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/compare/cb825da9cf7aff8f96b81ca7… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/compare/cb825da9cf7aff8f96b81ca7… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][rtoy-update-clx-with-cmucl-fixes] 73 commits: Merge branch 'rtoy-update-clx-with-cmucl-fixes' into 'master'
by Raymond Toy 17 Dec '18

17 Dec '18

Raymond Toy pushed to branch rtoy-update-clx-with-cmucl-fixes at cmucl / cmucl Commits: b464fc94 by Raymond Toy at 2018-01-27T19:52:26Z Merge branch 'rtoy-update-clx-with-cmucl-fixes' into 'master' Update clx from upstream Closes #50 See merge request cmucl/cmucl!31 - - - - - b8841170 by Raymond Toy at 2018-01-27T21:04:52Z Fix #49: CLM crashes When invoking motifd, the program name is #p:'library:motifd". This is passed directly to spawn (a C routine), which only accepts strings. So, before calling spawn, convert the program path to a unix namestring. This allows the example from the bug to run without crashing. - - - - - 87c07e5d by Raymond Toy at 2018-01-28T02:19:56Z Make sure spawn is called with a string The previous commit worked for search lists, but the program could be a string. Take care to convert pathnames to strings so that spawn is always called with a string. - - - - - 99eb4311 by Raymond Toy at 2018-01-28T02:54:17Z Merge branch 'rtoy-fix-49-clm-crash' into 'master' Fix #49: CLM crashes Closes #49 See merge request cmucl/cmucl!32 - - - - - 380759e3 by Raymond Toy at 2018-01-28T05:59:25Z Restore ability to compile in mt19937 rng. - src/tools/worldbuild.lisp - only compile rand-xoroshiro if :random-xoroshiro is a feature - src/tools/worldload.lisp - only load rand-xoroshiro if :random-xoroshiro is a feature - tests/rng.lisp - Add a quick test that the state vector of the *random-state* has the correct type. - - - - - dc4a7e00 by Raymond Toy at 2018-01-29T02:20:20Z Fix #47: Print backquote multiple splices correctly * Print multiple splices correclty without the extra set of parenthesis around each splice. * Add test for this. - - - - - e7f97a5d by Raymond Toy at 2018-01-30T03:04:30Z Merge branch 'rtoy-fix-47-backq-splice-printer' into 'master' Fix #47: Print backquote multiple splices correctly Closes #47 See merge request cmucl/cmucl!33 - - - - - 3acdd1b7 by Raymond Toy at 2018-02-03T16:57:28Z Fix #59: type derivation for decode-float exponent Type derivation for exponent part of decode-float was incorrect. We need to take the absolute value of the argument before deriving the type since the exponent is, of course, independent of the sign of the number. In the test case, the negative interval caused the lower and upper bounds to be reversed, resulting in an invalid interval. - - - - - 62c5f3e9 by Raymond Toy at 2018-02-03T17:03:04Z Add test for issue #59. - - - - - 2292400e by Raymond Toy at 2018-02-04T16:16:35Z Fix typo. double-double-float is in the kernel package - - - - - 4e58e53c by Raymond Toy at 2018-02-04T16:19:13Z Be more careful in computing the decode-float bounds If 0 is the lower bound then the smallest exponent is not for 0, but for the least positive float because of denormals. Also handle exclusive bounds. - - - - - 7b336362 by Raymond Toy at 2018-02-04T16:19:37Z Add more tests decode-float. - - - - - 90df7817 by Raymond Toy at 2018-02-04T18:46:50Z Merge branch 'rtoy-fix-59-derive-decode-float' into 'master' Fix #59: derive decode float Closes #59 See merge request cmucl/cmucl!34 - - - - - 894e18e0 by Raymond Toy at 2018-02-10T16:52:20Z Update from logs - - - - - e3c4759d by Philip Fominykh at 2018-02-13T05:20:33Z Restore hevea support for buliding cmu-user - - - - - 3be1f5ba by Philip Fominykh at 2018-02-13T05:22:15Z Improved function signature rendering in cmu-user html version - - - - - 26e3ad82 by Raymond Toy at 2018-02-18T03:44:02Z Fix #60: `C::%UNARY-FROUND` is undefined Remove the symbol `C::%UNARY-FROUND` and just let the compiler package inherit it from the kernel package. * src/bootfiles/21c/boot-2018-02-1.lisp * Use this to bootstrap the change (by uninterning the symbol) * src/code/float.lisp * Just export %unary-fround * src/general-info/release-21d.md * Update * tests/issues.lisp * Add test for this issue - - - - - 84d9a4bd by Raymond Toy at 2018-02-18T03:56:32Z Oops. Need to build with the bootstrap file. - - - - - 31c6bf9f by Raymond Toy at 2018-02-18T15:30:51Z Merge branch 'rtoy-fix-60-unary-fround-undefined' into 'master' Fix #60: unary fround undefined Closes #60 See merge request cmucl/cmucl!36 - - - - - bccd6a98 by Raymond Toy at 2018-02-18T17:01:08Z Fix #58: Bogus type error in comparison of complex number with `THE` form The deftransforms `upgraded-complex-real-contagion-arg1` and `upgraded-complex-real-contagion-arg2` were coercing the complex number to the exact type of the float number. Because of the `THE` form, the type of the float was `(member 1d0)`, so the compiler was coercing `#c(1/2 1/2)` to `(complex (double-float 1d0))`, which is wrong. Therefore, coerce the complex to just the type format of the real part, ignoring any bounds. * src/compiler/float-tran.lisp * Coerce to format type, discarding any bounds * src/general-info/release-21d.md * Update notes * tests/issues.lisp * Added test for this - - - - - 771fd903 by Raymond Toy at 2018-02-18T17:11:19Z Merge branch 'rtoy-fix-issue-58' into 'master' Fix #58: Bogus type error in comparison of complex number with `THE` form Closes #58 See merge request cmucl/cmucl!37 - - - - - e9a598e5 by Raymond Toy at 2018-02-19T16:41:07Z Complex array accessors are not foldable Fixes #61 and #62. The `ARRAY-HAS-FILL-POINTER-P` and `ARRAY-DISPLACEMENT` functions are declared inline and the compiler tries to constant-fold these inlined functions operating on simple arrays. Thus don't allow the compiler to constant-fold calls to `%ARRAY-FILL-POINTER-P`. This is normally protected by a call to `ARRAY-HEADER-P`, but when it's inlined, the compiler tries to constant-fold `%ARRAY-FILL-POINTER-P` on an array without such a slot. Likewise `ARRAY-DISPLACEMENT` calls `%ARRAY-DISPLACED-P`, `%ARRAY-DATA-VECTOR`, and `%ARRAY-DISPLACEMENT`, and the calls are protected by `ARRAY-HEADER-P`. So don't constant-fold these either. Maybe we could also make CONSTANT-FOLD-CALL be smarter about this? * src/compiler/generic/objdef.lisp * Remove flushable from these ref-trans methods. * src/general-info/release-21d.md * Update * tests/issues.lisp * Add tests from the bug reports. - - - - - ac4b9fc8 by Raymond Toy at 2018-02-19T16:50:47Z Merge branch 'rtoy-fix-61-62-not-flushable' into 'master' Complex array accessors are not foldable Closes #61 and #62 See merge request cmucl/cmucl!38 - - - - - 3c56ed8c by Raymond Toy at 2018-03-03T22:28:53Z Remove test files from tests The tests create some files in /tmp. Remove them when the test script ends so that we get a clean directory. I think this fixes the issue with the osx-runner sometimes failing because it can't remove the temp files that I created locally when testing locally. - - - - - 52a93a05 by Raymond Toy at 2018-03-03T22:30:47Z Use the 2018-03 snapshots for testing. - - - - - ccd159f1 by Philip Fominykh at 2018-03-05T05:59:37Z Remove extra paragraph generation in Hevea definitions. Added argument #5 to \layout to act as prelude. Putting index and spacing commands there eliminates extra paragraph. - - - - - 7b9be9a8 by Philip Fominykh at 2018-03-05T06:01:53Z Hevea cmu-user generation cleanups. - - - - - 9b55c3e4 by Philip Fominykh at 2018-03-05T06:03:02Z Merge branch 'master' into pfominykh-cmu-user-fixes - - - - - efc3d8c5 by Raymond Toy at 2018-03-06T04:18:37Z Merge branch 'pfominykh-cmu-user-fixes' into 'master' Restore hevea support for cmu-user See merge request cmucl/cmucl!35 - - - - - 3c749f8b by Raymond Toy at 2018-03-14T22:47:15Z Update manual date to 21c Just change the date on the manual to the date of the 21c release. Now that we can create the html pages again with hevea, we can update this. - - - - - 23e31483 by Raymond Toy at 2018-05-12T17:40:12Z ASDF 3.3.2 - - - - - 90d8b4b5 by Raymond Toy at 2018-07-04T16:54:08Z Bignum multiply without consing temp space The current bignum multiplier creates temp space to hold the absolute value of the bignums and then negates the result (in-place) at the end. Instead, use the algorithm from Hacker's Delight that pretends the numbers are unsigned, does the unsigned multiply and finally corrects the result. No extra memory is needed for this. - - - - - e6b95b82 by Raymond Toy at 2018-07-04T19:21:25Z Add simple test - - - - - 3af22f92 by Raymond Toy at 2018-07-04T19:40:30Z Add some timing code, but not for tests. - - - - - d652bd09 by Raymond Toy at 2018-07-04T20:31:21Z Rename functions to use the new version by default. Update tests to reflect the change in names. - - - - - be073d06 by Raymond Toy at 2018-07-07T17:41:33Z Use fixed ubuntu image - - - - - 01fa37d8 by Raymond Toy at 2018-07-07T19:01:45Z Use Ubuntu 14.04 Let's see if 14.04 works better. I don't feel like debugging the test failure in a VM right now. And I don't want to set up everything to use Fedora (which is what my linux box is running). - - - - - 0f0ac0b6 by Raymond Toy at 2018-07-15T17:45:08Z Add tests with fixed operands - - - - - 228359b6 by Raymond Toy at 2018-07-15T20:47:44Z Refactor common code into a routine The code for applying the correction is pretty much identical for each negative operant, so add a routine to do that. - - - - - cb6e99a3 by Raymond Toy at 2018-07-15T23:01:01Z Disable test issue.41.1 - - - - - 833fef6d by Raymond Toy at 2018-07-16T00:04:01Z Merge branch 'rtoy-bignum-mult-less-consing' into 'master' Reduce consing in bignum multiplier See merge request cmucl/cmucl!39 - - - - - 50b1201e by Raymond Toy at 2018-07-18T05:06:14Z Use ubuntu 16.04 image for testing - - - - - 05f11fa5 by Raymond Toy at 2018-07-21T03:38:57Z Issue #64: Disable test when running CI - - - - - 576fc79d by Raymond Toy at 2018-07-21T03:38:57Z Merge branch 'rtoy-issue-64' into 'master' Issue #64: Disable test when running CI See merge request cmucl/cmucl!40 - - - - - 0a2e45d4 by Raymond Toy at 2018-07-22T01:03:44Z Default RNG for x86 and sparc is :random-xoroshiro Replace :random-mt19937 with :random-xoroshiro in the cross-compile scripts. - - - - - 4915f467 by Raymond Toy at 2018-07-22T17:14:55Z Remove unused vars in WITH-FLOAT-TRAPS macro* The TRAPS and EXCEPTION vars in the WITH-FLOAT-TRAPS were unused. Remove them. Also add some tests for WITH-FLOAT-TRAPS-MASKED to verify that the traps are masked. - - - - - 0c427fc1 by Raymond Toy at 2018-07-27T17:51:02Z Remove extra closing paren - - - - - cb251bbe by Raymond Toy at 2018-08-05T01:46:45Z Export more symbols in defpackage for xlib. The compiler complained that these symbols were also being exported from the XLIB package. Just add them to the defpackage to silence the warnings. - - - - - 7c79326d by Raymond Toy at 2018-08-05T01:50:55Z Add %UNARY-FROUND to exports of defpackage for KERNEL. - - - - - 2de12cd7 by Raymond Toy at 2018-08-05T23:46:44Z Fix compiler warning clang complains: warning: incompatible pointer to integer conversion passing 'lispobj *' (aka 'unsigned long *') to parameter of type 'lispobj' (aka 'unsigned long'); dereference with * [-Wint-conversion] || in_range_p(addr, control_stack, control_stack_size) So cast control_stack to lispobj. Same complaint for binding_stack too. - - - - - 7a6a0e19 by Raymond Toy at 2018-08-23T00:16:10Z Add template for Bugs - - - - - 1894fbfe by Raymond Toy at 2018-08-23T00:19:24Z Add template for Feature requests - - - - - 14f72f54 by Raymond Toy at 2018-08-23T00:26:05Z Set label correctly. It's a tilde, not dash. - - - - - 1d6d12de by Raymond Toy at 2018-08-23T00:27:01Z Set label to feature - - - - - 82bf2c72 by Raymond Toy at 2018-08-25T23:51:54Z Add support for compiling with clang on x86/linux Add `Config.x86_linux_clang` to use clang instead of gcc to build cmucl. update `create-target.sh` so that it sets the motif variant correctly when using `Config.x86_linux_clang` See issue #68. With this config, Fedora 28 successfully builds cmucl and passes all the tests. - - - - - 9d2590c0 by Raymond Toy at 2018-08-28T22:00:19Z Get rid of FPU_MODE This was used to selecte whether we were building for x87 or sse2, but we dropped support for x87 a long while ago. Remove this var. - - - - - d7f49e51 by Raymond Toy at 2018-09-01T16:53:24Z Oops. Forgot to remove one more FPU_MODE - - - - - 7b4e019d by Raymond Toy at 2018-09-22T19:50:40Z Fix #69: Always compile in GC assertion code - - - - - 9cb80666 by Raymond Toy at 2018-09-22T19:50:40Z Merge branch 'issue-69-compile-in-gc-assert' into 'master' Fix #69: Always compile in GC assertion code Closes #69 See merge request cmucl/cmucl!41 - - - - - 925241a9 by Raymond Toy at 2018-09-22T19:57:52Z Fix some typos in comment. - - - - - 08a948e1 by Raymond Toy at 2018-09-22T20:02:05Z Update from commit logs - - - - - 810c52ea by Raymond Toy at 2018-10-07T21:10:41Z Define control_stack_end for all platforms - - - - - f471f66e by Raymond Toy at 2018-10-07T23:51:45Z Update with new docstring - - - - - 741b6176 by Raymond Toy at 2018-10-12T17:16:40Z Update translation files - - - - - b6faace8 by Raymond Toy at 2018-10-12T18:20:56Z Update notes - - - - - 0824e61e by Raymond Toy at 2018-12-06T22:42:16Z Fix #71: More info from machine-type/version on x86 - - - - - 3843a50c by Raymond Toy at 2018-12-06T22:42:16Z Merge branch 'rtoy-issue-71' into 'master' Fix #71: More info from machine-type/version on x86 Closes #71 See merge request cmucl/cmucl!42 - - - - - 6167e353 by Raymond Toy at 2018-12-08T16:58:15Z Update version numbers for 21d. - - - - - b664e46d by Raymond Toy at 2018-12-08T16:58:15Z Merge branch '21d-branch' into 'master' Update version numbers for 21d. See merge request cmucl/cmucl!43 - - - - - cb825da9 by Raymond Toy at 2018-12-10T14:53:27Z Rename BUILDING to BUILDIND.md and convert to markdown Initial conversion of BUILDING to markdown. - - - - - 15655145 by Raymond Toy at 2018-12-10T15:02:13Z Fix some incorrect markdown markup - - - - - d9487768 by Raymond Toy at 2018-12-10T15:55:54Z More markup fixes - - - - - 5e075fa0 by Raymond Toy at 2018-12-17T02:49:54Z Merge branch 'master' into rtoy-update-clx-with-cmucl-fixes - - - - - 30 changed files: - .gitlab-ci.yml - + .gitlab/issue_templates/Bug.md - + .gitlab/issue_templates/Feature.md - BUILDING → BUILDING.md - bin/build.sh - bin/create-target.sh - bin/run-tests.sh - + src/bootfiles/21c/boot-2018-02-1.lisp - + src/bootfiles/21c/boot-21d.lisp - src/clx/package.lisp - src/code/backq.lisp - src/code/bignum.lisp - src/code/exports.lisp - src/code/float-trap.lisp - src/code/float.lisp - src/code/gc.lisp - src/code/rand-xoroshiro.lisp - src/code/run-program.lisp - src/code/x86-vm.lisp - src/compiler/byte-comp.lisp - src/compiler/float-tran.lisp - src/compiler/generic/objdef.lisp - src/contrib/asdf/asdf.lisp - src/contrib/asdf/doc/asdf.html - src/contrib/asdf/doc/asdf.info - src/contrib/asdf/doc/asdf.pdf - src/docs/cmu-user/Makefile - src/docs/cmu-user/aliens.tex - src/docs/cmu-user/cmu-user.hva - src/docs/cmu-user/cmu-user.tex The diff was not included because it is too large. View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/compare/6c18cc63ba3b98ede7c16026… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/compare/6c18cc63ba3b98ede7c16026… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][rtoy-update-clx-with-cmucl-fixes] 3 commits: Import upstream clx version 0.7.5-19-g623c339
by Raymond Toy 17 Dec '18

17 Dec '18

Raymond Toy pushed to branch rtoy-update-clx-with-cmucl-fixes at cmucl / cmucl Commits: 60bde987 by Raymond Toy at 2018-12-16T23:58:32Z Import upstream clx version 0.7.5-19-g623c339 Straight copy of sharplispers/clx commit 623c339 - - - - - 48bc44d6 by Raymond Toy at 2018-12-17T00:00:09Z Merge branch 'upstream-clx' into rtoy-update-clx-with-cmucl-fixes - - - - - 6c18cc63 by Raymond Toy at 2018-12-17T00:45:58Z Compile clx files in the same order as in clx.asd Ran contrib-demos as a test of clx and everything appears to work correctly. - - - - - 3 changed files: - src/clx/depdefs.lisp - src/clx/manual/clx.texinfo - src/tools/clxcom.lisp Changes: ===================================== src/clx/depdefs.lisp ===================================== @@ -387,9 +387,7 @@ ;; FIXME: maybe we should reevaluate this? (defvar *def-clx-class-use-defclass* #+(or Genera allegro) t - #+(and cmu pcl) '(XLIB:DRAWABLE XLIB:WINDOW XLIB:PIXMAP) - #+(and cmu (not pcl)) nil - #-(or Genera cmu allegro) nil + #-(or Genera allegro) nil "Controls whether DEF-CLX-CLASS uses DEFCLASS. If it is a list, it is interpreted by DEF-CLX-CLASS to be a list of ===================================== src/clx/manual/clx.texinfo ===================================== @@ -15162,11 +15162,11 @@ a keycode. @item Convert the keycode into its corresponding keysym, based on the -current keyboard mapping. See @var{keycode->keysym}. +current keyboard mapping. See @var{keycode->keysym}. @item Convert the keysym into the corresponding Common Lisp character. See -@var{keysym->character}. +@var{keysym->character}. @end enumerate @menu ===================================== src/tools/clxcom.lisp ===================================== @@ -75,9 +75,15 @@ (comf "target:clx/extensions/glx" :load t) (comf "target:clx/extensions/gl" :load t) (comf "target:clx/extensions/dpms" :load t) + (comf "target:clx/extensions/xtest" :load t) (comf "target:clx/extensions/screensaver" :load t) + (comf "target:clx/extensions/randr" :load t) (comf "target:clx/extensions/xinerama" :load t) - (comf "target:clx/extensions/xtest" :load t)) + (comf "target:clx/extensions/dbe" :load t) + (comf "target:clx/extensions/xc-misc" :load t) + (comf "target:clx/extensions/dri2" :load t) + (comf "target:clx/extensions/composite" :load t) + ) (comf "target:code/clx-ext") (comf "target:hemlock/charmacs" :load t) (comf "target:hemlock/key-event" :load t) View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/compare/81e08b4c44f842db6e07cf64… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/compare/81e08b4c44f842db6e07cf64… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][rtoy-update-clx-with-cmucl-fixes] 3 commits: Update to upstream version 0.7.5-17-g1f2b6f3
by Raymond Toy 16 Dec '18

16 Dec '18

Raymond Toy pushed to branch rtoy-update-clx-with-cmucl-fixes at cmucl / cmucl Commits: dded48c6 by Raymond Toy at 2018-12-16T17:44:37Z Update to upstream version 0.7.5-17-g1f2b6f3 This is a copy of the upstream version, unchanged. - - - - - 3688d64c by Raymond Toy at 2018-12-16T18:00:42Z Merge branch 'upstream-clx' into rtoy-update-clx-with-cmucl-fixes # Conflicts: # src/clx/dependent.lisp # src/clx/macros.lisp - - - - - 81e08b4c by Raymond Toy at 2018-12-16T18:05:02Z Update extensions with upstream The merge with upstream had conflicts in extensions/shape.lisp and extensions/xrender.lisp and the new files were added as shape.lisp~ upstream-clx and xrender.lisp~upstream-clx. Just copy these files over the existing ones. - - - - - 28 changed files: - src/clx/CHANGES - src/clx/NEWS - src/clx/README-R5 - + src/clx/README.md - + src/clx/ci-doc-gh-pages.sh - src/clx/clx.asd - src/clx/debug/debug.lisp - src/clx/debug/describe.lisp - src/clx/debug/event-test.lisp - src/clx/debug/keytrans.lisp - src/clx/debug/trace.lisp - src/clx/debug/util.lisp - + src/clx/demo/image.lisp - + src/clx/demo/trapezoid.lisp - src/clx/dep-allegro.lisp - src/clx/dep-lispworks.lisp - src/clx/dep-openmcl.lisp - src/clx/dependent.lisp - src/clx/exclMakefile - src/clx/exclREADME - src/clx/excldep.c - + src/clx/extensions/composite.lisp - + src/clx/extensions/dbe.lisp - + src/clx/extensions/dri2.lisp - + src/clx/extensions/randr.lisp - src/clx/extensions/shape.lisp - + src/clx/extensions/xc-misc.lisp - src/clx/extensions/xrender.lisp The diff was not included because it is too large. View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/compare/d10aa4a6e7edcf8e6254cb88… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/compare/d10aa4a6e7edcf8e6254cb88… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][upstream-clx] Import upstream clx version 0.7.5-19-g623c339
by Raymond Toy 16 Dec '18

16 Dec '18

Raymond Toy pushed to branch upstream-clx at cmucl / cmucl Commits: 60bde987 by Raymond Toy at 2018-12-16T23:58:32Z Import upstream clx version 0.7.5-19-g623c339 Straight copy of sharplispers/clx commit 623c339 - - - - - 4 changed files: - src/clx/README-CMUCL - src/clx/depdefs.lisp - src/clx/dependent.lisp - src/clx/manual/clx.texinfo Changes: ===================================== src/clx/README-CMUCL ===================================== @@ -1,40 +1,9 @@ -$Id: README-CMUCL,v 1.2 2009/06/11 16:03:56 rtoy Rel $ +This is an import of Telent-CLX from the fork +https://github.com/sharplispers/clx, version +6e39a0df2a0a1d083166f405d4b8bbc463d54d85. -This is an import of Telent-CLX as of 0.7.3. +All (almost?) files are included. A few changes to fix bugs related +to CMUCL have been added, as well as the CVS id. I've tried to make +few changes so it will be easy to merge again when desired. -All files are included. A few changes to fix bugs related to CMUCL -have been added, as well as the CVS id. I've tried to make few -changes so it will be easy to merge again when desired. - -The following files from this directory are compiled and loaded by -CMUCL when it builds utilities: - -clx-library.lisp -package.lisp -depdefs.lisp -clx.lisp -dependent.lisp -macros.lisp -bufmac.lisp -buffer.lisp -display.lisp -gcontext.lisp -input.lisp -requests.lisp -fonts.lisp -graphics.lisp -text.lisp -attributes.lisp -translate.lisp -keysyms.lisp -manager.lisp -image.lisp -resource.lisp -shape.lisp -big-requests.lisp -xvidmode.lisp -xrender.lisp -glx.lisp -gl.lisp -dpms.lisp -provide.lisp +See src/tools/clxcom.lisp to see what files are compiled. ===================================== src/clx/depdefs.lisp ===================================== @@ -387,9 +387,7 @@ ;; FIXME: maybe we should reevaluate this? (defvar *def-clx-class-use-defclass* #+(or Genera allegro) t - #+(and cmu pcl) '(XLIB:DRAWABLE XLIB:WINDOW XLIB:PIXMAP) - #+(and cmu (not pcl)) nil - #-(or Genera cmu allegro) nil + #-(or Genera allegro) nil "Controls whether DEF-CLX-CLASS uses DEFCLASS. If it is a list, it is interpreted by DEF-CLX-CLASS to be a list of ===================================== src/clx/dependent.lisp ===================================== @@ -884,6 +884,47 @@ :element-type '(unsigned-byte 8) :input t :output t :buffering :none)) +#+cmu +(defun open-x-stream (host display protocol) + (let ((stream-fd + (ecase protocol + ;; establish a TCP connection to the X11 server, which is + ;; listening on port 6000 + display-number + ((:internet :tcp nil) + (let ((fd (ext:connect-to-inet-socket host (+ *x-tcp-port* display)))) + (unless (plusp fd) + (error 'connection-failure + :major-version *protocol-major-version* + :minor-version *protocol-minor-version* + :host host + :display display + :reason (format nil "Cannot connect to internet socket: ~S" + (unix:get-unix-error-msg)))) + fd)) + ;; establish a connection to the X11 server over a Unix + ;; socket. (:|| comes from Darwin's weird DISPLAY + ;; environment variable) + ((:unix :local :||) + (let ((path (unix-socket-path-from-host host display))) + (unless (probe-file path) + (error 'connection-failure + :major-version *protocol-major-version* + :minor-version *protocol-minor-version* + :host host + :display display + :reason (format nil "Unix socket ~s does not exist" path))) + (let ((fd (ext:connect-to-unix-socket (namestring path)))) + (unless (plusp fd) + (error 'connection-failure + :major-version *protocol-major-version* + :minor-version *protocol-minor-version* + :host host + :display display + :reason (format nil "Can't connect to unix socket: ~S" + (unix:get-unix-error-msg)))) + fd)))))) + (system:make-fd-stream stream-fd :input t :output t :element-type '(unsigned-byte 8)))) + ;;; BUFFER-READ-DEFAULT for CMU Common Lisp. ;;; ;;; If timeout is 0, then we call LISTEN to see if there is any input. @@ -1643,7 +1684,7 @@ Returns a list of (host display-number screen protocol)." (defmacro with-underlying-simple-vector ((variable element-type pixarray) &body body) (declare (ignore element-type)) - `(#+cmu kernel::with-array-data #+sbcl sb-kernel:with-array-data + `(#+cmu lisp::with-array-data #+sbcl sb-kernel:with-array-data ((,variable ,pixarray) (start) (end)) (declare (ignore start end)) ,@body)) @@ -1762,11 +1803,11 @@ Returns a list of (host display-number screen protocol)." height width) (declare (type array-index source-width sx sy dest-width dx dy height width)) #.(declare-buffun) - (kernel::with-array-data ((sdata source) + (lisp::with-array-data ((sdata source) (sstart) (send)) (declare (ignore send)) - (kernel::with-array-data ((ddata dest) + (lisp::with-array-data ((ddata dest) (dstart) (dend)) (declare (ignore dend)) ===================================== src/clx/manual/clx.texinfo ===================================== @@ -15162,11 +15162,11 @@ a keycode. @item Convert the keycode into its corresponding keysym, based on the -current keyboard mapping. See @var{keycode->keysym}. +current keyboard mapping. See @var{keycode->keysym}. @item Convert the keysym into the corresponding Common Lisp character. See -@var{keysym->character}. +@var{keysym->character}. @end enumerate @menu View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/60bde987869e73a25475727ac… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/60bde987869e73a25475727ac… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][upstream-clx] Update to upstream version 0.7.5-17-g1f2b6f3
by Raymond Toy 16 Dec '18

16 Dec '18

Raymond Toy pushed to branch upstream-clx at cmucl / cmucl Commits: dded48c6 by Raymond Toy at 2018-12-16T17:44:37Z Update to upstream version 0.7.5-17-g1f2b6f3 This is a copy of the upstream version, unchanged. - - - - - 30 changed files: - src/clx/CHANGES - src/clx/NEWS - src/clx/README-R5 - + src/clx/README.md - + src/clx/ci-doc-gh-pages.sh - src/clx/clx.asd - src/clx/debug/debug.lisp - src/clx/debug/describe.lisp - src/clx/debug/event-test.lisp - src/clx/debug/keytrans.lisp - src/clx/debug/trace.lisp - src/clx/debug/util.lisp - src/clx/demo/bezier.lisp - src/clx/demo/beziertest.lisp - src/clx/demo/clclock.lisp - src/clx/demo/clipboard.lisp - src/clx/demo/clx-demos.lisp - src/clx/demo/gl-test.lisp - src/clx/demo/hello.lisp - + src/clx/demo/image.lisp - src/clx/demo/mandel.lisp - + src/clx/demo/trapezoid.lisp - src/clx/dep-allegro.lisp - src/clx/dep-lispworks.lisp - src/clx/dep-openmcl.lisp - src/clx/dependent.lisp - src/clx/exclMakefile - src/clx/exclREADME - src/clx/excldep.c - + src/clx/extensions/big-requests.lisp The diff was not included because it is too large. View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/dded48c6a9b7cd7a3f5ac066f… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/dded48c6a9b7cd7a3f5ac066f… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl] Pushed new branch upstream-clx
by Raymond Toy 16 Dec '18

16 Dec '18

Raymond Toy pushed new branch upstream-clx at cmucl / cmucl -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/tree/upstream-clx You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][master] More markup fixes
by Raymond Toy 10 Dec '18

10 Dec '18

Raymond Toy pushed to branch master at cmucl / cmucl Commits: d9487768 by Raymond Toy at 2018-12-10T15:55:54Z More markup fixes - - - - - 1 changed file: - BUILDING.md Changes: ===================================== BUILDING.md ===================================== @@ -48,17 +48,20 @@ Setting up a build environment ------------------------------ 1. Create a base directory and change to it - +``` mkdir cmucl ; cd cmucl - +``` 2. Fetch the sources and put them into the base directory ``` tar xzf /tmp/cmucl-source.tar.gz ``` + or, if you want to use the git sources directly: + ``` git clone https://gitlab.common-lisp.net/cmucl/cmucl.git ``` + Whatever you do, the sources must be in a directory named src inside the base directory. Since the build tools keep all generated files in separate target directories, the src directory @@ -81,7 +84,9 @@ quick guide. Use this to build from a version of CMUCL that is very close to the sources you are trying to build now: +``` bin/build.sh -C "" -o "<name-of-old-lisp> <options-to-lisp>" +``` This will build CMUCL 3 times, each time with the result of the previous build. The last time, the additional libraries like CLX, @@ -100,7 +105,9 @@ quick guide. For these, you can use this: +``` bin/build.sh -C "" -o "<old-lisp>" -B boot1.lisp -B boot2.lisp +``` The bootstrap files listed with the -B option (as many as needed) are loaded in order, so be sure to get them right. @@ -121,9 +128,9 @@ file date of a boot file is later than the version of CMUCL you are building from, then you need to use b) or c) above. You may need to read the bootfiles for additional instructions, if any. -If there are no bootfiles, then you can use a) above. +If there are no bootfiles, then you can use 1. above. -The build.sh script supports other options, and bin/build.sh -? +The `build.sh` script supports other options, and `bin/build.sh -?` will give a quick summary. Read bin/build.sh for more information. @@ -373,10 +380,12 @@ Overview of the included build scripts The remaining arguments used to create the name of the tarfiles. The names will have the form: + ``` cmucl-<version>-<arch>-<os>.tar.bz2 cmucl-<version>-<arch>-<os>.extras.tar.bz2 ``` + Of course, the "bz2" will be "gz" if you specified gzip compression instead of bzip. @@ -695,4 +704,4 @@ In particular steps 3, 4, and 5 can be combined into one by using the -c, -r, and -l options for cross-build-world.sh. The -c option cleans out the targe and cross directories; -r does step 4; and -l does step 5. -=============== + View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/d94877687e6deab2f08d066f5… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/d94877687e6deab2f08d066f5… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][master] Fix some incorrect markdown markup
by Raymond Toy 10 Dec '18

10 Dec '18

Raymond Toy pushed to branch master at cmucl / cmucl Commits: 15655145 by Raymond Toy at 2018-12-10T15:02:13Z Fix some incorrect markdown markup - - - - - 1 changed file: - BUILDING.md Changes: ===================================== BUILDING.md ===================================== @@ -12,13 +12,13 @@ General Requirements In order to build CMU CL, you will need: -a. A working CMU CL binary. There is no way around this requirement! +1. A working CMU CL binary. There is no way around this requirement! This binary can either be for the platform you want to target, in that case you can either recompile or cross-compile, or for another supported platform, in that case you must cross-compile, obviously. -a. A supported C compiler for the C runtime code. +1. A supported C compiler for the C runtime code. Most of the time, this means GNU gcc, though for some ports it means the vendor-supplied C compiler. The compiler must be @@ -27,13 +27,13 @@ a. A supported C compiler for the C runtime code. Note for FreeBSD 10 and above: The build requires gcc (Clang will not work) and the lib32 compatiblity package. -a. GNU make +1. GNU make This has to be available either as gmake or make in your PATH, or the MAKE environment variable has to be set to point to the correct binary. -a. The CMU CL source code +1. The CMU CL source code Here you can either use one of the release source tarballs, or check out the source code directly from the public CMUCL git @@ -51,14 +51,14 @@ Setting up a build environment mkdir cmucl ; cd cmucl -2.) Fetch the sources and put them into the base directory - +2. Fetch the sources and put them into the base directory +``` tar xzf /tmp/cmucl-source.tar.gz - +``` or, if you want to use the git sources directly: - +``` git clone https://gitlab.common-lisp.net/cmucl/cmucl.git - +``` Whatever you do, the sources must be in a directory named src inside the base directory. Since the build tools keep all generated files in separate target directories, the src directory @@ -247,195 +247,195 @@ Overview of the included build scripts * bin/build.sh [-123obvuBCU?] -This is the main build script. It essentially calls the other build -scripts described below in the proper sequence to build cmucl from an -existing binary of cmucl. + This is the main build script. It essentially calls the other build + scripts described below in the proper sequence to build cmucl from an + existing binary of cmucl. * bin/create-target.sh target-directory [lisp-variant [motif-variant]] -This script creates a new target directory, which is a shadow of the -source directory, that will contain all the files that are created by -the build process. Thus, each target's files are completely separate -from the src directory, which could, in fact, be read-only. Hence you -can simultaneously build CMUCL for different targets from the same -source directory. - -The first argument is the name of the target directory to create. The -remaining arguments are optional. If they are not given, the script -tries to determine the lisp variant and motif variant from the system -the script is running on. - -The lisp-variant (i.e. the suffix of the src/lisp/Config.* to use as -the target's Config file), and optionally the motif-variant (again the -suffix of the src/motif/server/Config.* file to use as the Config file -for the target's CMUCL/Motif server code). If the lisp-variant is -given but the motif-variant is not, the motif-variant is determined -from the lisp-variant. - -The script will generate the target directory tree, link the relevant -Config files, and generate place-holder files for various files, in -order to ensure proper operation of the other build-scripts. It also -creates a sample setenv.lisp file in the target directory, which is -used by the build and load processes to set up the correct list of -*features* for your target lisp core. - -IMPORTANT: You will normally NOT have to modify the sample setenv.lisp -file, if you are building from a binary that has the desired features. -In fact, the sample has all code commented out, If you want to add or -remove features, you need to include code that puts at least a minimal -set of features onto the list (use PUSHNEW and/or REMOVE). You can -use the current set of *features* of your lisp as a first guide. The -sample setenv.lisp includes a set of features that should work for the -intended configuration. Note also that some adding or removing some -features may require a cross-compile instead of a normal compile. + This script creates a new target directory, which is a shadow of the + source directory, that will contain all the files that are created by + the build process. Thus, each target's files are completely separate + from the src directory, which could, in fact, be read-only. Hence you + can simultaneously build CMUCL for different targets from the same + source directory. + + The first argument is the name of the target directory to create. The + remaining arguments are optional. If they are not given, the script + tries to determine the lisp variant and motif variant from the system + the script is running on. + + The lisp-variant (i.e. the suffix of the src/lisp/Config.* to use as + the target's Config file), and optionally the motif-variant (again the + suffix of the src/motif/server/Config.* file to use as the Config file + for the target's CMUCL/Motif server code). If the lisp-variant is + given but the motif-variant is not, the motif-variant is determined + from the lisp-variant. + + The script will generate the target directory tree, link the relevant + Config files, and generate place-holder files for various files, in + order to ensure proper operation of the other build-scripts. It also + creates a sample setenv.lisp file in the target directory, which is + used by the build and load processes to set up the correct list of + *features* for your target lisp core. + + IMPORTANT: You will normally NOT have to modify the sample setenv.lisp + file, if you are building from a binary that has the desired features. + In fact, the sample has all code commented out, If you want to add or + remove features, you need to include code that puts at least a minimal + set of features onto the list (use PUSHNEW and/or REMOVE). You can + use the current set of *features* of your lisp as a first guide. The + sample setenv.lisp includes a set of features that should work for the + intended configuration. Note also that some adding or removing some + features may require a cross-compile instead of a normal compile. * bin/clean-target.sh [-l] target-directory [more dirs] -Cleans the given target directory, so that all created files will be -removed. This is useful to force recompilation. If the -l flag is -given, then the C runtime is also removed, including all the lisp -executable, any lisp cores, all object files, lisp.nm, internals.h, -and the config file. + Cleans the given target directory, so that all created files will be + removed. This is useful to force recompilation. If the -l flag is + given, then the C runtime is also removed, including all the lisp + executable, any lisp cores, all object files, lisp.nm, internals.h, + and the config file. * bin/build-world.sh target-directory [build-binary] [build-flags...] -Starts a complete world build for the given target, using the lisp -binary/core specified as a build host. The recompilation step will -only recompile changed files, or files for which the fasl files are -missing. It will also not recompile the C runtime code (the lisp -binary). If a (re)compilation of that code is needed, the genesis -step of the world build will inform you of that fact. In that case, -you'll have to use the rebuild-lisp.sh script, and then restart the -world build process with build-world.sh + Starts a complete world build for the given target, using the lisp + binary/core specified as a build host. The recompilation step will + only recompile changed files, or files for which the fasl files are + missing. It will also not recompile the C runtime code (the lisp + binary). If a (re)compilation of that code is needed, the genesis + step of the world build will inform you of that fact. In that case, + you'll have to use the rebuild-lisp.sh script, and then restart the + world build process with build-world.sh * bin/rebuild-lisp.sh target-directory -This script will force a complete recompilation of the C runtime code -of CMU CL (aka the lisp executable). Doing this will necessitate -building a new kernel.core file, using build-world.sh. + This script will force a complete recompilation of the C runtime code + of CMU CL (aka the lisp executable). Doing this will necessitate + building a new kernel.core file, using build-world.sh. * bin/load-world.sh target-directory version -This will finish the CMU CL rebuilding process, by loading the -remaining compiled files generated in the world build process into the -kernel.core file, that also resulted from that process, creating the -final lisp.core file. + This will finish the CMU CL rebuilding process, by loading the + remaining compiled files generated in the world build process into the + kernel.core file, that also resulted from that process, creating the + final lisp.core file. -You have to pass the version string as a second argument. The dumped -core will anounce itself using that string. Please don't use a string -consisting of an official release name only, (e.g. "18d"), since those -are reserved for official release builds. Including the build-date in -ISO8601 format is often a good idea, e.g. "18d+ 2002-05-06" for a -binary that is based on sources current on the 6th May, 2002, which is -post the 18d release. + You have to pass the version string as a second argument. The dumped + core will anounce itself using that string. Please don't use a string + consisting of an official release name only, (e.g. "18d"), since those + are reserved for official release builds. Including the build-date in + ISO8601 format is often a good idea, e.g. "18d+ 2002-05-06" for a + binary that is based on sources current on the 6th May, 2002, which is + post the 18d release. * bin/build-utils.sh target-directory -This script will build auxiliary libraries packaged with CMU CL, -including CLX, CMUCL/Motif, the Motif debugger, inspector, and control -panel, and the Hemlock editor. It will use the lisp executable and -core of the given target. + This script will build auxiliary libraries packaged with CMU CL, + including CLX, CMUCL/Motif, the Motif debugger, inspector, and control + panel, and the Hemlock editor. It will use the lisp executable and + core of the given target. -Note: To build with Motif (clm), you need to have the Motif libraries -available and headers available to build motifd, the clm Motif server. -OpenMotif is known to work. + Note: To build with Motif (clm), you need to have the Motif libraries + available and headers available to build motifd, the clm Motif server. + OpenMotif is known to work. -You may need to adjust the include paths and library paths in -src/motif/server/Config.* to match where Motif is installed if the -paths therein are incorrect. + You may need to adjust the include paths and library paths in + src/motif/server/Config.* to match where Motif is installed if the + paths therein are incorrect. -Unless you intend to use clm and motifd, you can safely ignore the -build failure. Everything else will have been compiled correctly; you -just can't use clm. + Unless you intend to use clm and motifd, you can safely ignore the + build failure. Everything else will have been compiled correctly; you + just can't use clm. * bin/make-dist.sh [-bg] [-G group] [-O owner] target-directory version arch os -This script creates both main and extra distribution tarballs from the -given target directory, using the make-main-dist.sh and -make-extra-dist.sh scripts. The result will be two tar files. One -contains the main distribution including the runtime and lisp.core -with PCL (CLOS); the second contains the extra libraries such as -Gray-streams, simple-streams, CLX, CLM, and Hemlock. - -Some options that are available: - - -b Use bzip2 compression - -g Use gzip compression - -G group Group to use - -O owner Owner to use - -If you specify both -b and -g, you will get two sets of tarfiles. The --G and -O options will attempt to set the owner and group of the files -when building the tarfiles. This way, when you extract the tarfiles, -the owner and group will be set as specified. You may need to be root -to do this because many Unix systems don't normally let you change the -owner and group of a file. - -The remaining arguments used to create the name of the tarfiles. The -names will have the form: - + This script creates both main and extra distribution tarballs from the + given target directory, using the make-main-dist.sh and + make-extra-dist.sh scripts. The result will be two tar files. One + contains the main distribution including the runtime and lisp.core + with PCL (CLOS); the second contains the extra libraries such as + Gray-streams, simple-streams, CLX, CLM, and Hemlock. + + Some options that are available: + + -b Use bzip2 compression + -g Use gzip compression + -G group Group to use + -O owner Owner to use + + If you specify both -b and -g, you will get two sets of tarfiles. The + -G and -O options will attempt to set the owner and group of the files + when building the tarfiles. This way, when you extract the tarfiles, + the owner and group will be set as specified. You may need to be root + to do this because many Unix systems don't normally let you change the + owner and group of a file. + + The remaining arguments used to create the name of the tarfiles. The + names will have the form: +``` cmucl-<version>-<arch>-<os>.tar.bz2 cmucl-<version>-<arch>-<os>.extras.tar.bz2 - -Of course, the "bz2" will be "gz" if you specified gzip compression -instead of bzip. +``` + Of course, the "bz2" will be "gz" if you specified gzip compression + instead of bzip. * /bin/make-main-dist.sh target-directory version arch os -This is script is not normally invoked by the user; make-dist will do -it appropriately. + This is script is not normally invoked by the user; make-dist will do + it appropriately. -This script creates a main distribution tarball (both in gzipped and -bzipped variants) from the given target directory. This will include -all the stuff that is normally included in official release tarballs -such as lisp.core and the PCL libraries, including Gray streams and -simple streams. + This script creates a main distribution tarball (both in gzipped and + bzipped variants) from the given target directory. This will include + all the stuff that is normally included in official release tarballs + such as lisp.core and the PCL libraries, including Gray streams and + simple streams. -This is intended to be run from make-dist.sh. + This is intended to be run from make-dist.sh. * bin/make-extra-dist.sh target-directory version arch os -This is script is not normally invoked by the user; make-dist will do -it appropriately. + This is script is not normally invoked by the user; make-dist will do + it appropriately. -This script creates an extra distribution tarball (both in gzipped and -bzipped variants) from the given target directory. This will include -all the stuff that is normally included in official extra release -tarballs, i.e. the auxiliary libraries such as CLX, CLM, and Hemlock. + This script creates an extra distribution tarball (both in gzipped and + bzipped variants) from the given target directory. This will include + all the stuff that is normally included in official extra release + tarballs, i.e. the auxiliary libraries such as CLX, CLM, and Hemlock. -This is intended to be run from make-dist.sh. + This is intended to be run from make-dist.sh. * cross-build-world.sh target-directory cross-directory cross-script [build-binary] [build-flags...] -This is a script that can be used instead of build-world.sh for -cross-compiling CMUCL. In addition to the arguments of build-world.sh -it takes two further required arguments: The name of a directory that -will contain the cross-compiler backend (the directory is created if -it doesn't exist, and must not be the same as the target-directory), -and the name of a Lisp cross-compilation script, which is responsible -for setting up, compiling, and loading the cross-compiler backend. -The latter argument is needed because each host/target combination of -platform's needs slightly different code to produce a working -cross-compiler. - -We include a number of working examples of cross-compiler scripts in -the cross-scripts directory. You'll have to edit the features section -of the given scripts, to specify the features that should be removed -from the current set of features in the host lisp, and those that -should be added, so that the backend features are correct for the -intended target. - -You can look at Eric Marsden's collection of build scripts for the -basis of more cross-compiler scripts. + This is a script that can be used instead of build-world.sh for + cross-compiling CMUCL. In addition to the arguments of build-world.sh + it takes two further required arguments: The name of a directory that + will contain the cross-compiler backend (the directory is created if + it doesn't exist, and must not be the same as the target-directory), + and the name of a Lisp cross-compilation script, which is responsible + for setting up, compiling, and loading the cross-compiler backend. + The latter argument is needed because each host/target combination of + platform's needs slightly different code to produce a working + cross-compiler. + + We include a number of working examples of cross-compiler scripts in + the cross-scripts directory. You'll have to edit the features section + of the given scripts, to specify the features that should be removed + from the current set of features in the host lisp, and those that + should be added, so that the backend features are correct for the + intended target. + + You can look at Eric Marsden's collection of build scripts for the + basis of more cross-compiler scripts. Step-by-Step Example of recompiling CMUCL for OpenBSD ----------------------------------------------------- Set up everything as described in the setup section above. Then execute: - +``` # Create a new target directory structure/config for OpenBSD: bin/create-target.sh openbsd OpenBSD_gencgc OpenBSD @@ -487,10 +487,12 @@ bin/load-world.sh openbsd "18d+ 2002-05-06" # core will announce. Please always put the build-date and some # other information in there, to make it possible to differentiate # those builds from official builds, which only contain the release. +``` Now you should have a new lisp.core, which you can start with - +``` ./openbsd/lisp/lisp -core ./openbsd/lisp/lisp.core -noinit -nositeinit +``` Compiling sources that contain disruptive changes ------------------------------------------------- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/156551453481307a0e3405a2e… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/156551453481307a0e3405a2e… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0

[Git][cmucl/cmucl][master] Rename BUILDING to BUILDIND.md and convert to markdown
by Raymond Toy 10 Dec '18

10 Dec '18

Raymond Toy pushed to branch master at cmucl / cmucl Commits: cb825da9 by Raymond Toy at 2018-12-10T14:53:27Z Rename BUILDING to BUILDIND.md and convert to markdown Initial conversion of BUILDING to markdown. - - - - - 1 changed file: - BUILDING → BUILDING.md Changes: ===================================== BUILDING → BUILDING.md ===================================== @@ -1,4 +1,3 @@ --*- Mode: text -*- Building CMU CL =============== @@ -13,13 +12,13 @@ General Requirements In order to build CMU CL, you will need: -a) A working CMU CL binary. There is no way around this requirement! +a. A working CMU CL binary. There is no way around this requirement! This binary can either be for the platform you want to target, in that case you can either recompile or cross-compile, or for another supported platform, in that case you must cross-compile, obviously. -b) A supported C compiler for the C runtime code. +a. A supported C compiler for the C runtime code. Most of the time, this means GNU gcc, though for some ports it means the vendor-supplied C compiler. The compiler must be @@ -28,13 +27,13 @@ b) A supported C compiler for the C runtime code. Note for FreeBSD 10 and above: The build requires gcc (Clang will not work) and the lib32 compatiblity package. -c) GNU make +a. GNU make This has to be available either as gmake or make in your PATH, or the MAKE environment variable has to be set to point to the correct binary. -d) The CMU CL source code +a. The CMU CL source code Here you can either use one of the release source tarballs, or check out the source code directly from the public CMUCL git @@ -48,7 +47,7 @@ though recompilation against 2.x Motif probably works as well. Setting up a build environment ------------------------------ -1.) Create a base directory and change to it +1. Create a base directory and change to it mkdir cmucl ; cd cmucl @@ -77,7 +76,7 @@ want to do that and in case you know, somehow, that the version of CMUCL you are building from will build the sources you have, here is a quick guide. -a) Simple builds +1. Simple builds Use this to build from a version of CMUCL that is very close to the sources you are trying to build now: @@ -93,7 +92,7 @@ a) Simple builds load-world.sh three times. See below for descriptions of these scripts. -b) Slightly more complicated builds +1. Slightly more complicated builds For slightly more complicated builds, you may need to use some bootstrap files. See below for more information about these @@ -109,7 +108,7 @@ b) Slightly more complicated builds As in a) above, three builds are done, and the result is in the directory build-4. -c) More complicated builds +1. More complicated builds If you have more complicated builds, this script probably will not work, and definitely does not handle cross-compiles. In this case, @@ -136,7 +135,7 @@ and cross-compilation. We'll first look at normal recompilation: The recompilation process basically consists of 4 phases/parts: -a) Compiling the lisp files that make up the standard kernel. +1. Compiling the lisp files that make up the standard kernel. This happens in your current CMU CL process, using your current CMU CL's normal file compiler. This phase currently consists of 3 @@ -148,7 +147,7 @@ a) Compiling the lisp files that make up the standard kernel. or "compiling up a world", based on the name of the first sub-phase. -b) Building a new kernel.core file out of the so created files +1. Building a new kernel.core file out of the so created files This process, which is generally called genesis, and which is controlled by src/tools/worldbuild.lisp, uses the newly compiled @@ -190,7 +189,7 @@ b) Building a new kernel.core file out of the so created files If it doesn't inform you of this, you can skip directly to the last phase d). -c) Recompiling the C runtime code, producing the "lisp" binary file +1. Recompiling the C runtime code, producing the "lisp" binary file This step is only needed if you haven't yet got a suitable lisp binary, or if the internals.h file has changed during genesis (of @@ -206,7 +205,7 @@ c) Recompiling the C runtime code, producing the "lisp" binary file the C sources and recompile because of this, you can do that before Phase b), so that you don't have to perform that phase twice. -d) Populating the kernel.core, and dumping a new lisp.core file. +1. Populating the kernel.core, and dumping a new lisp.core file. In this phase, which is controlled by src/tools/worldload.lisp, and hence often called world-load, the kernel.core file is started up @@ -218,11 +217,11 @@ We're not quite done yet. This produces just a basic lisp.core. To complete the build so that you something similar to what the releases of CMUCL do, there are a few more steps: -e) Build the utilities like Gray streams, simple streams, CLX, CLM, +1. Build the utilities like Gray streams, simple streams, CLX, CLM, and Hemlock. Use the bin/build-utils.sh script for this, as described below -f) Create tarfiles using the bin/make-dist.sh script, as +1. Create tarfiles using the bin/make-dist.sh script, as explained below. With these tarfiles, you can install them anywhere. The contents of @@ -504,7 +503,7 @@ binaries built from earlier sources can compile the sources containing that change. There are two forms of boostrapping that can be required: -a) Bootfiles +1. Bootfiles The maintainers try to make bootfiles available, that allow going from an old release to the next release. These are located in the @@ -525,7 +524,7 @@ a) Bootfiles Alternatively, the bootstrap file can just "load" the individual bootfiles as needed. -b) Cross-compiling +1. Cross-compiling Under some circumstances, bootstrap code will not be sufficient, and a cross-compilation is needed. In that case you will have to View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/cb825da9cf7aff8f96b81ca72… -- View it on GitLab: https://gitlab.common-lisp.net/cmucl/cmucl/commit/cb825da9cf7aff8f96b81ca72… You're receiving this email because of your account on gitlab.common-lisp.net.

1 0