Conflicts when starting up various processes

Diogo Franco diogoalexfranco at gmail.com
Fri Feb 5 16:36:34 UTC 2016


Thanks a lot Daniel, nice to know how to change the TMP path.

If I confirm the problem is with ASDF i'll let you know anyway.

Regards,
Diogo

On 30 January 2016 at 16:11, Daniel Kochmański <daniel at turtleware.eu> wrote:

> Hello,
>
> to change the temporary dir you may set the logical-pathname-translation
> of "TMP":
>
>    (setf (logical-pathname-translations "TMP")
>          `(("**;*.*.*" ,(merge-pathnames "/your/new/directory/"
> "**;*.*.*"))))
>
> (or something like this). But I think that the problem is cache
> directory, which is ASDF's area which internals I don't know well
> enough to give any hint – if you use ASDF obviously.
>
> The other solution may be compiling lisp things once and just
> require'ing them in the production code.
>
> Best regards,
> Daniel
>
> Diogo Franco writes:
>
> > Hi,
> >
> > We have a few different c++ projects with ecl embedded, which when
> starting
> > up, have ecl compiling and loading quite a bit of lisp code.
> >
> > If we start the various processes close enough in time, conflicts occur
> > while compiling the lisp code. All is good if I wait for the lisp
> > compilations between starting each process, but this is troublesome to do
> > in production.
> >
> > We believe this may be because the different processes might be using the
> > same temporary folder for the compiled code or something of this nature.
> Is
> > there any way to set the temporary path where ecl builds source code? Or
> > some other hint you think might help?
> >
> > Many thanks in advance for your help,
> >
> > Diogo Franco
>
>
> --
> Daniel Kochmański ;; aka jackdaniel | Poznań, Poland
> TurtleWare - Daniel Kochmański      | www.turtleware.eu
>
> "Be the change that you wish to see in the world." - Mahatma Gandhi
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20160205/84fb6831/attachment.html>


More information about the ecl-devel mailing list