From: Xi Ruoyao <xry111@xry111.site>
To: Dingjun Chen <Dingjun.Chen@geotechairborne.com>,
Kai Ruottu <kai.ruottu@wippies.com>,
Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: What caused my executable file not to run on a Linux of old version 2.4.36.1
Date: Tue, 10 Oct 2023 20:36:31 +0800 [thread overview]
Message-ID: <c09dd3dc667cbcd150ee30eee95273ee7446f2d3.camel@xry111.site> (raw)
In-Reply-To: <YT2P288MB0073A180106966A3D9775AFB97CDA@YT2P288MB0073.CANP288.PROD.OUTLOOK.COM>
On Tue, 2023-10-10 at 10:28 +0000, Dingjun Chen wrote:
>
> Hi, Ruoyao and Kai,
>
> The kernel is too old and Please see errors occurred below. You
> mentioned "because the executable may use symbols which don't exist in
> the old Glibc" and You are right. How to fix it?
I've told you:
Build a cross compiler and use the root FS of the target board as the
sysroot.
> By the way, the GNU ld command is 64-bit. However I want to build 32-
> bit executables.
The 64-bit ld can link 32-bit executables (with -m elf_i386).
> dingjun@G02515:~/DAQ_XYZCross2_cmake/build$ objdump -f /usr/bin/ld
> /usr/bin/ld: file format elf64-x86-64
> architecture: i386:x86-64, flags 0x00000150:
> HAS_SYMS, DYNAMIC, D_PAGED
> start address 0x0000000000048630
>
> Can I fix such an error with 32-bit ld?
No.
> Which GNU C/C++ compiler version can offer us a 32-bit ld to link the
> objects?
ld is not a part of GCC.
> I look forward to your help!
But now this is just being annoying. You are lacking some common
knowledge about how a program is linked and executed. gcc-help is not
for teaching these common knowledge.
Try to find a textbook.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-10-10 12:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 14:43 Dingjun Chen
2023-10-06 15:33 ` Fw: " Dingjun Chen
2023-10-06 17:07 ` Jonathan Wakely
2023-10-07 6:18 ` Xi Ruoyao
2023-10-07 11:19 ` Kai Ruottu
2023-10-10 10:28 ` Dingjun Chen
2023-10-10 12:36 ` Xi Ruoyao [this message]
2023-10-10 12:30 ` Dingjun Chen
2023-10-10 17:13 ` Dingjun Chen
2023-10-10 17:41 ` Kai Ruottu
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=c09dd3dc667cbcd150ee30eee95273ee7446f2d3.camel@xry111.site \
--to=xry111@xry111.site \
--cc=Dingjun.Chen@geotechairborne.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=kai.ruottu@wippies.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).