Re: dub ldc2 static linking

2022-10-28 Thread Yura via Digitalmars-d-learn
On Friday, 28 October 2022 at 09:02:22 UTC, Kagamin wrote: On Friday, 28 October 2022 at 02:46:42 UTC, ryuukk_ wrote: I'm just right now having an issue with glibc version mismatch for my server Just compile with an old enough glibc, 2.14 works for me. Indeed, if I got it right it seems to

Re: dub ldc2 static linking

2022-10-28 Thread Kagamin via Digitalmars-d-learn
On Friday, 28 October 2022 at 02:46:42 UTC, ryuukk_ wrote: I'm just right now having an issue with glibc version mismatch for my server Just compile with an old enough glibc, 2.14 works for me.

Re: dub ldc2 static linking

2022-10-28 Thread Sergey via Digitalmars-d-learn
On Friday, 28 October 2022 at 04:02:15 UTC, ryuukk_ wrote: On Friday, 28 October 2022 at 02:46:42 UTC, ryuukk_ wrote: On Friday, 28 October 2022 at 01:35:04 UTC, kinke wrote: For fully static linking on Linux, you'll need to move away from glibc to e.g. the musl C runtime, as used by the

Re: dub ldc2 static linking

2022-10-27 Thread ryuukk_ via Digitalmars-d-learn
On Friday, 28 October 2022 at 02:46:42 UTC, ryuukk_ wrote: On Friday, 28 October 2022 at 01:35:04 UTC, kinke wrote: For fully static linking on Linux, you'll need to move away from glibc to e.g. the musl C runtime, as used by the Alpine distro. I'm just right now having an issue with glibc

Re: dub ldc2 static linking

2022-10-27 Thread ryuukk_ via Digitalmars-d-learn
On Friday, 28 October 2022 at 01:35:04 UTC, kinke wrote: For fully static linking on Linux, you'll need to move away from glibc to e.g. the musl C runtime, as used by the Alpine distro. I'm just right now having an issue with glibc version mismatch for my server, so i'm looking to move to

Re: dub ldc2 static linking

2022-10-27 Thread Mike Parker via Digitalmars-d-learn
On Friday, 28 October 2022 at 01:37:50 UTC, Mike Parker wrote: This has nothing to do with dub and is not a D issue specifically. Enter your error message in Google and you'll get a long list of results. Maybe one of them can help you. Or do what kinke suggests :-)

Re: dub ldc2 static linking

2022-10-27 Thread kinke via Digitalmars-d-learn
For fully static linking on Linux, you'll need to move away from glibc to e.g. the musl C runtime, as used by the Alpine distro.

Re: dub ldc2 static linking

2022-10-27 Thread Mike Parker via Digitalmars-d-learn
On Thursday, 27 October 2022 at 08:08:38 UTC, Yura wrote: curl.d:(.text._D3std3net4curl7CurlAPI7loadAPIFZPv+0xd): warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking and many other warnings like this.

Re: dub ldc2 static linking

2022-10-27 Thread Yura via Digitalmars-d-learn
Thank you! I tried this one, but it did not help. All these warnings survived : "... Using 'getservbyport' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking" On Thursday, 27 October 2022 at 14:18:01 UTC, Anonymouse wrote: On

Re: dub ldc2 static linking

2022-10-27 Thread Anonymouse via Digitalmars-d-learn
On Thursday, 27 October 2022 at 08:08:38 UTC, Yura wrote: What am I doing wrong? Any way to fix it? https://forum.dlang.org/thread/gghcyaapjwfcpnvks...@forum.dlang.org worked for me.

dub ldc2 static linking

2022-10-27 Thread Yura via Digitalmars-d-learn
Dear All, I am trying to create a static executable to be able to run it on virtually any linux x86_64 OS. At the end I get a binary, however, multiple warnings are printed after compilation. My dub.sdl: dependency "mir" version="~>3.2.3" dependency "lubeck" version="~>1.5.1" lflags