This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Building for older systems
- From: "Carlos O'Donell" <carlos at redhat dot com>
- To: Michael Eager <eager at eagerm dot com>, Ãngel GonzÃlez <keisial at gmail dot com>
- Cc: libc-help at sourceware dot org
- Date: Tue, 1 Dec 2015 11:04:29 -0500
- Subject: Re: Building for older systems
- Authentication-results: sourceware.org; auth=none
- References: <565B0993 dot 7040202 at eagerm dot com> <565BA0CA dot 4070102 at gmail dot com> <565DB6B8 dot 607 at eagerm dot com>
On 12/01/2015 10:03 AM, Michael Eager wrote:
> On 11/29/2015 05:05 PM, Ãngel GonzÃlez wrote:
>> On 29/11/15 15:20, Michael Eager wrote:
>>> I'm trying to build packages (gcc, etc.) on a newer
>>> version of Linux which can run on an older Linux system
>>> with an older glibc. I've run into the memcpy versioning
>>> problem._2.14
>>> (...)
>>> Any solutions to building for an older glibc?
>>>
>>
>> If you just want to work around the memcpy 2.14 version bump, you can:
>> a) #define memcpy memmove
>
> That is more or less equivalent to including a .symver for memcpy.
>
> The problem is that this needs to be included in each of many thousands
> of source files.
I have done this using gcc's `-include` command-line directive to put
a header into every source file compiled.
It's still not the recommended way :-)
c.