mmap error (?) when building clisp-2.38 in freebsd-6.1-release for amd64

Alejandro Pulver alepulver at
Sat Jul 29 19:01:28 UTC 2006

Hash: SHA1

On Sat, 29 Jul 2006 13:24:54 +0530
Gautham Ganapathy <gauthamglist at> wrote:

> Hi
> I am trying to the the clisp-2.38 port to build on freebsd-6.1-release
> of amd64. However, it does not build and I found a post saying that it
> was marked as broken.
> So far I have tried the following. 
> 1, After running make, the first error that comes up is
> gmake: *** No rule to make target `avcall-amd64.lo', needed by
> `avcall.lo'.  Stop.
> In the Makefile in 'work/clisp-2.38/amd64-portbld-freebsd6.1/avcall',
> CPU is set to amd64 and avcall-$(CPU).lo expands to avcall-amd.lo, when
> the actual source file is avcall-x64_64.c. Setting CPU to x86_64 fixes
> this error
> 2. The next error is
> gmake[1]: *** No rule to make target `vacall-amd64.lo', needed by
> `vacall.lo'.  Stop.
> There is a similar error in
> 'work/clisp-2.38/amd64-portbld-freebsd6.1/callback/vacall_r/Makefile'
> and is easily fixed
> 3. However, the third error is beyond me.
> ./ -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -Emisc 1:1 -norc
> -m 1400KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit))
> (ext::exit t)"
> Cannot map memory to address 0x4000000000000 .
> [spvw_mmap.d:359] errno = EINVAL: Invalid argument.
> ./ Not enough memory for Lisp.
> *** Error code 1
> Is there any way to fix this? Is this for using mmap? The Makefile for
> the port enables the '--disable-mmap' option for amd64
> Regards
> Gautham


I think you are using an old version of the lang/clisp port (current
one is clisp-2.38_1, where building on amd64 was fixed).

Could you please update your ports and try again?

Best Regards,

P.S.: please CC me the next time (or mail me directly).
Version: GnuPG v1.4.4 (FreeBSD)


More information about the freebsd-ports mailing list