public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "js5506 at columbia dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/92247] ‘__NR_open’ was not declared in this scope libsanitizer/sanitizer_common/sanitizer_linux compilation failed on ubuntu 18.04 WSL2
Date: Tue, 11 Aug 2020 06:43:24 +0000 [thread overview]
Message-ID: <bug-92247-4-u92OJfTozG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92247-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92247
js5506 at columbia dot edu changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |js5506 at columbia dot edu
--- Comment #12 from js5506 at columbia dot edu ---
(In reply to fdlbxtqi from comment #10)
> I have found out the reason.
>
> I created the incorrect soft link. /usr/include/asm should link to
> x86_64-linux-gnu/asm/ instead of asm-generic
>
>
> Solution:
>
> cd /usr/include
> sudo rm asm
> sudo ln -s x86_64-linux-gnu/asm/ asm
>
>
> https://blog.csdn.net/yihui8/article/details/8620914
Where is /usr/include/asm?
parent reply other threads:[~2020-08-11 6:43 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-92247-4@http.gcc.gnu.org/bugzilla/>]
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-92247-4-u92OJfTozG@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).