Re: A question about pure static linking with libdl

[John Hu <heat0415@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2806 bytes --]

Dear Mr.Nagy,

First thanks for your sincere reply but I still have some questions. The
reason why I do this test is that I want to build my project on my machine
and distribute it to any other Linux (I can't ask other people to compile
my project on their machine, that is totally unacceptable). I think full
static linking can do this. Since full static linking does not support
dlopen I made another test: generate ld.gold that ONLY dynamic links with
musl-libc(libc.so) and so does LLVMgold.so. Then I copy them to Ubuntu
16.04 and exec ldd command on both and I found that "libc.musl-x86_64.so.1
=> not found"  in the output. Finally I exec "./ld.gold --plugin
LLVMgold.so" and an error occurred that "could not load plugin library:
libc.musl-x86_64.so.1: cannot open shared object file: No such file or
directory". I test the basic function of these two files that works well
because they can find glibc ld.so on Ubuntu16.04 as ldd shows.
Now I have no idea how to workaround this problem, my question is that
whether there is a way that generating some binary executable files in one
system and they are portable and compatible on any other Linux
distributions (means these binary files can run normally without any
problem).

2017-05-16 18:30 GMT+08:00 Szabolcs Nagy <nsz@port70.net>:

> * John Hu <heat0415@gmail.com> [2017-05-16 15:40:28 +0800]:
> > Recently I have an experiment about whether full static-linked ld.gold
> with
> > plugin function enabled can use its --plugin option to dynamically load
> > plugins such as LLVMgold.so. I use "./configure --enable --enable-plugins
> > --disable-werror LDFLAGS="-static" "  to generate a full statically
> linked
> > ld.gold which does not have any dynamic library dependency, then I exec
> > "./ld.gold --plugin LLVMgold.so" but an error occurs that "could not load
> > plugin library: Dynamic loading not supported". I doubt this is a bug
> > because it is claimed that musl supports full static linking but I am not
> > sure about that. BTW, my experiment environment is Alpine 3.5.
>
> dlopen is not supported in static linked binaries yet, that is non-trivial
> to support and in your use case it does not make sense: the loaded lib is
> linked against the host libc (and many other libs) and is in a package that
> is updated independently of the libc, there is no guarantee that the static
> linked libc is compatible with the host libc (and if there is then you
> don't really need static linking anyway, you could get the same effect
> by using your custom libc to launch ld.gold as ./mylibc.so ld-gold ).
>
> >
> > Now I send this email again because I want this email to be replied
> > according to "If you are not subscribed and want to receive a reply,
> please
> > mention in your email that you want to be Cc'd." in the website.
>

[-- Attachment #2: Type: text/html, Size: 3444 bytes --]