"unexec: not enough room for load commands ..." on OSX

"unexec: not enough room for load commands ..." on OSX

[Randal L. Schwartz]

About every third or fourth day when I build the HEAD on OSX, I get
something that looks like this:

    Writing LC_DYLD_INFO_ONLY command
    Writing LC_SYMTAB command
    Writing LC_DYSYMTAB command
    Writing LC_LOAD_DYLINKER  command
    Writing LC_UUID           command
    Writing LC_VERSION_MIN_MACOSX command
    Writing LC_SOURCE_VERSION command
    Writing LC_MAIN           command
    Writing LC_LOAD_DYLIB     command
    Writing LC_LOAD_DYLIB     command
    Writing LC_LOAD_DYLIB     command
    Writing LC_LOAD_DYLIB     command
    Writing LC_LOAD_DYLIB     command
    Writing LC_LOAD_DYLIB     command
    Writing LC_LOAD_DYLIB     command
    Writing LC_LOAD_DYLIB     command
    Writing LC_LOAD_DYLIB     command
    Writing LC_FUNCTION_STARTS command
    Writing LC_DATA_IN_CODE   command
    Writing LC_DYLIB_CODE_SIGN_DRS command
    unexec: not enough room for load commands for new __DATA segments
    make[1]: *** [bootstrap-emacs] Error 1
    make: *** [src] Error 2

Even resetting the workdir to a fresh checkout, and following the
instructions in INSTALL.BZR, doesn't fix it.

But then, a couple of days later, on a later daily HEAD, it just "works
again".

Is someone fixing this by setting some value to a higher number?  If so,
can I do that myself too?

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.posterous.com/ for Smalltalk discussion

Re: "unexec: not enough room for load commands ..." on OSX

[David Reitter]

On May 20, 2013, at 10:22 AM, Randal L. Schwartz <merlyn@stonehenge.com> wrote:

>    unexec: not enough room for load commands for new __DATA segments
>    make[1]: *** [bootstrap-emacs] Error 1
>    make: *** [src] Error 2

I get these, too.  

I found that adjusting headerpad_extra in autogen/configure (or configure.ac) may take care of the issue.