From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: Woodrow Douglass <wdouglass@carnegierobotics.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [git commit] package/chicken: move literals into text section for xtensa architecture
Date: Fri, 2 Aug 2024 22:05:48 +0200 [thread overview]
Message-ID: <20240802220548.1e6676f9@windsurf> (raw)
In-Reply-To: <CAMo8Bf+5XSQyEp1ZP1UbqL7DF=VLfWbUuA-3OFY9M7WENn0GaA@mail.gmail.com>
On Fri, 2 Aug 2024 11:00:02 -0700
Max Filippov <jcmvbkbc@gmail.com> wrote:
> > It causes build failures:
> >
> > http://autobuild.buildroot.net/results/ce36170d67c4702f34bee025d8a46e5269c4573e/
>
> I see the following in the build-end.log:
>
> /home/autobuild/autobuild/instance-2/output-1/per-package/chicken/host/bin/xtensa-buildroot-linux-uclibc-gcc
> -fno-strict-aliasing -fwrapv -DHAVE_CHICKEN_CONFIG_H
> -DC_ENABLE_PTABLES -c -Os -fomit-frame-pointer -fPIC -DPIC
> -DC_BUILDING_LIBCHICKEN library.c -o library.o -I. -I./
>
> There's no TARGET_CFLAGS in this command line.
Hm, indeed!
So, Woodrow, could you have a look at the chicken build system, and why
our CFLAGS are not passed down to the build?
Thanks!
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
next prev parent reply other threads:[~2024-08-02 20:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 17:06 [Buildroot] [git commit] package/chicken: move literals into text section for xtensa architecture Thomas Petazzoni via buildroot
2024-08-02 17:24 ` Max Filippov
2024-08-02 17:43 ` Thomas Petazzoni via buildroot
2024-08-02 18:00 ` Max Filippov
2024-08-02 20:05 ` Thomas Petazzoni via buildroot [this message]
2024-08-05 15:47 ` Woody Douglass 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=20240802220548.1e6676f9@windsurf \
--to=buildroot@buildroot.org \
--cc=jcmvbkbc@gmail.com \
--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