clisp brew failing #10370

nesv opened this Issue Feb 21, 2012 · 7 comments


None yet

5 participants

nesv commented Feb 21, 2012

clisp is failing with the error message: Failed executing: ulimit -s 16384 && make

The full gist, of brew install -v clisp, is here. brew doctor gives me "Your system is raring to brew."

I am running OS X 10.7 (Lion), brew update has been run, and XCode is at the latest version.

adamv commented Feb 21, 2012

Link isn't working for me.

nesv commented Feb 21, 2012

Oops, sorry about that. It's fixed, now (the link that is).

binjo commented Feb 24, 2012

same issue here, any workaround? thanks.


The real error is here:

./ -B . -E UTF-8 -Epathname 1:1 -Emisc 1:1 -norc -m 2MW -lp  -x '(and (load "init.lisp") (sys::%saveinitmem) (ext::exit)) (ext::exit t)'
C_CODE_ALIGNMENT is wrong. &EVAL-WHEN = 0x10e925853.
Add -falign-functions=4 to CFLAGS in the Makefile.

Try adding that flag to CFLAGS and see if it works. It may also be worth having a look at issue #7368. In the worst case, try building 32-bit.

While it's worthwhile to get this working, I'd try clozure-cl too.

2bits commented Feb 24, 2012

The solution is to allow what the developers have determined is the correct optimization level for their software. In our particular case, it's likely that the recent change from -O3 from -Oshas done a number on this. Your solution is to add a line of code under the j1 business:

def install
  ENV.j1 # This build isn't parallel safe.
  ENV.remove_from_cflags /-O./

It removes our -Os from your environment and allows the proper -O to work.
What is also a reasonable solution is to yank that whole inreplace.
Anybody feel like doing the fix on this formula?

binjo commented Feb 24, 2012

@2bits add 'ENV.remove_from_cflags /-O./' seems able to fix the issue for me, thank you very much.

nesv commented Feb 24, 2012

@2bits This worked for me as well! Thank you. :)

Here is the pull request for the fixes for this issue.

@nesv nesv closed this Feb 24, 2012
@xu-cheng xu-cheng locked and limited conversation to collaborators Feb 16, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.