On Thu, Jul 06, 2017 at 09:55:35AM +0800, blubee blubeeme wrote:
>
> those are sprinkled all over the place, how do I avoid that and use libc
> instead?
The software you are building needs to update their configure process
to cope with dlopen being somewhere other than libdl, from what informatio
Hi Ben
If you can help me with this, I would appreciate it greatly. I am trying to
port this project to FreeBSD:
https://github.com/endlessm/epson-inkjet-printer
After I grab those files then I run autoreconf -fi;
I am not sure how to get autoreconf to not put INCLUDES, which autoreconf
complains
blubee blubeeme wrote:
> Thanks for the reply, I haven't set any -static in my env variables or
> anything like that. Here's a brief output of my env
> the linking to ldl is being done automatically since I call autoreconf -fi
> and that sets up an m4 directory. grep -rn "\-ldl" in the root of t
@Simon libdl is something used on Linux to provide dlopen like functions;
on FreeBSD it's already in libc so, removing the LIBS += -ldl removes the
problem and the program compiles successfully; I am just a bit lost as how
to proceed;
See my last email with the attached updated.diff file.
Best,
O