From: "Uwe Kleine-König" <uwe@kleine-koenig.org>
To: linux-sparse@vger.kernel.org
Subject: sparse fails to build against llvm16
Date: Sat, 16 Sep 2023 17:49:31 +0200 [thread overview]
Message-ID: <e482a4de-55f3-25bd-4938-af05ad553b7d@kleine-koenig.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1117 bytes --]
Hello,
Debian upgraded llvm to version 16 and sparse fails to build against
this with:
g++ -L/usr/lib/llvm-16/lib -Wl,-z,relro -Wl,-z,now -Wl,--as-needed
sparse-llvm.o libsparse.a -lLLVM-16 -o sparse-llvm
/usr/bin/ld: sparse-llvm.o: in function `get_sym_value':
././sparse-llvm.c:305:(.text+0x7b2): undefined reference to `LLVMConstGEP'
/usr/bin/ld: sparse-llvm.o: in function `calc_gep':
././sparse-llvm.c:488:(.text+0xe37): undefined reference to
`LLVMBuildInBoundsGEP'
/usr/bin/ld: sparse-llvm.o: in function `output_op_load':
././sparse-llvm.c:714:(.text+0x24a9): undefined reference to `LLVMBuildLoad'
/usr/bin/ld: sparse-llvm.o: in function `output_op_call':
././sparse-llvm.c:822:(.text+0x262e): undefined reference to `LLVMBuildCall'
collect2: error: ld returned 1 exit status
(See https://bugs.debian.org/1051864 for the corresponding bug report. A
quick workaround could be to disable llvm-support in sparse to prevent
sparse from being dropped from Debian unstable.)
After a quick internet search I didn't find the obvious fix for that.
Any hints?
Best regards
Uwe
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2023-09-16 15:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e482a4de-55f3-25bd-4938-af05ad553b7d@kleine-koenig.org \
--to=uwe@kleine-koenig.org \
--cc=linux-sparse@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).