From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4590 Path: news.gmane.org!not-for-mail From: Oliver Schneider Newsgroups: gmane.linux.lib.musl.general Subject: How can I assess compatibility of a statically linked binary? Date: Thu, 20 Feb 2014 17:50:47 +0000 Organization: CYREN Iceland Message-ID: <53064077.30702@f-prot.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1392918656 32030 80.91.229.3 (20 Feb 2014 17:50:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Feb 2014 17:50:56 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4594-gllmg-musl=m.gmane.org@lists.openwall.com Thu Feb 20 18:51:05 2014 Return-path: Envelope-to: gllmg-musl@plane.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by plane.gmane.org with smtp (Exim 4.69) (envelope-from ) id 1WGXm4-0006jk-IW for gllmg-musl@plane.gmane.org; Thu, 20 Feb 2014 18:51:04 +0100 Original-Received: (qmail 7923 invoked by uid 550); 20 Feb 2014 17:51:03 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Original-Received: (qmail 7911 invoked from network); 20 Feb 2014 17:51:02 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 X-Antivirus: Scanned by F-PROT Antivirus (http://www.f-prot.com) Xref: news.gmane.org gmane.linux.lib.musl.general:4590 Archived-At: Hi, when I have a file linked against glibc the file(1) utility will usually tell me something like this: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped However, when I run this on a statically linked binary that uses musl, I get ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, stripped which gives no indication of the minimum expected kernel. Does that mean that this binary will also run on, say, a 2.4.x kernel? I guess not? How can I tell which kernel interface a certain binary requires? After all the system call numbers on which the libc relies change every once in a while. Thanks, // Oliver