Advanced search

Message boards : Number crunching : GLIBC

Post to thread Subscribe Sort
Author Message
cenit
Send message
Joined: 11 Nov 09
Posts: 23
Credit: 668,841
RAC: 0
Level
Gly
Scientific publications
watwat
Message 27130 - Posted: 23 Oct 2012 | 13:50:41 UTC

the "old" application using cuda31 is compiled with an "older" GLIBC, while the new one cuda42 does not. Could you please compile the new application linking to the same old GLIBC or am I the only one asking for it?
In particular, I'm talking about keeping a compatibility with a RHEL 5 (which is still compatible with cuda5, so I'm not asking about not using new features)...

ID: 27130 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
Profile GDF
Volunteer moderator
Project administrator
Project developer
Project tester
Volunteer developer
Volunteer tester
Project scientist
Send message
Joined: 14 Mar 07
Posts: 1957
Credit: 629,356
RAC: 0
Level
Gly
Scientific publications
watwatwatwatwat
Message 27146 - Posted: 24 Oct 2012 | 18:18:51 UTC - in response to Message 27130.

yes we can do this as soon as the new app is out.
However the nvidia libs distributed with acemd are also dependent on the new glibc.
so you need to override it.

gdf

ID: 27146 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
cenit
Send message
Joined: 11 Nov 09
Posts: 23
Credit: 668,841
RAC: 0
Level
Gly
Scientific publications
watwat
Message 27153 - Posted: 25 Oct 2012 | 9:21:41 UTC - in response to Message 27146.

yes we can do this as soon as the new app is out.
However the nvidia libs distributed with acemd are also dependent on the new glibc.
so you need to override it.

gdf

well it depends on which toolkit you use, not?
For compatibility with as many users as possible, maybe you should use the sdk for CentOS/RHEL 5 or something like that. In this way, every nvidia lib should link to old-enough glibc for everyone... While, for example, if you use the toolkit for fedora 16, it's almost sure that it would link to bleeding-edge glibc.
Maybe just for a test, I don't know. Because I'm sure that dynamically linking to an older glibc should improve the compatibility for the userbase while on the other hand should not give any performance hit. You want the newest cuda libs, whatever the system libs are, am I right?
Of course, if I am the only one with this problem, I recognize that the trouble is not worth the effort and I'll crunch until it's possible (at the moment, I'm stuck with cuda31 apps, while on my workstation cuda5 is already available but not working with your app).

ID: 27153 | Rating: 0 | rate: Rate + / Rate - Report as offensive    Reply Quote
Post to thread

Message boards : Number crunching : GLIBC

//