This is something I experienced a couple weeks ago. The solution is to link
your final executable against the 'contrib' libraries that ECL has compiled.
You need to add something like this to your compiler step: `-L/path/to/ecl
-lasdf`
This email from last month's mailing list archives has more
Just wanted to give an update: thanks to Paul's advice I got everything
working properly!
Thank you again!
-Ava
On 27/11/2020 14:13, Ava Fox wrote:
Still running into some issues, but this feels promising and gives me
something to explore.
Thanks Paul!
- Ava
On 27/11/2020 13:54, PR
Still running into some issues, but this feels promising and gives me
something to explore.
Thanks Paul!
- Ava
On 27/11/2020 13:54, PR wrote:
On 11/27/20, Ava Fox wrote:
Daniel,
drakma does not list uiop/asdf/sb-bsd-sockets in it's asd system
definition.
I did try and add those sy
in the world." - Mahatma Gandhi
‐‐‐ Original Message ‐‐‐
On Thursday, 26 November 2020 00:46, Ava Fox wrote:
I've been learning how to create static executables with ECL and was
looking at the provided example that uses an ASDF system that has
defined dependencies
(https://gi
I've been learning how to create static executables with ECL and was
looking at the provided example that uses an ASDF system that has
defined dependencies
(https://gitlab.com/embeddable-common-lisp/ecl/-/tree/develop/examples/asdf_with_dependence).
When following the readme, and building it as
