[Mono-list] libc.so vs libc.so.6

tomason tom at creamysoft.com
Mon Jan 14 17:11:01 UTC 2013


I'm using Link Mint 14, and I'm creating a new program in which I embed
mono.  Using the samples as a starting point, I had no problems building my
app.  However, I'm having problems running it: libc.so is not found.

I enabled debug output and found out that mono is looking for libc.so first
in the current directory and then in /usr/lib/x86_64-linux-gnu.  It finds
libc.so in the latter directory, but says that it's not a valid ELF file.

It's right: that libc.so file is a linker script, not an ELF.  The linker
script redirects to /lib/x86_64-linux-gnu/libc-2.15.so.  If I rename the
libc.so script and then create a link named libc.so that targets
libc-2.15.so, then my app runs just fine.  But the problem then is that I
can no longer build my app.

Is there a way to tell mono to look somewhere else for libc.so?

Lastly, when I run my managed assembly with the installed version of mono
using debug output, I see that it does not look for libc.so, but libc.so.6. 
libc.so.6 also exists in /lib/x86_64-linux-gnu/ and is a link to
libc-2.15.so.  It finds libc.so.6 just fine and runs perfectly.

Any help is greatly appreciated!


View this message in context: http://mono.1490590.n4.nabble.com/libc-so-vs-libc-so-6-tp4658121.html
Sent from the Mono - General mailing list archive at Nabble.com.

More information about the Mono-list mailing list