blocks|key|1503596|text|当您正在使用llvm/clang时，您(或包管理器)删除了以前存在的标准C库开发包(Debian上的埃格利布)，或者您可能一开始就没有安装它，因此您需要重新安装它，现在又回到gcc了。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1503597|您可以在Debian上这样做：|1503598|aptitude+show+libc-dev|code-block|syntax|javascript|1503599|Ubuntu：|1503600|apt-get+install+libc-dev|1503601|在Ubuntu上，如果您没有libc6，因为我在packages.ubuntu.com上找不到它，您可以直接安装libc6-dev。|1503602|或者在类似红帽的系统上：|1503603|百胜安装glibc-devel|blockquote|1503604|注意:虽然你在评论中得到了简短的答复，但这里有一个答案，如果有人遇到这个问题，并可能正在寻找答案，那么这里有一个记录在案的答案，但在评论中没有给出答案，或者评论对他们来说不够明确。|1503605|entityMap|0|LINK|mutability|MUTABLE|url|http://www.eglibc.org/home^0|1E|4|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@$A|16|B|17|1|18]]|C|$]]|$1|D|3|E|5|6|7|19|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|1A|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|1B|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|1C|8|@]|9|@]|C|$I|J]]|$1|O|3|P|5|6|7|1D|8|@]|9|@]|C|$]]|$1|Q|3|R|5|6|7|1E|8|@]|9|@]|C|$]]|$1|S|3|T|5|U|7|1F|8|@]|9|@]|C|$]]|$1|V|3|W|5|6|7|1G|8|@]|9|@]|C|$]]|$1|X|3|-4|5|6|7|1H|8|@]|9|@]|C|$]]]|Y|$Z|$5|10|11|12|C|$13|14]]]]

It seems that while you were playing with llvm/clang you(or the package manager) removed previously existing standard C library development package(<a href="http://www.eglibc.org/home">eglibc</a> on Debian) or maybe you didn't have it installed in the first place, thus you need to reinstall it, now that you reverted back to gcc.

You can do so like this on Debian:

<pre><code>aptitude show libc-dev
</code></pre>

Ubuntu:

<pre><code>apt-get install libc-dev
</code></pre>

On Ubuntu, if you don't have libc-dev, since I cannot find it on packages.ubuntu.com, you can try installing libc6-dev directly.

Or on Redhat like systems:

<blockquote>
 yum install glibc-devel
</blockquote>

NB: Although you were briefly answered in the comments, here is an answer just so there is one on record in case someone encounters this one and might be looking for an answer, but not in the comments or the comment is not explicit enough for them.

blocks|key|2700038|text|帮助我创建了一个象征性的链接：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2700039|sudo+ln+-s+/usr/lib/x86_64-linux-gnu+/usr/lib64|code-block|syntax|javascript|2700040|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

What helped me is to create a symbolic link:

<pre><code>sudo ln -s /usr/lib/x86_64-linux-gnu /usr/lib64
</code></pre>

blocks|key|1503676|text|如果您使用的是Debian的测试版本，称为“喘息”，那么您可能会被移动到multiarch而被咬伤。更多关于Debian的多重弓的信息，这里是：http://wiki.debian.org/Multiarch|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1503677|基本上，正在发生的是各种特定于体系结构的库正在从文件系统中的传统位置转移到新的特定于体系结构的地方。这就是为什么/usr/bin/ld感到困惑的原因。|style|CODE|1503678|您现在可以在/usr/lib64/和/usr/lib/i386-linux-gnu/中找到crt1.o，并且需要告诉您的工具链。下面是一些关于如何做到这一点的文档；http://wiki.debian.org/Multiarch/LibraryPathOverview|1503679|请注意，仅仅创建一个符号链接只会为您提供一个体系结构，而实际上您将禁用多重架构。虽然这可能是您想要的，但它可能不是最佳解决方案。|1503680|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.debian.org/Multiarch|1|http://wiki.debian.org/Multiarch/LibraryPathOverview^0|20|W|0|0|1K|B|0|6|B|I|O|2A|1G|1|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@$A|10|B|11|F|G]]|9|@]|C|$]]|$1|H|3|I|5|6|7|12|8|@$A|13|B|14|F|G]|$A|15|B|16|F|G]]|9|@$A|17|B|18|1|19]]|C|$]]|$1|J|3|K|5|6|7|1A|8|@]|9|@]|C|$]]|$1|L|3|-4|5|6|7|1B|8|@]|9|@]|C|$]]]|M|$N|$5|O|P|Q|C|$R|S]]|T|$5|O|P|Q|C|$R|U]]]]

