build questions

Matthias Lang matthias@REDACTED
Sun Mar 19 12:46:38 CET 2006

I'm not volunteering to do it, but one or more of the following are
potential cleaner solutions:

  a) modify the make system so that mkliteral is compiled with the
     host compiler

  b) modify the make system so that it uses mkliteral from the
     natively-compiled copy of Erlang on the build system (you need
     this anyway for other parts of the build)
  c) add a build option --disable-dialyzer (works until someone wants
     to cross-compile dialyzer...)

My struggles with autoconf, toolchains and make always seem to get
messy and unsatisfying, even when I have the best of
intentions. So "dirty but works" is just fine by me.


Kostis Sagonas writes:
 > Matthias Lang wrote:
 >  > ...
 >  > HIPE:
 >  >
 >  >    There's a configure option --disable-hipe, but it doesn't 
 >  >    completely disable hipe. It stil tries to run 'mkliteral'.
 > There are reasons for doing this.  mkliteral is needed in order
 > to compile some lib/hipe files to BEAM bytecode.  These files 
 > are needed for e.g. dialyzer to work, not necessarily for
 > compilation to native code.
 >  >    Hacking erts/emulator/ so that HIPE_GENERATE is 
 >  >    left empty mostly fixes that.
 > Yes, but you should be aware of the above.
 > Kostis

More information about the erlang-questions mailing list