error on debian 64-bit

[daniel-jacob-pearson]

Issue #55 appears to be occurring again with the binaries for version 1.4.

"./jq: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found (required by ./jq)"

[nicowilliams]

@hamann @daniel-jacob-pearson @stedolan Please clue me in as to how to build with statically linked libc and libm on Ubuntu. I tried using diet(1), but its libm is very limited. I could try uclibc, but I'm hoping there's something more trivial that I've missed.

[stroan]

@nicowilliams The issue last time was a GLIB_C incompatibility between the version on the build machine and the target machines. I believe if you just do a regular compile on an old ubuntu, with an old GLIB_c everything will be ok.

[nicowilliams]

Well, OK, but I'll have to find and install old images.

[stroan]

I can do it tonight in a VM if you're ok with waiting a few hours.

[gregoryb]

Interested! I just got the issue! Thanks you

[karthikkrishnanv]

I have the same issue as well (on SUSE). It would be of great help if there are older images lying somewhere.

[nicowilliams]

I'll restore the old binaries in a couple of hours.

Clues as to how to build statically linked executables on Ubuntu 14.04
would be useful.

[nicowilliams]

I've put the 1.3 executables back up.

I'll try to get an Ubuntu 12.04 image going on which to build a 1.4 jq executable that works for more people.

[nicowilliams]

@daniel-jacob-pearson @stroan @gregoryb @karthikkrishnanv

Can you try now? I've updated the Linux 64-bit jq executable to one built on Oneiric.

[gregoryb]

it works. Thanks

[karthikkrishnanv]

It works for me as well. Thanks.

On Fri, Jun 13, 2014 at 2:13 AM, Grégory notifications@github.com wrote:

it works. Thanks

—
Reply to this email directly or view it on GitHub
#401 (comment).

[mwilliamson]

@nicowilliams I might be telling you things you already know, but I find it easiest to build for older versions of glibc by using debootstrap and chroot (and possibly schroot). A little bit more reading required to get going compared to using virtual machines, but much less faff once everything is set up.

[nicowilliams]

@mwilliamson Thanks! I learned about debootstrap late yesterday, and though I didn't use it this time, I will next time.

[hamann]

I would highly recommend to do this stuff with vagrant

[nicowilliams]

@hamann Thanks! That looks like exactly what I'm after.

[daniel-jacob-pearson]

It works again now. Thanks!