Re: Got my name in the list
[email protected] (Don Cohen)
| Newsgroups | gmane.lisp.clisp.devel |
|---|---|
| Message-ID | <[email protected]> |
Compro Prasad writes: > Strikeoff "Giving the path is necessary" on the first line of the previous > email. ... > > Dropbox/programs/hg/clisp/src/foreign1.lisp ... > > *** - SYSTEM::%FIND-PACKAGE: There is no package with name "FFI" Actually you don't need FFI in order to work on MT. It might save trouble to just not include it. > > I have Makefile.devel . Does it need attention? This was (and still is) my suggestion: > I suggest starting with Makefile.devel (is that part of the hg source?), > finding the line that says > # Options to pass to configure > and changing the next line to > MULTIBUILD_OPTIONS = --with-threads=POSIX_THREADS > storing the result as Makefile.develMT > then > make -f Makefile.develMT -k multibuild-porting64-gcc > in order to at least find SOME way to build MT. This tests a number of different configs, some with enable-portability and some without. I'm hoping that (as happens for me), at least SOME of these configurations work. I think you can work on hash tables just as well in any of them, so you might as well just find one that works and use that. Even if the hash table code turns out to depend on these config differences, you might as well start with one that works. The result of the make above (eventually) is a whole set of build directories with names like build-porting64-gcc-debug_gcsafety, build-porting64-gcc-generational_gc-old_gc, etc. ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ clisp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/clisp-devel