From: Peter Korsgaard <peter@korsgaard.com>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: "Köry Maincent" <kory.maincent@bootlin.com>,
"Louis Chauvet" <louis.chauvet@bootlin.com>,
"Sergey Matyukevich" <geomatsi@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] boot/arm-trusted-firmware: fix the RPATH of fiptool
Date: Wed, 03 Jan 2024 14:31:57 +0100 [thread overview]
Message-ID: <878r565yr6.fsf@48ers.dk> (raw)
In-Reply-To: <20240103134654.3240d15a@windsurf> (Thomas Petazzoni's message of "Wed, 3 Jan 2024 13:46:54 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> On Wed, 03 Jan 2024 14:39:18 +0200
> Baruch Siach <baruch@tkos.co.il> wrote:
>> The last defconfig test report shows these failures:
>>
>> https://lists.buildroot.org/pipermail/buildroot/2023-December/681835.html
>>
>> For example (solidrun_macchiatobin):
>>
>> https://gitlab.com/buildroot.org/buildroot/-/jobs/5834758777
> I guess:
> HOSTCC="$(HOSTCC) $(HOST_LDFLAGS)"
> should be:
> HOSTCC="$(HOSTCC) $(HOST_CPPFLAGS) $(HOST_LDFLAGS)"
> However, I don't understand how it could have worked for us without
> this.
I can confirm that the build fails with the current patch and works
after adding HOST_CPPFLAGS.
Can you send a patch for it for master?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2024-01-03 13:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-08 17:42 [Buildroot] [PATCH v2] boot/arm-trusted-firmware: fix the RPATH of fiptool Louis Chauvet via buildroot
2023-12-08 21:29 ` Yann E. MORIN
2024-01-03 12:01 ` Peter Korsgaard
2024-01-03 12:10 ` Baruch Siach via buildroot
2024-01-03 12:29 ` Peter Korsgaard
2024-01-03 12:39 ` Baruch Siach via buildroot
2024-01-03 12:46 ` Thomas Petazzoni via buildroot
2024-01-03 13:31 ` Peter Korsgaard [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=878r565yr6.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=geomatsi@gmail.com \
--cc=kory.maincent@bootlin.com \
--cc=louis.chauvet@bootlin.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.