<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">
      <p>Hi again,</p>
      On 29/05/2013 18:53, Juan Jose Garcia-Ripoll wrote:<br>
    </div>
    <blockquote
cite="mid:CANejTzoM-S8pq=LQEWQnTXD6YfuDUbfh9OZ+8Dv763pcjDQsnQ@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Wed, May 29, 2013 at 6:10 PM,
            William Hounslow <span dir="ltr"><<a
                moz-do-not-send="true"
                href="mailto:hounslow@users.sourceforge.net"
                target="_blank">hounslow@users.sourceforge.net</a>></span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">Can a
              truly standalone program be created? If not, how to ensure
              that the end user can deploy the output binary in a
              location of their choice?</blockquote>
          </div>
          <br>
          Apart from what you have been told, ECL can be built in
          statically linked mode with --disable-shared. In this case,
          standalone executables should be linked against a statically
          linked version of the library. But I personally find the other
          solution (deliver executable with the ECL library) preferable
          (and more compliant with LGPL).</div>
        <div class="gmail_extra"><br>
        </div>
        <div class="gmail_extra">Juanjo<br>
          <br clear="all">
          <div><br>
          </div>
          -- <br>
          Instituto de Física Fundamental, CSIC<br>
          c/ Serrano, 113b, Madrid 28006 (Spain) <br>
          <a moz-do-not-send="true"
            href="http://juanjose.garciaripoll.googlepages.com"
            target="_blank">http://juanjose.garciaripoll.googlepages.com</a>
        </div>
      </div>
    </blockquote>
    <p>I rebuilt ECL as suggested, deleted the old binary, evaluated
      (ext:install-c-compiler) and was able to get the hoped-for
      statically linked program.</p>
    <p>Now I need to change something and recompile.</p>
    <p>The initial problem was something to do with an unexpected rubout
      character in the FASL (I don't have a record of this
      unfortunately). I then tried deleting the ASDF cache to force a
      total recompilation. Now I get:</p>
    <small><font face="Courier New, Courier, monospace">Condition of
        type: CASE-FAILURE<br>
        :FASL fell through ECASE expression.<br>
        Wanted one of (:PROGRAM :LIB ...).<br>
        Broken at C::BUILDER. In: #<process TOP-LEVEL>.<br>
        >> :b<br>
        <br>
        Backtrace:<br>
          > C::BUILDER<br>
          > c:build-fasl<br>
          > uiop/lisp-build:compile-file*<br>
          > lambda<br>
          > uiop/utility:call-with-muffled-conditions<br>
          > uiop/lisp-build:call-with-muffled-compiler-conditions<br>
          > lambda<br>
          > uiop/utility:call-function<br>
          > uiop/lisp-build:call-around-hook<br>
          > asdf/lisp-action:call-with-around-compile-hook<br>
          > asdf/lisp-action:perform-lisp-compilation<br>
          > asdf/action:perform<br>
          > asdf/action:perform-with-restarts<br>
          > asdf/action:perform-with-restarts<br>
          > asdf/plan:perform-plan<br>
          > asdf/plan:perform-plan<br>
          > asdf/operate:operate<br>
          > call-next-method<br>
          > lambda<br>
          > asdf/cache:call-with-asdf-cache<br>
          > asdf/find-system::call-with-system-definitions<br>
          > lambda<br>
          > asdf/operate:operate<br>
          > call-next-method<br>
          > lambda<br>
          > asdf/cache:call-with-asdf-cache<br>
          > asdf/find-system::call-with-system-definitions<br>
          > lambda<br>
          > lambda<br>
          > asdf/bundle:make-build<br>
          > si:bytecodes [Evaluation of: (asdf/bundle:make-build
        :process-form ...)]<br>
          > si:bytecodes [Evaluation of: (si:top-level t)]</font></small><br>
    <p>What is wrong?</p>
    <p>Thanks in anticipation,</p>
    <p>William</p>
  </body>
</html>