From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Joseph Kogut <joseph.kogut@gmail.com>,
Romain Naour <romain.naour@gmail.com>,
Daniel Lang <dalang@gmx.at>,
Valentin Korenblit <valentinkorenblit@gmail.com>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/llvm-project/clang: update patch to be applied with fuzz 0
Date: Mon, 1 Jul 2024 22:49:33 +0200 [thread overview]
Message-ID: <ZoMWXfYLDtjGT8dy@landeda> (raw)
In-Reply-To: <20240630153126.259530-1-bernd@kuhls.net>
Bernd, All,
On 2024-06-30 17:31 +0200, Bernd Kuhls spake thusly:
> Commit 8f88a644ed "support/scripts/apply-patches.sh: set the maximum
> fuzz factor to 0" reduced the fuzz factor.
>
> Due to this change, host-clang fails to build with output:
>
> Applying 0001-lib-Driver-ToolChains-Gnu-Use-GCC_INSTALL_PREFIX-in-.patch using patch:
> patching file lib/Driver/ToolChains/Gnu.cpp
> Hunk #1 FAILED at 1725.
> Hunk #2 succeeded at 2011 (offset 277 lines).
> 1 out of 2 hunks FAILED -- saving rejects to file lib/Driver/ToolChains/Gnu.cpp.rej
>
> Rebase the patch to fix the problem.
>
> Fixes:
> http://autobuild.buildroot.net/results/75b/75baa62275d64c699d9757f7c756fc03ea717877/
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
Applied to master, thanks.
Regards,
Yann E. MORIN.
> ---
> ...1-lib-Driver-ToolChains-Gnu-Use-GCC_INSTALL_PREFIX-in-.patch | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/llvm-project/clang/0001-lib-Driver-ToolChains-Gnu-Use-GCC_INSTALL_PREFIX-in-.patch b/package/llvm-project/clang/0001-lib-Driver-ToolChains-Gnu-Use-GCC_INSTALL_PREFIX-in-.patch
> index 08371154d5..ffdd5d187f 100644
> --- a/package/llvm-project/clang/0001-lib-Driver-ToolChains-Gnu-Use-GCC_INSTALL_PREFIX-in-.patch
> +++ b/package/llvm-project/clang/0001-lib-Driver-ToolChains-Gnu-Use-GCC_INSTALL_PREFIX-in-.patch
> @@ -44,7 +44,7 @@ index 2ad45097dc..90d6b5b748 100644
> +++ b/lib/Driver/ToolChains/Gnu.cpp
> @@ -1725,6 +1725,8 @@ void Generic_GCC::GCCInstallationDetector::init(
>
> - Prefixes.push_back(GCCToolchainDir);
> + Prefixes.push_back(std::string(GCCToolchainDir));
> } else {
> + StringRef GccIinstallPrefix = GCC_INSTALL_PREFIX;
> +
> --
> 2.39.2
>
> _______________________________________________
> 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
prev parent reply other threads:[~2024-07-01 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-30 15:31 [Buildroot] [PATCH 1/1] package/llvm-project/clang: update patch to be applied with fuzz 0 Bernd Kuhls
2024-07-01 20:49 ` Yann E. MORIN [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=ZoMWXfYLDtjGT8dy@landeda \
--to=yann.morin.1998@free.fr \
--cc=bernd@kuhls.net \
--cc=buildroot@buildroot.org \
--cc=dalang@gmx.at \
--cc=joseph.kogut@gmail.com \
--cc=romain.naour@gmail.com \
--cc=valentinkorenblit@gmail.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.