Re: next nightly build problem

Hi,

Adding this because it might be related: on NetBSD I disabled
TRIVIALMAP_MEMORY and SINGLEMAP_MEMORY because our fixed address (0x40...0)
is not mappable there.

This was done with commit 1c61a0 [1]

[1]
https://sourceforge.net/p/clisp/clisp/ci/1c61a0872d35c2a19dfdaaeb673f7b70365c30e2/

Don Cohen <[email protected]> schrieb am Sa., 4. März
2017, 05:58:

> Bruno Haible writes:
>  > Don Cohen wrote:
>  > > so do something like this?
>  > >  make -f Makefile.devel  -k multibuild-porting64-gcc
>  >
>  > Yes.
>  >
>  > > That ends up with
>  > >   *** - SYSTEM::INITIAL-BREAK-DRIVER: The value of *DEBUG-IO* was not
> an appropriate stream: #<UNBOUND>. It has been changed to #<IO
> SYNONYM-STREAM *TERMINAL-IO*>.
>  >
>  > This is caused by Sam's commit at Feb 26 21:39:18 2017 -0500.
>  > You need to revert it locally
>  >   $ hg diff -c d61ff18e7daa | patch -R -p1
>  > before you can build clisp in any configuration.
>
> This makes a difference, all right.
> I think I can guess which ones work from this:
> -rw-rw-r--. 1 don don    5372 Mar  3 20:41
> build-porting64-gcc-generational_gc-multithread_gc/cbcstep3.log
> -rw-rw-r--. 1 don don    5116 Mar  3 20:40
> build-porting64-gcc-generational_gc-old_gc/cbcstep3.log
> -rw-rw-r--. 1 don don 3042294 Mar  3 20:22
> build-porting64-gcc-generic64_heapcodes/cbcstep3.log
> -rw-rw-r--. 1 don don 3037594 Mar  3 20:17
> build-porting64-gcc-heapcodes/cbcstep3.log
> -rw-rw-r--. 1 don don 3046443 Mar  3 20:32
> build-porting64-gcc-heapcodes-spvw_mixed_blocks/cbcstep3.log
> -rw-rw-r--. 1 don don 3043261 Mar  3 20:26
> build-porting64-gcc-heapcodes-spvw_pages/cbcstep3.log
> -rw-rw-r--. 1 don don    4860 Mar  3 20:39
> build-porting64-gcc-multithread_gc/cbcstep3.log
> -rw-rw-r--. 1 don don    4604 Mar  3 20:38
> build-porting64-gcc-old_gc/cbcstep3.log
> -rw-rw-r--. 1 don don    4636 Mar  3 20:42
> build-porting64-gcc-safety0/cbcstep3.log
> -rw-rw-r--. 1 don don    4983 Mar  3 20:43
> build-porting64-gcc-safety0-optimized/cbcstep3.log
> -rw-rw-r--. 1 don don    4636 Mar  3 20:14
> build-porting64-gcc-safety3/cbcstep3.log
> -rw-rw-r--. 1 don don 3040627 Mar  3 20:37
> build-porting64-gcc-spvw_pure_blocks/cbcstep3.log
> -rw-rw-r--. 1 don don 3041797 Mar  3 20:20
> build-porting64-gcc-standard_heapcodes/cbcstep3.log
> -rw-rw-r--. 1 don don 3046009 Mar  3 20:34
> build-porting64-gcc-typecodes-spvw_mixed_blocks/cbcstep3.log
> -rw-rw-r--. 1 don don 3042770 Mar  3 20:29
> build-porting64-gcc-typecodes-spvw_pages/cbcstep3.log
>
> Next steps?
> I guess you'd like them all to work, right?
> How would one choose among those that work?
>
>
> ------------------------------------------------------------------------------
> 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
>

------------------------------------------------------------------------------
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