From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: strip is missing?
Date: Wed, 02 Oct 2024 17:01:08 +0100 [thread overview]
Message-ID: <F1B18E88-8237-4D8A-886E-82C30B1BDE19@ipfire.org> (raw)
In-Reply-To: <f513e960-1129-41fe-8eb9-5d0053cd81b1@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Hello Matthias,
We are still stripping all binaries, but we don’t do it in the build system any more.
We basically strip them when we package everything:
https://git.ipfire.org/?p=ipfire-2.x.git;a=blob;f=lfs/Config;h=9fabe790c3b0e1f7dcba1b86593e59da0b42520a;hb=HEAD#l371
That makes the build slightly faster because we only strip what we actually need to strip and not the rest. It also allows us to have some files with debugging information enabled which we normally don’t have access to.
In the final system there should not be any unstripped binaries.
-Michael
> On 2 Oct 2024, at 14:14, Matthias Fischer <matthias.fischer(a)ipfire.org> wrote:
>
> Hi,
>
> today I built the updated 'suricata 7.0.7' and 'libhtp 0.5.49' with
> Core188 and Core189.
>
> Builds ran without problems - but the resulting binary in /usr/bin was
> somehow bigger than I expected: 63071K. It should have ~9.9K.
> It wasn't stripped.
>
> I looked for (e.g.) 'squid 6.11' - the same.
>
> It looks like 'strip' didn't run during the build process...
>
> Can anyone confirm?
>
> Best
> Matthias
next prev parent reply other threads:[~2024-10-02 16:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 13:14 Matthias Fischer
2024-10-02 16:01 ` Michael Tremer [this message]
2024-10-02 19:29 ` Matthias Fischer
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=F1B18E88-8237-4D8A-886E-82C30B1BDE19@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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