All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/linux-tools: Exclude checking PE binaries from perf test
Date: Thu, 29 Sep 2022 08:40:06 +0200	[thread overview]
Message-ID: <20220929084006.64c0a629@windsurf> (raw)
In-Reply-To: <dda7b7d2-4846-6623-5ca7-39799015a138@gmail.com>

On Wed, 28 Sep 2022 15:28:58 -0700
Florian Fainelli <f.fainelli@gmail.com> wrote:

> ./host/bin/aarch64-linux-readelf -h 
> build/linux-custom/tools/perf/tests/pe-file.exe | sed -r -e '/^ 
> Machine: +(.+)/!d; s//\1/;' | head -1
> IMAGE_FILE_MACHINE_AMD64 (0x8664)

Could you provide the full output? In other words, I'm interested to
see if it's really readelf showing the same "Machine:" field as for
regular ELF files, or if it's something somewhat different that we
could distinguish.

> I should mention that the readelf binary in this case is the LLVM Object 
> Reader and it does support PE/COFF which is probably why it even 
> remotely attempts to parse the file.

How come your readelf is from LLVM? Are you using an external toolchain
that isn't based on the standard GNU Binutils?

Thanks!

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-09-29  6:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-27 22:11 [Buildroot] [PATCH] package/linux-tools: Exclude checking PE binaries from perf test Florian Fainelli
2022-09-28 21:38 ` Thomas Petazzoni
2022-09-28 22:28   ` Florian Fainelli
2022-09-29  6:40     ` Thomas Petazzoni [this message]
2022-09-30 22:05       ` Florian Fainelli
2022-10-01 19:07     ` Yann E. MORIN
2022-10-03 17:21       ` Florian Fainelli
2022-10-03 19:15         ` Yann E. MORIN
2023-04-17 19:58 ` Yann E. MORIN
2023-04-19  0:27   ` Florian Fainelli
2023-04-23 10:40 ` Peter Korsgaard

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=20220929084006.64c0a629@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@buildroot.org \
    --cc=f.fainelli@gmail.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 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.