From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/4591 Path: news.gmane.org!not-for-mail From: Justin Cormack Newsgroups: gmane.linux.lib.musl.general Subject: Re: How can I assess compatibility of a statically linked binary? Date: Thu, 20 Feb 2014 17:59:57 +0000 Message-ID: References: <53064077.30702@f-prot.com> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b6d7c5e00789304f2da462f X-Trace: ger.gmane.org 1392919202 7194 80.91.229.3 (20 Feb 2014 18:00:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 20 Feb 2014 18:00:02 +0000 (UTC) To: musl@lists.openwall.com Original-X-From: musl-return-4595-gllmg-musl=m.gmane.org@lists.openwall.com Thu Feb 20 19:00:12 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 1WGXut-0004Kh-Cv for gllmg-musl@plane.gmane.org; Thu, 20 Feb 2014 19:00:11 +0100 Original-Received: (qmail 17551 invoked by uid 550); 20 Feb 2014 18:00:10 -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 17534 invoked from network); 20 Feb 2014 18:00:10 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=specialbusservice.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=3F7yBoVgnmxr0dlf63tWJ+HDsv/s3b/WXaNBowWjkFU=; b=d0Qqh7bjd1uKEsjbo0OWkHtxm3SX2yAQCOO8b96kI8RueDpnmRfxnW1P7soHAP00HG dKCRkbb9IHsEc3kDIfdQ6MMSF19wuo8B20gH0nBepHI6jk54tJttTHb6UMbrh/wWTTa2 wKgw2Jb4go7au1w1W/M/Rua0SlRZanVbAS4tY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=3F7yBoVgnmxr0dlf63tWJ+HDsv/s3b/WXaNBowWjkFU=; b=glVQW6+RVyiMEXiRT7wiPlucM4hWV1PmyPgOWH3lW0OMWQA6Qw8g7WPDy6Bb6qZdIP 9VhOKM8BfAlm2cvqn2c+4ht76gXIgLVYXnNJ30iq+n/WxOPiGcK2XR91UyGEU2D79AE+ FSXAwlnE04bjL31/pK8rbUUEK2zlkB1lRfnf80iApwiUh475iD9wISlS4S5B1o/eJ9Tw rZYQjBkpoDDm2xVyPky89FYiv8K2Jphhw9dcsokP04fmv88IeSKZq6lO/2zeI/7GwkOu Kg6RnyiVXbD+EcVOLtiOyMrFFGXLDRoz43Nj2CEQOl/1nL92MucJEorQx/jYkBuRPstN 29Yg== X-Gm-Message-State: ALoCoQnmsvVaZH27qgpv8ceZo2vSu9ULkUiCKb6Xddt+jHD22ucVQSrKJW6kSP/B4i+KYeB7DZNH X-Received: by 10.66.155.133 with SMTP id vw5mr3669732pab.124.1392919198062; Thu, 20 Feb 2014 09:59:58 -0800 (PST) In-Reply-To: <53064077.30702@f-prot.com> Xref: news.gmane.org gmane.linux.lib.musl.general:4591 Archived-At: --047d7b6d7c5e00789304f2da462f Content-Type: text/plain; charset=UTF-8 On 20 Feb 2014 17:51, "Oliver Schneider" wrote: > > 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. > The Musl docs say which the earliest supported release is. From memory it is late 2.4 but I don't recall the exact version. If you don't use some functionality things might work on an earlier version of course. Justin --047d7b6d7c5e00789304f2da462f Content-Type: text/html; charset=UTF-8


On 20 Feb 2014 17:51, "Oliver Schneider" <musl-mailinglist@f-prot.com> wrote:
>
> 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.
>

The Musl docs say which the earliest supported release is. From memory it is late 2.4 but I don't recall the exact version. If you don't use some functionality things might work on an earlier version of course.

Justin

--047d7b6d7c5e00789304f2da462f--