From: Xi Ruoyao <xry111@xry111.site>
To: Tiezhu Yang <yangtiezhu@loongson.cn>,
Huacai Chen <chenhuacai@kernel.org>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH v3 0/8] Add objtool and orc support for LoongArch
Date: Fri, 20 Oct 2023 18:45:48 +0800 [thread overview]
Message-ID: <23a3ebe302f77db630edc52b23afb812f31f103e.camel@xry111.site> (raw)
In-Reply-To: <a967ebeb-f19d-4e36-3547-80e838ad2fa0@loongson.cn>
On Fri, 2023-10-20 at 18:28 +0800, Tiezhu Yang wrote:
> On 10/20/2023 04:51 PM, Huacai Chen wrote:
> > Cross compiling on X86 for LoongArch fails:
> >
> > CALL scripts/checksyscalls.sh
> > DESCEND objtool
> > make[5]: *** No rule to make target
> > '/usr/lib/gcc/x86_64-redhat-linux/8/include/stdbool.h', needed by
> > '/home/chenhuacai/linux-official.git/tools/objtool/libsubcmd/exec-cmd.o'.
> > Stop.
> > make[4]: *** [Makefile:80:
> > /home/chenhuacai/linux-official.git/tools/objtool/libsubcmd/libsubcmd-in.o]
> > Error 2
> > make[3]: *** [Makefile:82:
> > /home/chenhuacai/linux-official.git/tools/objtool/libsubcmd/libsubcmd.a]
> > Error 2
> > make[2]: *** [Makefile:73: objtool] Error 2
> > make[1]: *** [/home/chenhuacai/linux-official.git/Makefile:1355:
> > tools/objtool] Error 2
> > make: *** [Makefile:234: __sub-make] Error 2
>
> It seems that there is no stdbool.h in your cross compile environment.
>
> It works well with the following steps, you can try it.
/* snip */
> find /opt -name stdbool.h
> /opt/cross-tools/lib/gcc/loongarch64-unknown-linux-gnu/14.0.0/include/stdbool.h
> /opt/cross-tools/loongarch64-unknown-linux-gnu/include/c++/14.0.0/tr1/stdbool.h
The problem is HOSTCC cannot find stdbool.h, not (target) CC. So these
two files are not relevant.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2023-10-20 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 2:26 Tiezhu Yang
2023-10-20 2:26 ` [PATCH v3 1/8] objtool/LoongArch: Enable objtool to be built Tiezhu Yang
2023-10-20 2:26 ` [PATCH v3 2/8] objtool/LoongArch: Implement instruction decoder Tiezhu Yang
2023-10-20 2:26 ` [PATCH v3 3/8] objtool/x86: Separate arch-specific and generic parts Tiezhu Yang
2023-10-20 2:26 ` [PATCH v3 4/8] objtool/LoongArch: Enable orc to be built Tiezhu Yang
2023-10-21 8:08 ` Huacai Chen
2023-10-20 2:26 ` [PATCH v3 5/8] objtool: Check local label about sibling call Tiezhu Yang
2023-10-20 9:30 ` Peter Zijlstra
2023-10-20 10:56 ` Tiezhu Yang
2023-10-20 2:26 ` [PATCH v3 6/8] objtool: Check local label in add_dead_ends() Tiezhu Yang
2023-10-20 2:27 ` [PATCH v3 7/8] objtool: Check local label in read_unwind_hints() Tiezhu Yang
2023-10-20 2:27 ` [PATCH v3 8/8] LoongArch: Add ORC stack unwinder support Tiezhu Yang
2023-10-21 8:08 ` Huacai Chen
2023-10-20 8:51 ` [PATCH v3 0/8] Add objtool and orc support for LoongArch Huacai Chen
2023-10-20 10:28 ` Tiezhu Yang
2023-10-20 10:45 ` Xi Ruoyao [this message]
2023-10-20 10:54 ` Tiezhu Yang
2023-10-21 8:13 ` Huacai Chen
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=23a3ebe302f77db630edc52b23afb812f31f103e.camel@xry111.site \
--to=xry111@xry111.site \
--cc=chenhuacai@kernel.org \
--cc=jpoimboe@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
--cc=peterz@infradead.org \
--cc=yangtiezhu@loongson.cn \
/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
all inboxes | Powered by JetHome®