Robert Jordan wrote
Your custom loader is supposed to support dlopen(NULL) and
your linker must be able to export public symbols.
See ld's --export-dynamic option.
Thanks Robert
In my case loader is not custom and supports dlopen(NULL) and I'm using
mkbundle.
--
View this message in
Same here! Did you solve it?
ralphbariz wrote
Hi,
I'm trying to compile a static one binary mono(Because the target system
has an incompatible loader).
First I got mono to build statically, but without libMonoPosixHelper in
the archive. After a few tries, I got also this, changed all
Sadly no
Am 31.12.2013 11:37 schrieb mobin.seven [via Mono]
ml-node+s1490590n4661646...@n4.nabble.com:
Same here! Did you solve it?
ralphbariz wrote
Hi,
I'm trying to compile a static one binary mono(Because the target system
has an incompatible loader).
First I got mono to build
On 31.12.2013 10:34, mobin.seven wrote:
Same here! Did you solve it?
ralphbariz wrote
Hi,
I'm trying to compile a static one binary mono(Because the target system
has an incompatible loader).
First I got mono to build statically, but without libMonoPosixHelper in
the archive. After a few
On Apr 12, 2012, at 3:43 AM, ralphbariz wrote:
I'm trying to compile a static one binary mono(Because the target system has
an incompatible loader).
What platform is this? What kind of loader does your target system have? Does
it have any shared library loader?
After a few tries, I got also
AFAIK, the DLLImport binding depend on loading information of dynamic
libraries, if you want to call something statically linked in the runtime
you'll need to move to using internal calls, but that means an extensive
rewrite of the the affected libraries both managed and native as the
protocol
Hi,
I'm trying to compile a static one binary mono(Because the target system has
an incompatible loader).
First I got mono to build statically, but without libMonoPosixHelper in the
archive. After a few tries, I got also this, changed all DllImport(MPH)
calls in Mono.Posix.dll to
