All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Martin Wetterwald <martin@wetterwald.eu>
Cc: Vadim Kochan <vadim4j@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/tinysshd: Fix static-only build
Date: Sat, 31 Aug 2024 23:48:03 +0200	[thread overview]
Message-ID: <87msksuzxo.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20240725173709.1087549-1-martin@wetterwald.eu> (Martin Wetterwald's message of "Thu, 25 Jul 2024 19:37:09 +0200")

>>>>> "Martin" == Martin Wetterwald <martin@wetterwald.eu> writes:

 > When using BR2_STATIC_LIBS=y, tinysshd's build was successful, but the
 > binary didn't work on the final target: this is because a dynamically
 > linked ELF was produced, on a target having no dynamic loader at all.

 > Using $(TARGET_CONFIGURE_OPTS) propagates all the options and not only
 > "CC", resulting in a correct static binary able to run on the target.

 > Without the patch:

 >> tinysshd: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),
 >> dynamically linked, interpreter /lib/ld-musl-armhf.so.1, stripped

 > With the patch:

 >> tinysshd: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV),
 >> statically linked, stripped

 > Signed-off-by: Martin Wetterwald <martin@wetterwald.eu>

Committed to 2024.02.x and 2024.05.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2024-08-31 21:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-25 17:37 [Buildroot] [PATCH 1/1] package/tinysshd: Fix static-only build Martin Wetterwald
2024-07-26  7:19 ` Thomas Petazzoni via buildroot
2024-08-31 21:48 ` Peter Korsgaard [this message]

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=87msksuzxo.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@buildroot.org \
    --cc=martin@wetterwald.eu \
    --cc=vadim4j@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.