All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alexey Brodkin via buildroot <buildroot@buildroot.org>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
	"Yann E . MORIN" <yann.morin.1998@free.fr>,
	Vladimir Isaev <VVIsaev@gmail.com>,
	Pavel Kozlov <Pavel.Kozlov@synopsys.com>
Subject: Re: [Buildroot] [PATCH v2] arch: Set max/common-page-size for libgcc & libstdc++
Date: Fri, 5 Jan 2024 23:50:52 +0100	[thread overview]
Message-ID: <20240105235052.1f70db20@windsurf> (raw)
In-Reply-To: <20240105191710.1330461-1-abrodkin@synopsys.com>

On Fri,  5 Jan 2024 11:17:10 -0800
Alexey Brodkin via buildroot <buildroot@buildroot.org> wrote:

> With [1], [2] & [3] we made sure Buildroot packages get built with
> proper MMU page size assumed. This was done nicely through insertion of
> required flags into the toolchain wrapper so that there's no need to
> pass these flags to each and every package separately - toolchain
> wrapper used for real building has all set internally and so proper
> flags are impleicitly used.
> 
> But there's yet another corner case which is not handled that way -
> these are binaries or rather libraries which are being used as a part of
> GCC compilation: libgcc_s.so.1 and libstdc++.so.
> 
> And so to make sure both the libraries get built properly we need to set
> TARGET_CFLAGS (cures libgcc_s.so) & TARGET_LDFLAGS (cures libstdc++.so).
> 
> In case of ARM by defaut 64 KiB page size seems to be used, as w/o that
> patch I see the following for BR2_ARM64_PAGE_SIZE_4K=y:
> --------------------------->8----------------------------  
> $ ./output/host/bin/aarch64-linux-readelf -l ./output/target/lib/libgcc_s.so.1

Applied to master with a few minor improvements in the commit title and
commit log. Thanks a lot!

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

  reply	other threads:[~2024-01-05 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-05 19:17 [Buildroot] [PATCH v2] arch: Set max/common-page-size for libgcc & libstdc++ Alexey Brodkin via buildroot
2024-01-05 22:50 ` Thomas Petazzoni via buildroot [this message]
2024-01-12 18:41 ` 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=20240105235052.1f70db20@windsurf \
    --to=buildroot@buildroot.org \
    --cc=Alexey.Brodkin@synopsys.com \
    --cc=Pavel.Kozlov@synopsys.com \
    --cc=VVIsaev@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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.