blocks|key|304255|text|这是在创建交叉编译器时发生的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|304256|它指的不是顶级config.log，而是$LFS_TGT/libgcc/config.log。|offset|length|style|CODE|304257|对我来说，在那里，它是这样说的：|304258|configure:3566:+/foo/gcc/build/./gcc/xgcc+-B/foo/gcc/build/./gcc/+-B/opt/gcc-cross-11.1.0/aarch64-none-elf/bin/+-B/opt/gcc-cross-11.1.0/aarch64-none-elf/lib/+-isystem+/opt/gcc-cross-11.1.0/aarch64-none-elf/include+-isystem+/opt/gcc-cross-11.1.0/aarch64-none-elf/sys-include++++-o+conftest+-g+-O2+++conftest.c++>&5
conftest.c:9:10:+fatal+error:+stdio.h:+No+such+file+or+directory
++++9+%7C+#include+<stdio.h>
++++++%7C++++++++++%5E~~~~~~~~
compilation+terminated.
configure:3569:+$?+=+1
configure:3782:+checking+for+suffix+of+object+files
configure:3804:+/foo/gcc/build/./gcc/xgcc+-B/foo/gcc/build/./gcc/+-B/opt/gcc-cross-11.1.0/aarch64-none-elf/bin/+-B/opt/gcc-cross-11.1.0/aarch64-none-elf/lib/+-isystem+/opt/gcc-cross-11.1.0/aarch64-none-elf/include+-isystem+/opt/gcc-cross-11.1.0/aarch64-none-elf/sys-include++++-c+-g+-O2++conftest.c+>&5
/foo/gcc/build/./gcc/as:+line+106:+exec:+-E:+invalid+option
exec:+usage:+exec+[-cl]+[-a+name]+[command+[arguments+...]]+[redirection+...]
configure:3808:+$?+=+1
configure:+failed+program+was:
%7C+/*+confdefs.h+*/
%7C+#define+PACKAGE_NAME+"GNU+C+Runtime+Library"
%7C+#define+PACKAGE_TARNAME+"libgcc"
%7C+#define+PACKAGE_VERSION+"1.0"
%7C+#define+PACKAGE_STRING+"GNU+C+Runtime+Library+1.0"
%7C+#define+PACKAGE_BUGREPORT+""
%7C+#define+PACKAGE_URL+"http://www.gnu.org/software/libgcc/"
%7C+/*+end+confdefs.h.++*/
%7C+
%7C+int
%7C+main+()
%7C+{
%7C+
%7C+++;
%7C+++return+0;
%7C+}
configure:3822:+error:+in+`/foo/gcc/build/aarch64-none-elf/libgcc':
configure:3824:+error:+cannot+compute+suffix+of+object+files:+cannot+compile
See+`config.log'+for+more+details|code-block|syntax|javascript|304259|您的日志文件类似吗？|304260|我相信，gcc的编译/安装过程将包含各种includes，通过fixincludes运行它们来修复问题并为目标arch量身定制它们。所需的文件不存在。|304261|关于Prerequisites页面，我相信这一部分是相关的(重点是我的)：|304262|C+standard+library+and+headers

In+order+to+build+GCC,+the+C+standard+library+and+headers+must+be+present+for+all
target+variants+for+which+target+libraries+will+be+built+(and+not+only+the+variant
of+the+host+C%2B%2B+compiler).

This+affects+the+popular+‘x86_64-pc-linux-gnu’+platform+(among+other+multilib
targets),+for+which+64-bit+(‘x86_64’)+and+32-bit+(‘i386’)+libc+headers+are+usually
packaged+separately.+If+you+do+a+build+of+a+native+compiler+on+‘x86_64-pc-linux-gnu’,
make+sure+you+either+have+the+32-bit+libc+developer+package+properly+installed+(the
exact+name+of+the+package+depends+on+your+distro)+or+you+must+build+GCC+as+a+64-bit
only+compiler+by+configuring+with+the+option+--disable-multilib.+Otherwise,+you+may
encounter+an+error+such+as+‘fatal+error:+gnu/stubs-32.h:+No+such+file’|304263|我认为解决方案是获取目标平台的头文件。|304264|entityMap|0|LINK|mutability|MUTABLE|url|https://gcc.gnu.org/install/prerequisites.html^0|0|7|A|K|Q|0|0|0|0|V|B|0|2|D|0|0|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@$D|18|E|19|F|G]|$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|1D|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|1E|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|1F|8|@$D|1G|E|1H|F|G]]|9|@]|A|$]]|$1|S|3|T|5|6|7|1I|8|@]|9|@$D|1J|E|1K|1|1L]]|A|$]]|$1|U|3|V|5|L|7|1M|8|@]|9|@]|A|$M|N]]|$1|W|3|X|5|6|7|1N|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

