From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Woodrow Douglass via buildroot <buildroot@buildroot.org>
Cc: Woodrow Douglass <wdouglass@carnegierobotics.com>
Subject: Re: [Buildroot] [PATCH] package/chicken: move literals into text section for xtensa architecture
Date: Fri, 2 Aug 2024 19:10:56 +0200 [thread overview]
Message-ID: <20240802191056.30ca5678@windsurf> (raw)
In-Reply-To: <20240722173136.412283-1-wdouglass@carnegierobotics.com>
Hello Woodrow,
On Mon, 22 Jul 2024 13:31:36 -0400
Woodrow Douglass via buildroot <buildroot@buildroot.org> wrote:
> This solves a build problem -- by default xtensa-gcc puts literals in a
> different section of memory then the program text, and chicken is a very
> literal-heavy program, so they don't all fit there. This avoids that problem.
>
> Signed-off-by: Woodrow Douglass <wdouglass@carnegierobotics.com>
Thanks, I have applied your patch, with a few fixes.
First, I've added a reference to an autobuilder failure fixed by this
patch, as follows:
"""
Fixes:
http://autobuild.buildroot.net/results/ce36170d67c4702f34bee025d8a46e5269c4573e/
"""
> -# If ARCH is not set, it attempts to autodiscover. But it is anyway not used.
> +#Chicken only uses the "arch" variable for some special-case compile arguments
> +#If it's empty, it tries to detect the arch host
> +#Filter out values that have an effect, or pass "unused" here
We always put a space after the # sign starting a comment.
> +ifeq ($(BR2_NORMALIZED_ARCH),"x86_64")
I've used $(NORMALIZED_ARCH) instead, which already has double quotes
stripped, so instead of "x86_64" we can use just x86_64.
> +CHICKEN_ARCH="x86-64"
Spaces around = sign, no double quotes around x86-64.
> +else ifeq ($(BR2_NORMALIZED_ARCH),"xtensa")
> +CHICKEN_ARCH="xtensa"
> +else
> +CHICKEN_ARCH="unused"
> +endif
> +
> CHICKEN_MAKE_OPTS = \
> - ARCH=unused \
> + ARCH=$(CHICKEN_ARCH) \
and instead, used ARCH="$(CHICKEN_ARCH)" here
Thanks a lot!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-08-02 17:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 13:11 [Buildroot] [PATCH] package/chicken: move literals into text section for xtensa architecture Woodrow Douglass via buildroot
2024-07-22 13:41 ` Thomas Petazzoni via buildroot
2024-07-22 14:30 ` Woodrow Douglass via buildroot
2024-07-22 14:57 ` Baruch Siach via buildroot
2024-07-22 15:07 ` Woody Douglass via buildroot
2024-07-22 15:08 ` Woodrow Douglass via buildroot
2024-07-22 16:15 ` Thomas Petazzoni via buildroot
2024-07-22 17:24 ` Woody Douglass via buildroot
2024-07-22 17:31 ` Woodrow Douglass via buildroot
2024-08-02 17:10 ` Thomas Petazzoni via buildroot [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=20240802191056.30ca5678@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=wdouglass@carnegierobotics.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox