[erlang-questions] libei use in port drivers

Thomas Stover tstover@REDACTED
Fri Oct 18 23:45:53 CEST 2013

Thanks for the response.

On 10/18/13 4:32 PM, "Anthony Ramine" wrote:

>Le 18 oct. 2013 à 22:13, Thomas Stover <tstover@REDACTED> a écrit :
>What is your platform? Also please note that driver_output_term() is

Yes, noted. I'm working with an inherited codebase. Platform is Linux on

>> ...
>Use erl_ddll:format_error({open_error,-10}).

"undefined symbol: erl_decode"

I'm sure that is due to the objects inside libei.a (most likely) not being
built with -fpic, which is what would have had to happen for them to load
up in the dlopen() of my driver.

I suppose I could try to rebuild libei as a shared lib (why isn't it to
start with?). That feels strange though, because is no one else using
libei inside a driver? Does everyone just use only manual encoding from
erlang to C when it comes to drivers. Does everyone just use external
process ports when they use libei?

More information about the erlang-questions mailing list