From: muzungu@gmx.net
To: linux-embedded@vger.kernel.org
Subject: 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 13:50:09 +0200 [thread overview]
Message-ID: <20090515115009.110740@gmx.net> (raw)
Hello all
We have a target system with an old Linux environment that we can not easily upgrade to a new one.
The actual development system (linux) has more or less the same age (prox. 10 year)
We intend to do the following:
- Use a new distribution as development environment (linux)
- Still compile the target application for the old system (2.2 and 2.4 kernels, once all compiled with egcs 2.91.66)
- Test the target applications in the new development environment
Questions:
- Can I run an application compiled with gcc ABI 2.95 on a kernel compiled with gcc ABI 3.4?
- In other words: does it matter if the gcc ABI of the compilers for the kernel and the application are different, assuming all the libraries used, have the same gcc ABI as the application?
I guess:
- gcc ABI of librabies and applications compilation must generally match
- gcc ABI of kernel, libraries and applications compilation must generally match to.
Am I wrong?
I would appreciate any help
Roman
--
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss für nur 17,95 Euro/mtl.!* http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a
next reply other threads:[~2009-05-15 11:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 11:50 muzungu [this message]
2009-05-15 12:31 ` Can I run an application compiled with gcc ABI 2.95 on a kernel compiled with gcc ABI 3.4? David Woodhouse
2009-05-15 13:51 ` Jamie Lokier
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=20090515115009.110740@gmx.net \
--to=muzungu@gmx.net \
--cc=linux-embedded@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.