From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
Pavel Kozlov <Pavel.Kozlov@synopsys.com>,
Vladimir Isaev <VVIsaev@gmail.com>,
Alexey Brodkin via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH] arch: Set max/common-page-size for libgcc & libstdc++
Date: Thu, 4 Jan 2024 22:34:34 +0100 [thread overview]
Message-ID: <ZZckauC7K7-qR0lP@landeda> (raw)
In-Reply-To: <20240104221941.044adcb5@windsurf>
Thomas, Alexey, All,
On 2024-01-04 22:19 +0100, Thomas Petazzoni spake thusly:
> On Wed, 3 Jan 2024 02:23:11 -0800
> Alexey Brodkin via buildroot <buildroot@buildroot.org> wrote:
> > I would agree that it gets more and more ugly, but so far I cannot see
> > any more elegant solution. So if there're suggestions how to improve,
> > let's discuss.
[--SNIP--]
> But I'm surprised they are not needed also in the C library build. Why
> are you not seeing the same problem with the C library build, it should
> also need the same page size flags, doesn't it?
It is my understanding that the toolchain wrapper is installed as a post
initial gcc hook as well:
package/gcc/gcc-initial/gcc-initial.mk:
59 HOST_GCC_INITIAL_POST_BUILD_HOOKS += TOOLCHAIN_WRAPPER_BUILD
60 HOST_GCC_INITIAL_POST_INSTALL_HOOKS += TOOLCHAIN_WRAPPER_INSTALL
61 HOST_GCC_INITIAL_POST_INSTALL_HOOKS += HOST_GCC_INSTALL_WRAPPER_AND_SIMPLE_SYMLINKS
So the C libraries are built using our wrapper.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-01-04 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 10:23 [Buildroot] [PATCH] arch: Set max/common-page-size for libgcc & libstdc++ Alexey Brodkin via buildroot
2024-01-04 21:19 ` Thomas Petazzoni via buildroot
2024-01-04 21:34 ` Yann E. MORIN [this message]
2024-01-04 21:38 ` Thomas Petazzoni via buildroot
2024-01-04 22:22 ` Alexey Brodkin via buildroot
2024-01-04 22:42 ` Thomas Petazzoni via buildroot
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=ZZckauC7K7-qR0lP@landeda \
--to=yann.morin.1998@free.fr \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Pavel.Kozlov@synopsys.com \
--cc=VVIsaev@gmail.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.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.