If you're using Debian's Testing version, called 'wheezy', then you may have been bitten by the move to multiarch. More about Debian's multiarch here: <a href="http://wiki.debian.org/Multiarch" rel="noreferrer">http://wiki.debian.org/Multiarch</a>

Basically, what is happening is various architecture specific libraries are being moved from traditional places in the file system to new architecture specific places. This is why <code>/usr/bin/ld</code> is confused.

You will find crt1.o in both <code>/usr/lib64/</code> and <code>/usr/lib/i386-linux-gnu/</code> now and you'll need to tell your toolchain about that. Here is some documentation on how to do that; <a href="http://wiki.debian.org/Multiarch/LibraryPathOverview" rel="noreferrer">http://wiki.debian.org/Multiarch/LibraryPathOverview</a>

Note that merely creating a symlink will only give you one architecture and you'd be essentially disabling multiarch. While this may be what you want it might not be the optimal solution.

blocks|key|2700093|text|在阅读了耶利米发布的http://wiki.debian.org/Multiarch/LibraryPathOverview后，我发现gcc的国旗没有符号链接就能发挥作用：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2700094|gcc+-B/usr/lib/x86_64-linux-gnu+hello.c|code-block|syntax|javascript|2700095|因此，您可以将-B/usr/lib/x86_64-linux-gnu添加到生成文件中的CFLAGS变量中。|style|CODE|2700096|entityMap|0|LINK|mutability|MUTABLE|url|http://wiki.debian.org/Multiarch/LibraryPathOverview^0|A|1G|0|0|0|7|R|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@$A|V|B|W|1|X]]|C|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|Z|8|@$A|10|B|11|K|L]]|9|@]|C|$]]|$1|M|3|-4|5|6|7|12|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]]]

After reading the <a href="http://wiki.debian.org/Multiarch/LibraryPathOverview" rel="noreferrer">http://wiki.debian.org/Multiarch/LibraryPathOverview</a> that jeremiah posted, i found the gcc flag that works without the symlink:

<pre><code>gcc -B/usr/lib/x86_64-linux-gnu hello.c
</code></pre>

So, you can just add <code>-B/usr/lib/x86_64-linux-gnu</code> to the CFLAGS variable in your Makefile.

blocks|key|3058217|text|正如在缺少crti.o文件中所解释的，最好使用"gcc+-打印-搜索-脏“来找出所有的搜索路径。然后创建一个链接，如上面解释的"sudo+ln+-s“，指向crt1.o的位置。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3058218|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/91576/crti-o-file-missing^0|3|A|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

As explained in <a href="https://stackoverflow.com/questions/91576/crti-o-file-missing">crti.o file missing</a> , it's better to use "gcc -print-search-dirs" to find out all the search path. Then create a link as explain above "sudo ln -s" to point to the location of crt1.o

blocks|key|2700182|text|在CentOs+5.4上遇到了这个问题。注意到lib64包含crt*.o文件，但lib没有。通过yum安装了glibc，它安装了i386位，这解决了我的问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2700183|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Ran into this on CentOs 5.4. Noticed that lib64 contained the crt*.o files, but lib did not. Installed glibc-devel through yum which installed the i386 bits and this resolved my issue.

