bitbake-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: Kenth Eriksson <Kenth.Eriksson@infinera.com>
To: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: reproducible build and yocto sdk
Date: Mon, 29 May 2023 09:53:02 +0000	[thread overview]
Message-ID: <MW5PR10MB5713792CCE8B2C1E5E89AF8AE34A9@MW5PR10MB5713.namprd10.prod.outlook.com> (raw)

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

I'm having issues with reproducible builds on kirkstone when comparing a build driven by bitbake compared to a build driven from a yocto sdk. Can I expect reproducible build between bitbake builds and sdk builds? Some produced binaries have minor differences, but larger c++ binaries show quite huge diff. One common difference is that the ELF header seems to have different OS/ABI between the two builds. Can binutils on different host give such a result?

diffoscope

│┄ File has been modified after NT_GNU_BUILD_ID has been applied.
├── readelf --wide --file-header {}
│ @@ -1,20 +1,20 @@
│  ELF Header:
│ -  Magic:   7f 45 4c 46 01 01 01 03 00 00 00 00 00 00 00 00
│ +  Magic:   7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
│    Class:                             ELF32
│    Data:                              2's complement, little endian
│    Version:                           1 (current)
│ -  OS/ABI:                            UNIX - GNU
│ +  OS/ABI:                            UNIX - System V
│    ABI Version:                       0
│    Type:                              DYN (Position-Independent Executable file)
│    Machine:                           ARM
│    Version:                           0x1
│    Entry point address:               0x1f04
│    Start of program headers:          52 (bytes into file)
│ -  Start of section headers:          41316 (bytes into file)
│ +  Start of section headers:          41328 (bytes into file)


Thanks,
Kenth

[-- Attachment #2: Type: text/html, Size: 4510 bytes --]

             reply	other threads:[~2023-05-29  9:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-29  9:53 Kenth Eriksson [this message]
2023-05-29 13:43 ` [bitbake-devel] reproducible build and yocto sdk Richard Purdie

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=MW5PR10MB5713792CCE8B2C1E5E89AF8AE34A9@MW5PR10MB5713.namprd10.prod.outlook.com \
    --to=kenth.eriksson@infinera.com \
    --cc=bitbake-devel@lists.openembedded.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 NNTP newsgroup(s).