From: "G.B." <rm-dash-bau-haus@dash.futureapps.de>
Subject: Re: GLIBC_2.14 memcpy
Date: Wed, 23 Apr 2014 13:11:13 +0200
Date: 2014-04-23T13:10:58+02:00 [thread overview]
Message-ID: <53579fc2$0$6704$9b4e6d93@newsspool2.arcor-online.net> (raw)
In-Reply-To: <85y4yw4hcj.fsf@stephe-leake.org>
On 23.04.14 09:47, Stephen Leake wrote:
> Ian Douglas <ian@vionia.com> writes:
>
>> So I write my first hello world program, and it runs fine. Upload to
>> the server, but it does not run there.
>>
>> ./Hello1: /lib64/libc.so.6: version `GLIBC_2.14' not found (required
>> by ./Hello1)
>
> Use static rather than dynamic linking.
>
With glibc, static linking may work only to some extent.
It may work in this case.
IIRC, some networking routines will still be linked at run time.
Similarly, I'd prefer not to have linked libssl1.0.1 statically. ;-)
next prev parent reply other threads:[~2014-04-23 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 13:28 GLIBC_2.14 memcpy Ian Douglas
2014-04-22 16:54 ` Tero Koskinen
2014-04-22 19:41 ` Ian Douglas
2014-04-22 21:58 ` Jeffrey Carter
2014-04-23 7:47 ` Stephen Leake
2014-04-23 11:11 ` G.B. [this message]
2014-04-23 18:30 ` Ian Douglas
2014-04-23 7:53 ` anon
2014-04-23 18:37 ` Ian Douglas
2014-04-24 9:56 ` anon
2014-04-26 20:10 ` Ian Douglas
2014-04-28 12:23 ` anon
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox