[opensuse] Compiling on 12.1 but running on 11.4
Hi, I have a piece of software that I would like to compile on opensuse 12.1 but run on older machines with opensuse 11.4. If I do so I get: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./prog) The problem is that the program uses memcpy and this is linked against: U memcpy@@GLIBC_2.14 How can I achieve that my program runs on opensuse 11.4? Christoph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/01/12 10:54, Christoph Bartoschek wrote:
Hi,
I have a piece of software that I would like to compile on opensuse 12.1 but run on older machines with opensuse 11.4.
If I do so I get:
/lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./prog)
The problem is that the program uses memcpy and this is linked against:
U memcpy@@GLIBC_2.14
How can I achieve that my program runs on opensuse 11.4?
Christoph
IS this program open source ? if so, you can build it directly in the Open build service... if your program is propietary, custom etc.. you can try this... __asm__(".symver memcpy,memcpy@GLIBC_2.2.5"); In the source code. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/01/12 12:17, Cristian Rodríguez wrote:
__asm__(".symver memcpy,memcpy@GLIBC_2.2.5");
In the source code.
ps: This is somewhat hackish (or "advanced vodoo" if you want a positive word for it :-D ) It is expected and intended to work just fine, however I strongly suggest you to use as a last resort. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 25.01.2012 16:28, schrieb Cristian Rodríguez:
On 25/01/12 12:17, Cristian Rodríguez wrote:
__asm__(".symver memcpy,memcpy@GLIBC_2.2.5");
In the source code.
ps: This is somewhat hackish (or "advanced vodoo" if you want a positive word for it :-D ) It is expected and intended to work just fine, however I strongly suggest you to use as a last resort.
I hoped that there is a compiler or linker option to achieve this. I do not what to change the source because then the danger exists that I accidentally check the hack in. Christoph -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 1/25/2012 2:23 PM, Christoph Bartoschek wrote:
Am 25.01.2012 16:28, schrieb Cristian Rodríguez:
On 25/01/12 12:17, Cristian Rodríguez wrote:
__asm__(".symver memcpy,memcpy@GLIBC_2.2.5");
In the source code.
ps: This is somewhat hackish (or "advanced vodoo" if you want a positive word for it :-D ) It is expected and intended to work just fine, however I strongly suggest you to use as a last resort.
I hoped that there is a compiler or linker option to achieve this. I do not what to change the source because then the danger exists that I accidentally check the hack in.
Christoph
Use osc ? It means making a spec but then osc will build in like 15 or more suse environments more or less effortlessly. Several other non-suse too but with more effort. (after the effort of learning how to use osc and making a good spec file in the first place) Similarly you could use obs but the devel cycle to get to a working spec file and a working compile will be faster with osc locally. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/01/12 16:23, Christoph Bartoschek wrote:
Am 25.01.2012 16:28, schrieb Cristian Rodríguez:
On 25/01/12 12:17, Cristian Rodríguez wrote:
__asm__(".symver memcpy,memcpy@GLIBC_2.2.5");
I hoped that there is a compiler or linker option to achieve this.
that *IS* a linker instruction :-D
I do not what to change the source because then the danger exists that I accidentally check the hack in.
You may also want to change calls of memcpy to memmove, which will do almost the same thing and will not demand a new version of the glibc symbol. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Am 25.01.2012 20:46, schrieb Cristian Rodríguez:
On 25/01/12 16:23, Christoph Bartoschek wrote:
Am 25.01.2012 16:28, schrieb Cristian Rodríguez:
On 25/01/12 12:17, Cristian Rodríguez wrote:
__asm__(".symver memcpy,memcpy@GLIBC_2.2.5");
I hoped that there is a compiler or linker option to achieve this.
that *IS* a linker instruction :-D
Yes, but it is in the source code. I check whether I can change memcpy to memmove. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 25/01/12 16:23, Christoph Bartoschek wrote:
I hoped that there is a compiler or linker option to achieve this. I do not what to change the source because then the danger exists that I accidentally check the hack in.
a Third possible hack is to use __builtin_memcpy instead. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Brian K. White -
Christoph Bartoschek -
Cristian Rodríguez