Created attachment 326422 [details]
For some reason the current stable of clisp fails to compile on one of my boxes. It claims to have not enough memory, but there should be plenty left according to top and the swap isn't even used yet (which would be an other 2gb).
I suspect that maybe the build-tools are limited to a certain amount - maybe that can be resolved easily.
Created attachment 326424 [details]
Created attachment 326426 [details]
emerge --info '=dev-lisp/clisp-2.48-r1'
Created attachment 326428 [details]
emerge -pqv '=dev-lisp/clisp-2.48-r1'
According to your emerge --info, you're running a hardened profile and have ccache enabled.
Could you please disable ccache and report if it fails in the same way or differently?
hm ok, I didn't know that this could cause problems.
But the results are the same.
Created attachment 333904 [details]
My build.log for clisp-2.48-r1
Created attachment 333906 [details]
My emerge --info for clisp-2.48-r1
Created attachment 333908 [details]
My emergy -pqv for clisp-2.48-r1
Created attachment 333910 [details]
My environment file for clisp-2.48-r1
I seem to be having the same issue, added my relevant logs and emerge output. Also running the hardened profile.
switching the compiler profile temporary to x86_64-pc-linux-gnu-4.7.2-hardenednopiessp helped me.
Created attachment 452504 [details]
mayge hardened related ? Id o have 64 GB here
Created attachment 452506 [details]
Created attachment 452508 [details]
Created attachment 452510 [details]
Per bug #638942, libffcall update should fix the issue