blocks|key|3058251|text|在我的例子中，crti.o错误是由Matlab的执行路径配置引起的。例如，如果之前没有设置执行目录的路径，则无法执行文件。要做到这一点:+File+>+setPath，添加您的目录并保存。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3058252|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case, the crti.o error was entailed by the execution path configuration from Matlab.
For instance, you cannot perform a file if you have not set the path of your execution directory earlier.
To do this: File > setPath, add your directory and save.

blocks|key|2700209|text|Debian+/+Ubuntu|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2700210|问题是，您可能只有gcc为您目前的架构，这是64位。您需要32位支持文件。为此，您需要安装它们。|2700211|sudo+apt+install+gcc-multilib|code-block|syntax|javascript|2700212|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

<h1>Debian / Ubuntu</h1>

The problem is you likely only have the gcc for your current architecture and that's 64bit. You need the 32bit support files. For that, you need to install them

<pre><code>sudo apt install gcc-multilib
</code></pre>

blocks|key|1503867|text|这是一个在launchpad中报告的错误，但是有一个解决办法：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1503868|运行此命令以查看这些文件的位置。|1503869|$+find+/usr/+-name+crti*
/usr/lib/x86_64-linux-gnu/crti.o|code-block|syntax|javascript|1503870|然后将此路径添加到LIBRARY_PATH变量|1503871|$+export+LIBRARY_PATH=/usr/lib/x86_64-linux-gnu:$LIBRARY_PATH|1503872|entityMap|0|LINK|mutability|MUTABLE|url|https://bugs.launchpad.net/ubuntu/%2Bsource/binutils/%2Bbug/738098^0|I|2|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]]|C|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|11|8|@]|9|@]|C|$I|J]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|C|$]]|$1|M|3|N|5|H|7|13|8|@]|9|@]|C|$I|J]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|P|$Q|$5|R|S|T|C|$U|V]]]]

This is a <a href="https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/738098" rel="noreferrer">BUG</a> reported in launchpad, but there is a workaround :

Run this to see where these files are located

<pre><code>$ find /usr/ -name crti*
/usr/lib/x86_64-linux-gnu/crti.o
</code></pre>

then add this path to LIBRARY_PATH variable

<pre><code>$ export LIBRARY_PATH=/usr/lib/x86_64-linux-gnu:$LIBRARY_PATH
</code></pre>

blocks|key|3058304|text|使用gcc+-B+lib_path_containing_crt?.o|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3058305|entityMap^0|2|X|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

use <code>gcc -B lib_path_containing_crt?.o</code>

blocks|key|1503891|text|甚至在交叉编译i+686-cm-linux-gcc时，我也遇到了同样的编译错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503892|下面的编译选项解决了我的问题|1503893|$+i686-cm-linux-gcc+a.c+--sysroot=/opt/toolchain/i686-cm-linux-gcc|code-block|syntax|javascript|1503894|注意：sysroot应该指向编译器目录，其中usr/可用|offset|length|style|BOLD|1503895|在我的例子中，工具链安装在/opt/+toolchain+/i+686-cm+gcc目录下，usr/include也可以在同一个目录中找到。|1503896|entityMap^0|0|0|0|3|7|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@$K|W|L|X|M|N]]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

Even I got the same compilation error when I was cross compiling i686-cm-linux-gcc.

The below compilation option solved my problem

<pre><code>$ i686-cm-linux-gcc a.c --sysroot=/opt/toolchain/i686-cm-linux-gcc
</code></pre>

Note: The sysroot should point to compiler directory where usr/include available

In my case the toolchain is installed at /opt/toolchain/i686-cm-linux-gcc directory and usr/include is also available in the same directory

blocks|key|3058368|text|我解决了以下问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3058369|1)尝试使用find+-name+ctr1.o定位ctr1.o和ctri.o文件|offset|length|style|CODE|3058370|我的电脑里有以下内容：$/usr/lib/i386-linux/gnu|3058371|2)将该路径添加到PATH+(也是LIBRARY_PATH)环境变量(以查看终端中的名称:键入env命令)：|3058372|$PATH=/usr/lib/i386-linux/gnu:$PATH
$export+PATH|code-block|syntax|javascript|3058373|entityMap^0|0|6|H|0|B|O|0|9|4|H|C|1B|3|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@$D|U|E|V|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|W|8|@$D|X|E|Y|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@$D|10|E|11|F|G]|$D|12|E|13|F|G]|$D|14|E|15|F|G]]|9|@]|A|$]]|$1|L|3|M|5|N|7|16|8|@]|9|@]|A|$O|P]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$]]

