From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 215862] clang-15 fails ppc64 BE kernel build - ld.lld: error: undefined symbol: .early_setup
Date: Tue, 15 Nov 2022 23:11:50 +0000 [thread overview]
Message-ID: <bug-215862-206035-FlNNdaAEax@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215862-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215862
Erhard F. (erhard_f@mailbox.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |https://github.com/ClangBui
| |ltLinux/linux/issues/1761
--- Comment #4 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Christophe Leroy from comment #3)
> If not already done, can you report the problem at
> https://github.com/ClangBuiltLinux/linux/issues
I was not aware of this issue tracker. Thanks for the hint!
Filed now unter https://github.com/ClangBuiltLinux/linux/issues/1761
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-11-15 23:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 14:12 [Bug 215862] New: clang-14 fails 5.18-rc3 ppc64 BE kernel build - <unknown>:0: error: expected relocatable expression bugzilla-daemon
2022-11-15 18:48 ` [Bug 215862] clang-15 fails ppc64 BE kernel build - ld.lld: error: undefined symbol: .early_setup bugzilla-daemon
2022-11-15 18:49 ` bugzilla-daemon
2022-11-15 20:08 ` bugzilla-daemon
2022-11-15 23:11 ` bugzilla-daemon [this message]
2023-07-31 10:22 ` bugzilla-daemon
2023-07-31 10:23 ` bugzilla-daemon
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=bug-215862-206035-FlNNdaAEax@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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.