Thread overview
GLIBC_2.27 not found when running ldc on Debian Jessie
Aug 13, 2021
tastyminerals
Aug 13, 2021
kinke
Aug 16, 2021
tastyminerals
August 13, 2021

I tried to compile one of the D projects using our CI (Jenkins) today. Unfortunately, we use Debian Jessie as a base image and its glibc version is 2.19 while current ldc2-1.27.0-linux-x86_64 requires 2.27. Which ldc2 version uses glibc 2.19 or compatible with Debian Jessie?

August 13, 2021

On Friday, 13 August 2021 at 19:42:09 UTC, tastyminerals wrote:

>

I tried to compile one of the D projects using our CI (Jenkins) today. Unfortunately, we use Debian Jessie as a base image and its glibc version is 2.19 while current ldc2-1.27.0-linux-x86_64 requires 2.27. Which ldc2 version uses glibc 2.19 or compatible with Debian Jessie?

You'd probably have to go back quite a number steps - in recent years, we've always used the oldest non-EOL Ubuntu version as base image. Ubuntu 16 used for the last ~2 years (before the recent bump to 18) came with v2.23, so something < v1.15 might work (for which the packages weren't built automatically by CI services but manually).

August 16, 2021

On Friday, 13 August 2021 at 21:33:17 UTC, kinke wrote:

>

On Friday, 13 August 2021 at 19:42:09 UTC, tastyminerals wrote:

>

I tried to compile one of the D projects using our CI (Jenkins) today. Unfortunately, we use Debian Jessie as a base image and its glibc version is 2.19 while current ldc2-1.27.0-linux-x86_64 requires 2.27. Which ldc2 version uses glibc 2.19 or compatible with Debian Jessie?

You'd probably have to go back quite a number steps - in recent years, we've always used the oldest non-EOL Ubuntu version as base image. Ubuntu 16 used for the last ~2 years (before the recent bump to 18) came with v2.23, so something < v1.15 might work (for which the packages weren't built automatically by CI services but manually).

I see, thank you.
After some trial-and-error, I found that actually v1.21 worked with our image.