From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-amarula@amarulasolutions.com,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] package/ntpsec: fix host building
Date: Tue, 20 Aug 2024 23:36:47 +0200 [thread overview]
Message-ID: <ZsUMb1U7cYJvrODe@landeda> (raw)
In-Reply-To: <20240820172343.2124306-1-dario.binacchi@amarulasolutions.com>
Dario, All,
On 2024-08-20 19:23 +0200, Dario Binacchi spake thusly:
> The following build failure on xtensa:
>
> Waf: Entering directory `/home/buildroot/instance-0/output-1/build/ntpsec-1.2.3/build/host'
> [1/2] Processing ntpd/ntp_parser.y
> [2/2] Compiling build/host/ntpd/ntp_parser.tab.c
> gcc: error: unrecognized command-line option '-mlongcalls'
> gcc: error: unrecognized command-line option '-mauto-litpools'
>
> reveals that the target's CFLAGS are being used for host compilation.
> The patch fixes the host compilation by correctly setting the CFLAGS to
> be used.
>
> It should be noted that the build script used by ntpsec applies CFLAGS
> for host compilation and --cross-cflags for target compilation.
>
> Fixes:
> - http://autobuild.buildroot.org/results/9321a637f2c340ce8dcb24249676bb6c44d0dfc6
I've added a little blurb that explains how long it has been happening,
so what branches it should be backported to.
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> Changes v1 -> v2:
> - Rework the patch following the suggestion of Thomas Petazzoni.
> - Update the commit message
>
> package/ntpsec/ntpsec.mk | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/package/ntpsec/ntpsec.mk b/package/ntpsec/ntpsec.mk
> index 661af788423c..3acf7745cf07 100644
> --- a/package/ntpsec/ntpsec.mk
> +++ b/package/ntpsec/ntpsec.mk
> @@ -42,6 +42,7 @@ NTPSEC_DEPENDENCIES = \
> # --cross-compiler
> NTPSEC_CONF_OPTS = \
> CC="$(HOSTCC)" \
> + CFLAGS="$(HOST_CFLAGS)" \
> PYTHON_CONFIG="$(STAGING_DIR)/usr/bin/python3-config" \
> --libdir=/usr/lib/python$(PYTHON3_VERSION_MAJOR)/site-packages/ntp \
> --cross-compiler="$(TARGET_CC)" \
> --
> 2.43.0
>
> _______________________________________________
> buildroot mailing list
> buildroot@buildroot.org
> https://lists.buildroot.org/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| 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-08-20 21:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 17:23 [Buildroot] [PATCH v2] package/ntpsec: fix host building Dario Binacchi
2024-08-20 21:36 ` Thomas Petazzoni via buildroot
2024-08-20 21:36 ` Yann E. MORIN [this message]
2024-08-20 21:41 ` Yann E. MORIN
2024-09-18 11:14 ` 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=ZsUMb1U7cYJvrODe@landeda \
--to=yann.morin.1998@free.fr \
--cc=buildroot@buildroot.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=linux-amarula@amarulasolutions.com \
--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.