Movatterモバイル変換

This is the mail archive of thebinutils@sources.redhat.commailing list for thebinutils project.

Binding to a specified symbol version

• From: Mike Hearn <m dot hearn at signal dot qinetiq dot com>
• To: binutils at sources dot redhat dot com
• Date: 30 Jun 2003 11:17:16 +0100
• Subject: Binding to a specified symbol version
• Organization: QinetiQ - Malvern Technology Center

Hi,In the ld manual, here:http://sources.redhat.com/binutils/docs-2.12/ld.info/VERSION.html#VERSIONit says at the bottom that you can use the .symver directive to bind toa specific version (ie not the default version) of a symbol, but itdoesn't give any examples or explain further. Could somebody pleaseexplain how I would for instance choose an old glibc symbol version formy application to bind to when compiling my app? Also, is there a way to externally "graft" these selections onto anapplication automatically, ie without altering the source too much.The reason I'm asking is that I'd like to be able to compile binaries towork with older versions of Linux than the one on our developermachines, but the only ways I've found to do this so far are:a) Install an older version of a distro and compile using that (butthat's a lot of hassle and you run into problems with compiler versionsetc)b) Compile using stub libraries. The LSB provides some, butunfortunately if you also try to link against other libraries on thesystem ld seems to try and resolve the entire symbol set, not just theones for the program it's linking. The only solution to *that* I'vefound is to make ALL the libraries being linked against temporary stublibraries, which is awfully ugly, not to mention slow and confusing.So, I'd really like to be simply able to tell ld which glibc versions touse, but the manual doesn't make it clear to me how.many thanks to anybody that can help-mike-- Mike Hearn <m.hearn@signal.qinetiq.com>QinetiQ - Malvern Technology Center