This happens while creating a cross-compiler.
It's not referring to the top-level <code>config.log</code>, but <code>$LFS_TGT/libgcc/config.log</code>.
For me, in there, it says:
<pre><code>configure:3566: /foo/gcc/build/./gcc/xgcc -B/foo/gcc/build/./gcc/ -B/opt/gcc-cross-11.1.0/aarch64-none-elf/bin/ -B/opt/gcc-cross-11.1.0/aarch64-none-elf/lib/ -isystem /opt/gcc-cross-11.1.0/aarch64-none-elf/include -isystem /opt/gcc-cross-11.1.0/aarch64-none-elf/sys-include -o conftest -g -O2 conftest.c &gt;&amp;5
conftest.c:9:10: fatal error: stdio.h: No such file or directory
 9 | #include &lt;stdio.h&gt;
 | ^~~~~~~~~
compilation terminated.
configure:3569: $? = 1
configure:3782: checking for suffix of object files
configure:3804: /foo/gcc/build/./gcc/xgcc -B/foo/gcc/build/./gcc/ -B/opt/gcc-cross-11.1.0/aarch64-none-elf/bin/ -B/opt/gcc-cross-11.1.0/aarch64-none-elf/lib/ -isystem /opt/gcc-cross-11.1.0/aarch64-none-elf/include -isystem /opt/gcc-cross-11.1.0/aarch64-none-elf/sys-include -c -g -O2 conftest.c &gt;&amp;5
/foo/gcc/build/./gcc/as: line 106: exec: -E: invalid option
exec: usage: exec [-cl] [-a name] [command [arguments ...]] [redirection ...]
configure:3808: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME &quot;GNU C Runtime Library&quot;
| #define PACKAGE_TARNAME &quot;libgcc&quot;
| #define PACKAGE_VERSION &quot;1.0&quot;
| #define PACKAGE_STRING &quot;GNU C Runtime Library 1.0&quot;
| #define PACKAGE_BUGREPORT &quot;&quot;
| #define PACKAGE_URL &quot;http://www.gnu.org/software/libgcc/&quot;
| /* end confdefs.h. */
| 
| int
| main ()
| {
| 
| ;
| return 0;
| }
configure:3822: error: in `/foo/gcc/build/aarch64-none-elf/libgcc':
configure:3824: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details
</code></pre>
Was your logfile similar?
It's my belief that the gcc compilation/installation process will take the various includes, run them through <code>fixincludes</code> to fix problems and tailor them to the target arch. The expected file is not present.
Referring to the <a href="https://gcc.gnu.org/install/prerequisites.html" rel="nofollow noreferrer">Prerequisites</a> page, I believe this section is relevant (emphasis mine):
<pre><code>C standard library and headers

In order to build GCC, the C standard library and headers must be present for all
target variants for which target libraries will be built (and not only the variant
of the host C++ compiler).

This affects the popular ‘x86_64-pc-linux-gnu’ platform (among other multilib
targets), for which 64-bit (‘x86_64’) and 32-bit (‘i386’) libc headers are usually
packaged separately. If you do a build of a native compiler on ‘x86_64-pc-linux-gnu’,
make sure you either have the 32-bit libc developer package properly installed (the
exact name of the package depends on your distro) or you must build GCC as a 64-bit
only compiler by configuring with the option --disable-multilib. Otherwise, you may
encounter an error such as ‘fatal error: gnu/stubs-32.h: No such file’
</code></pre>
I believe that the solution is to obtain headers for the TARGET platform.

I'm actually reading the LFS book (version 7.1) and I'm blocked at page 53. Trying to compile gcc, I tried the following command:

<pre><code>./configure --target=$LFS_TGT --prefix=$LFS/build/gcc-build --disable-nls\
--disable-shared --disable-multilib --disable-decimal-float --disable-threads\
--disable-libmudflap --disable-libssp --disable-libgomp --disable-libquadmath\
--disable-target-libiberty --disable-target-zlib\
--enable-languages=c\
--without-ppl --without-cloog\
--with-mpfr-include=$LFS/source/mpfr/src
--with-mpfr-lib=$LFS/source/mpfr/src/.libs\
--with-gmp-include=/mnt/LFS/source/gmp\
--with-gmp-lib=/mnt/LFS/source/gmp/.libs\
--with-mpc-include=/mnt/LFS/source/mpc/src\
--with-mpc-lib=/mnt/LFS/source/mpc/src/.libs
</code></pre>

to run the configure script of gcc (of course I already compiled mpfr, mpc and gmp as well).
But once I launch:

<pre><code>make -j4
</code></pre>

I get the following error:

<pre><code>checking for suffix of object files... configure: error: in `/mnt/LFS/source/gcc-4.6.2/x86_64-lfs-linux-gnu/libgcc':
configure: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
make[1]: *** [configure-target-libgcc] Error 1
</code></pre>

I tried to google for it and tried the solutions I found but nothing worked. Does anyone know why I get this error?

Gcc compilation "cannot compute suffix of object files: cannot compile"

日志文件

编译器

实际上，我正在阅读LFS书籍(7.1版)，我在第53页被阻止了。为了编译gcc，我尝试了以下命令：./configure --target=$LFS_TGT --prefix=$LFS/build/gcc-build --disable-nls\--disable-shared --disable-multilib -...

问Gcc编译“无法计算目标文件的后缀:无法编译”
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gcc编译“无法计算目标文件的后缀:无法编译”EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Gcc编译“无法计算目标文件的后缀:无法编译”
EN