-
Notifications
You must be signed in to change notification settings - Fork 67
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
Use of glibc_version_header in project not effective #15
Comments
Curl probably links to other dependencies which were not compiled with this (eg libssl) |
Right, before I rebuild openssl and curl I wanted to successfully build a simple executable with which to confirm correct usage of a glibc_version_header header file. So, I assumed that "...'GLIBC_2.7' not found ..." (due to, say, an sscanf (2.7) versioned symbol) might be resolved by including the force_link_glibc_2.6.h header, but, haven't had success yet; i.e., my test executable won't run on the target platform regardless of the force_link_glibc_x.y.h header I include. So, it seems clear I'm missing something ... maybe a lot. BTW, the previously cited Makefile builds a simple program ... |
Didn't mean to close this thread. |
Hi, I am running into the same issue. Freshly built on : native glibc:
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
int main(int argc, char **argv) {
pause();
return 0;
}
What am I doing wrong? Thanks |
I'm not sure what I need to do, or, what I'm failing to understand ...
Platforms:
Development
x86_64
CentOS Linux 2.6.32-358.el6.x86_64
gcc 4.4.7
Target:
x86_64
Oracle Linux 2.6.39-400.294.3.el5uek
curl-7.61.0 built on development platform fails to run on target
platform:
./curl: /lib64/libc.so.6: version `GLIBC_2.7' not found (required by ./curl)
Tried simple project with Makefile entries ...
SHELL = /bin/sh
CC = gcc -static-libgcc
CFLAGS = -include /home/geek2/dev/proofs/glibcVerHdr/force_link_glibc_2.6.h
LDFLAGS = -Wl,-v
(and with other versions of force_link_glibc_2.*.h), but, the executable
continues to fail like curl.
The text was updated successfully, but these errors were encountered: