-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
failure with older glibc #30
Comments
+1 for this. Trying to run the pre-compiled binary on CentOS 5.8 results in the GLIBC error above. Haven't tried a local compile just yet. |
The libc API (or at least, the bits that jq uses) hasn't changed in more than 20 years, and still glibc manages to break compatibility between minor versions :( I don't have a box with a sufficiently old glibc to build against to hand at the moment, so for now building from source is your best bet. The release tarball and git master (at the moment) have generated parsers, etc. checked in so all you need to build is make and gcc. I'll have another look at this when packaging for more current systems is figured out :) |
Same situation with CentOS 6.3 machines. |
+1 Can't run the binary nor build from source when running CentOS 6.3 because it runs on glibc 2.12 foo]$ jq -v |
Why can't you build it from source on CentOS 6.3? |
@HarryR maybe it's something with my own environment Here's what I've got
|
That's a bit strange, it looks like you're running into a different issue when building. Can you run the
line in a shell on its own? Do you have write permissions here? What does |
tl;dr don't know if related, but had just updated kernel-* and NOT rebooted yet when tried to build jq. After reboot build works. I had full permissions to the jq src directory but not to its parent directory, I mean My machine was up for just over 3 months and I had just run a bunch of updates including kernel-* when I tried building jq immediately after all those updates - without rebooting the machine. Sorry for the delay on the feedback. |
OK, figured this one out a bit. It seems a recentish change to memcpy in glibc broke things (http://lwn.net/Articles/414467/), and so the glibc guys bumped the symbol version for memcpy, which means that binaries that were built with a new glibc aren't backwards compatible if they call memcpy. The Debian project removed that change, so binaries built with Debian glibc don't seem to have the GLIBC_2.14 dependency. I'll be releasing a new version of jq fairly soon, with binaries that shouldn't have this issue. |
|
I can confirm that the jq 1.2 binary works with CentOS 5.8 64-bit (glibc 2.5). I can also confirm that jq rocks -- thank you very much for this! |
Hey,
Awesome project; really love it!
More of an fyi, but under Fedora 13, I couldn't run the precompiled version; it complained "GLIBC_2.14 not found". Compiling locally works great.
I have many "yes, please"s to add to other feature requests; will add them there.
The text was updated successfully, but these errors were encountered: