linux-embedded.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: muzungu@gmx.net, linux-embedded@vger.kernel.org,
	linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Can I run an application compiled with gcc ABI 2.95 on a kernel compiled with gcc ABI 3.4?
Date: Fri, 15 May 2009 14:51:05 +0100	[thread overview]
Message-ID: <20090515135105.GC8235@shareable.org> (raw)
In-Reply-To: <1242390699.4201.3.camel@macbook.infradead.org>

David Woodhouse wrote:
> On Fri, 2009-05-15 at 13:50 +0200, muzungu@gmx.net wrote:
> > Questions:
> > - Can I run an application compiled with gcc ABI 2.95 on a kernel
> > compiled with gcc ABI 3.4?
> 
> Yes. The kernel ABI never changes in a backward-incompatible fashion.
> Unless you try switching your kernel to ARM EABI and don't update
> userspace to match -- don't do that :)

Eek, can you say a bit more about the ARM EABI mismatch?

I would like to run a shiny modern ARM EABI kernel and userspace, but
also need to run one or two OABI binaries (from the gcc 2.95 era) on
the same kernel which I cannot recompile because they're built with
closed source libraries only supplied as OABI.

Does that not work at all?

If it does work, which part of userspace must be EABI to work?

Thanks,
-- Jamie

  reply	other threads:[~2009-05-15 13:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-15 11:50 Can I run an application compiled with gcc ABI 2.95 on a kernel compiled with gcc ABI 3.4? muzungu
2009-05-15 12:31 ` David Woodhouse
2009-05-15 13:51   ` Jamie Lokier [this message]
2009-05-15 13:55     ` Ben Dooks
2009-05-15 14:32       ` George G. Davis
2009-05-15 14:54         ` Jamie Lokier
2009-05-15 14:56           ` Jamie Lokier
2009-05-15 21:42           ` Russell King - ARM Linux
2009-05-15 13:56     ` David Woodhouse
2009-05-15 14:03       ` Gustavo Zacarias
2009-05-15 16:31       ` Nicolas Pitre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090515135105.GC8235@shareable.org \
    --to=jamie@shareable.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-embedded@vger.kernel.org \
    --cc=muzungu@gmx.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).