public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dingjun Chen <Dingjun.Chen@geotechairborne.com>
To: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Fw: What caused my executable file not to run on a Linux of old version 2.4.36.1
Date: Fri, 6 Oct 2023 15:33:57 +0000	[thread overview]
Message-ID: <YT2P288MB0073E02CECBFE4D3F8DE031997C9A@YT2P288MB0073.CANP288.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <YT2P288MB0073C2DC2CDAE9C52D2333EE97C9A@YT2P288MB0073.CANP288.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 2317 bytes --]

Hi again, Dear Sir or Madam,


Is the setting

set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=gnu++14") used in my CMakeLists.txt

having impact on the binary codes?

If so, what kind of setting for -std=????

I look forward to hearing from you.

Thanks and regards,

Dingjun
________________________________
From: Dingjun Chen
Sent: Friday, October 6, 2023 10:43 AM
To: gcc-help@gcc.gnu.org <gcc-help@gcc.gnu.org>
Subject: What caused my executable file not to run on a Linux of old version 2.4.36.1

Hi, Dear Sir or Madam,

I used the following gcc/g++ to build 32-bit executable file: vtem_xyz and please see the following information below:

dingjun@G02515:~/DAQ_XYZCross2_cmake/bin$ objdump -f vtem_xyz
vtem_xyz:     file format elf32-i386
architecture: i386, flags 0x00000150:
HAS_SYMS, DYNAMIC, D_PAGED
start address 0x000027d0

The Linux version and gcc/g++ version information are given below when building above executable file:

dingjun@G02515:~/DAQ_XYZCross2_cmake/bin$ uname -a
Linux G02515 5.15.90.1-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

dingjun@G02515:~/DAQ_XYZCross2_cmake/bin$ g++ --version
g++ (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

dingjun@G02515:~/DAQ_XYZCross2_cmake/bin$ gcc --version
gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Copyright (C) 2021 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.


However, the executable file: vtem_xyz cannot run on RTD single board computer with Linux 2.4.36.1 2009, i686.
All shared .so libraries are under the same directory with the executable file: vtem_xyz. I am wondering what's wrong with it.

Could you please tell me if your GNU libraries are compatible with the Linux of old version?  Do you have any suggestions when building an executable file running under a Linux of old version?

I look forward to your help and your reply would be greatly appreciated.

Thanks and regards,

Dingjun









  reply	other threads:[~2023-10-06 15:34 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 ` Dingjun Chen [this message]
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
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=YT2P288MB0073E02CECBFE4D3F8DE031997C9A@YT2P288MB0073.CANP288.PROD.OUTLOOK.COM \
    --to=dingjun.chen@geotechairborne.com \
    --cc=gcc-help@gcc.gnu.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 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).