I solved it as follows:

1) try to locate ctr1.o and ctri.o files by using <code>find -name ctr1.o</code>

I got the following in my computer: <code>$/usr/lib/i386-linux/gnu</code>

2) Add that path to <code>PATH</code> (also <code>LIBRARY_PATH</code>) environment variable (in order to see which is the name: type <code>env</code> command in the Terminal):

<pre><code>$PATH=/usr/lib/i386-linux/gnu:$PATH
$export PATH
</code></pre>

blocks|key|1503967|text|要获得RHEL+7+64位编译gcc+4.8+32位程序，您需要做两件事.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1503968|确保所有32位gcc+4.8开发工具都已完全安装：
sudo安装glibc-devel.i+686+libgcc.i686+libstdc%2B%2B-devel.i+686+ncurses-devel.i+686|ordered-list-item|1503969|使用-m32标志编译程序
gcc+-m32+-o+pgm|1503970|从这里偷来的：如何在64位RHEL上编译32位应用程序？+-我只需要做第一步。|offset|length|1503971|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/23638271/how-to-compile-32-bit-apps-on-64-bit-rhel^0|0|0|0|7|L|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$]]|$1|E|3|F|5|D|7|U|8|@]|9|@]|A|$]]|$1|G|3|H|5|6|7|V|8|@]|9|@$I|W|J|X|1|Y]]|A|$]]|$1|K|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

To get RHEL 7 64-bit to compile gcc 4.8 32-bit programs, you'll need to do two things.

<ol>
<li>Make sure all the 32-bit gcc 4.8 development tools are completely installed:

<pre><code>sudo yum install glibc-devel.i686 libgcc.i686 libstdc++-devel.i686 ncurses-devel.i686
</code></pre></li>
<li>Compile programs using the -m32 flag

<pre><code>gcc pgm.c -m32 -o pgm
</code></pre></li>
</ol>

stolen from here : <a href="https://stackoverflow.com/questions/23638271/how-to-compile-32-bit-apps-on-64-bit-rhel">How to Compile 32-bit Apps on 64-bit RHEL?</a> - I only had to do step 1.

blocks|key|2700287|text|在我的例子中，Ubuntu+16.04完全没有crti.o：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2700288|$+find+/usr/+-name+crti*|code-block|syntax|javascript|2700289|因此，我安装了developer+libc6-dev包：|BOLD|2700290|sudo+apt-get+install+libc6-dev|2700291|entityMap^0|7|C|N|6|0|0|L|1|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|W|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|X|8|@$9|Y|A|Z|B|M]]|D|@]|E|$]]|$1|N|3|O|5|H|7|10|8|@]|D|@]|E|$I|J]]|$1|P|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|Q|$]]

In my case <code>Ubuntu 16.04</code> I have no <code>crti.o</code> at all:

<pre><code>$ find /usr/ -name crti*
</code></pre>

So I install developer libc6-dev package:

<pre><code>sudo apt-get install libc6-dev
</code></pre>

blocks|key|3058518|text|这对我和Ubuntu+16.04起了作用|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3058519|$+LIBRARY_PATH=/usr/lib/x86_64-linux-gnu
$+export+LIBRARY_PATH|code-block|syntax|javascript|3058520|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This worked for me with Ubuntu 16.04

<pre><code>$ LIBRARY_PATH=/usr/lib/x86_64-linux-gnu
$ export LIBRARY_PATH
</code></pre>

blocks|key|2700495|text|今天我也遇到了同样的问题，我通过安装推荐的软件包来解决这个问题:+libc6-dev-mipsel-cross+libc+6-dev-mipsel-cross，libc-dev-mipsel-cross。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2700496|这样做是有效的：|2700497|sudo+apt-get+install+libc6-dev-mipsel-cross|code-block|syntax|javascript|2700498|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had the same problem today, I solved it by installing recommended packages:
libc6-dev-mipsel-cross libc6-dev-mipsel-cross, libc-dev-mipsel-cross

This worked:

<pre><code>sudo apt-get install libc6-dev-mipsel-cross
</code></pre>

blocks|key|3058605|text|/配置-禁用-多库|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3058606|为它工作|3058607|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

./configure --disable-multilib

works for it

blocks|key|3058614|text|一个神奇的命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3058615|sudo+apt+install+build-essential|code-block|syntax|javascript|3058616|为我修复了一切，即使是在树莓派。|3058617|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

One magic command:
<pre><code>sudo apt install build-essential
</code></pre>
Fixed everything for me even on Raspberry Pi.

blocks|key|1504193|text|在阿尔卑斯Linux上，这意味着您的musl-dev|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1504194|apk+add+musl-dev|code-block|syntax|javascript|1504195|尽管就我而言，这些信息是：|1504196|/usr/lib/gcc/x86_64-alpine-linux-musl/11.2.1/../../../../x86_64-alpine-linux-musl/bin/ld:+cannot+find+Scrt1.o:+No+such+file+or+directory
/usr/lib/gcc/x86_64-alpine-linux-musl/11.2.1/../../../../x86_64-alpine-linux-musl/bin/ld:+cannot+find+crti.o:+No+such+file+or+directory
/usr/lib/gcc/x86_64-alpine-linux-musl/11.2.1/../../../../x86_64-alpine-linux-musl/bin/ld:+cannot+find+-lssp_nonshared:+No+such+file+or+directory
collect2:+error:+ld+returned+1+exit+status|1504197|这也是由于缺少musl-dev造成的。|1504198|entityMap|0|LINK|mutability|MUTABLE|url|https://pkgs.alpinelinux.org/contents?file=crt1.o&path=&name=&branch=v3.16&arch=x86_64^0|I|8|I|8|0|0|0|0|0|7|8|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|15|8|@]|D|@]|E|$]]|$1|M|3|N|5|H|7|16|8|@]|D|@]|E|$I|J]]|$1|O|3|P|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|Q|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

On Alpine Linux that would mean that you <a href="https://pkgs.alpinelinux.org/contents?file=crt1.o&amp;path=&amp;name=&amp;branch=v3.16&amp;arch=x86_64" rel="nofollow noreferrer">need <code>musl-dev</code></a>:
<pre><code>apk add musl-dev
</code></pre>
Although in my case the messages were:
<pre><code>/usr/lib/gcc/x86_64-alpine-linux-musl/11.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: cannot find Scrt1.o: No such file or directory
/usr/lib/gcc/x86_64-alpine-linux-musl/11.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: cannot find crti.o: No such file or directory
/usr/lib/gcc/x86_64-alpine-linux-musl/11.2.1/../../../../x86_64-alpine-linux-musl/bin/ld: cannot find -lssp_nonshared: No such file or directory
collect2: error: ld returned 1 exit status
</code></pre>
Which are also caused by missing <code>musl-dev</code>.

I have a virtual Debian system which I use to develop. Today I wanted to try llvm/clang. After installing clang I can't compile my old c-projects (with gcc).
This is the error:
<pre class="lang-none prettyprint-override"><code>/usr/bin/ld: cannot find crt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
collect2: ld returned 1 exit status
</code></pre>
I uninstalled clang and it still did not work. Does anyone have any idea how I can fix this?

How to fix linker error "cannot find crt1.o"?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我有一个虚拟Debian系统，我用它来开发。今天我想试一试。安装clang后，我无法编译我的旧c-项目(与gcc)。这是一个错误：/usr/bin/ld: cannot find crt1.o: No such file or directory/usr/bin/ld: cannot find crti.o: No s...

问如何修复链接器错误“找不到crt1.o"？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复链接器错误“找不到crt1.o"？EN