Collect2 exe error ld returned 1 exit status ninja build stopped subcommand failed

The collect2: error: ld returned 1 exit status error message is easily fixed by removing an existing executable file inside your document. It is possible to remove the existing file that is running in the background by accessing the thread tools inside your system. The complete process is easy to do and only consists of a couple of steps.

If you want to become an expert at fixing this undefined reference in your program, keep reading this complete guide that contains all the details.

Why Is the collect2: Error: Ld Returned 1 Exit Status Happening?

This specific collect2: error: ld returned 1 exit status error message appears due to previous errors in your document, especially when working with C++. It represents one of the most common errors web developers face but it is also one of the easiest ones to fix. In other words, this error is there to indicate that the linking step in the process of creating faced certain problems.

This is going to create an undefined reference because the exit status is more than the value of zero. You can run multiple steps to create a search thread that is going to eliminate the problem. We are going to list and explain the various methods you can use to fix this error in your document. Continue reading the following section of this article to learn more about the debugging process.

How To Fix This Error Inside Your Program

The easiest and most common method of fixing this error requires you to completely delete the existing executable file that is running in the background of your program. However, as is the case with most other bugs, this solution might not work for everyone and every single time. Lucky for you, programming languages allow users to fix an error in multiple ways, in case any of the previous ones does not work.

This is called a process of debugging, where you are trying to completely remove an error you have encountered in your program. No matter how serious the error may be, the debugging process always starts with an inspection of the problem. After that, locate where the error is coming from and apply all the necessary changes to the code.

Let us now learn something more about the ways of debugging this error.

– Listing All the Possible Methods for Debugging This Error

In this part of the guide, we are going to list the possible methods for debugging and also briefly explain their function. Let us take a deep dive at the following list that shows the most common ways of fixing this error:

• Deleting the existing executable file inside your program: The file may have failed because it is locked in a different location, such as an antivirus.

• It is possible to try and rename that specific executable file in your program. Then, you are supposed to restructure the contents, and you are done. Renaming the file helps the program to create an additional executable file.

• In case none of this works, you should try restarting your computer and redo the first step. This solution shows that debugging does not always have to be complicated.

In theory, this is all it takes to completely remove this error from your syntax. However, it is always best to learn from examples. That is why in the following section of this article, we are going to show you example codes to easily fix this error.

– A Common Error in the Gem Native Extension

Many web developers face certain problems once working with extensions for their browsers. One such bug appears when you are trying to install a gem inside the native extension on your browser.

The reason why we are explaining the native extension is that the collect2 error usually appears during the process of installing a gem. To better understand what this means, you should take a look at the complete syntax.

Take a closer look at the following code that is going to initiate the collect2 error:

Building a proper native extension.  This might take a while…

ERROR:  Error installing json:
ERROR: Failed to generate gem native extension.
/home/foobar/.rvm/ruby-2.4.7/bin/ruby -r ./siteconf134617815-3312439-1i9lahdrj.rb extconf.rb
creating Makefile
make “DESTDIR=” clean
make “DESTDIR=”
compiling generator.c
linking shared-object json/ext/generator.so
/usr/bin/ld: cannot find -lgmp
collect2: error: ld returned 1 exit status
make: *** [generator.so] Error 1
make failed, exit code 2

Gem files will remain installed in /home/foobar/.rvm/gems/ruby-2.4.7/gems/json-1.8.3 for inspection.

Results logged to /home/foobar/.rvm/gems/ruby-2.4.7/extensions/x86_64-linux/2.2.0/json-1.8.3/gem_make.out

As you can see, this is the complete code for the collect2 error inside your program. There is certainly something you can do to the syntax to debug this error and make the program functional again. Indeed, we are going to change some things in the library and this is going to completely remove the error. Take a look at the following section of this article to learn more.

– Using the Debugging Library Syntax for the collect2 Error

As previously explained, you are supposed to change certain things inside the library to fix this error. For this, you are going to need the gmp function to locate the correct files and return the incorrect status. Open the code with the cache search gmp function and include all the additional tools inside.

The following syntax shows how to properly use the gmp function to fix this error:

$ apt-cache search gmp
libgmp-dev – Multiprecision arithmetic library developers tools
libgmp10 – Multiprecision arithmetic library
libgmp10-doc – Multiprecision arithmetic library example code
libgmp3-dev – Multiprecision arithmetic library developers tools
libgmpxx4ldbl – Multiprecision arithmetic library (C++ bindings)
[…]

Be aware that the syntax may be subject to changes. As this example shows, the annoying collect2 error does not have to be complicated to locate and fix. However, pay attention to the exact location of the gmp function because this may sometimes be the difference between a correctly and incorrectly executed code. Let us now learn other things about this common error in your program.

– Facing This Error in Dev C++

As previously explained, the collect2 error may usually appear once working with Dev C++. It refers to a specific reference to a name where the linker cannot define the way it looks based on the object files. This also applies to all the libraries that make up your document.

Lucky for you, fixing the error is done in the same manner as previously taught. All you have to do is to follow the steps discussed in this article and the problem is going to disappear. To learn more about this error, continue reading the FAQ section of this article.

FAQs

Here are the answers to some of your questions regarding this error.

– What Is collect2 Exe?

Collect2 represents a utility that web developers use to arrange certain initialization functions during the start time. In other words, it is used to link the program and the adequate functions, while creating a table inside a temporary file. Then, it is going to create a second link with the program but include a different file.

– What Does Error 1d Returned 1 Exit Status Mean?

The returned 1 status refers to an error in your document that is created due to previous errors. It is used as an indicator to point out that certain linking steps during the building process have bugs. To fix the error, you are supposed to refer to all the previous functions and locate the part of the program that is operating incorrectly.

– How To Combine Two Files in C++?

You can start combining two files in C++ by creating two separate source files on your server. The process of combining two C++ files is important because you can combine two different programs and functions. Since the collect2 error usually appears during this process, it is important to understand how the files are merged together.

There are several steps you are supposed to closely follow, as shown in the following list:

1. Create two separate C++ source files on your server.
2. Both files should be saved inside the same location on the server.
3. Open the Command Prompt tool and run the various commands from your files.
4. The tool is going to merge the two separate source files together and comply their functions.
5. Install the C++ Complier Program to run the newly-created file without any bugs.

This is all it takes to create a complex C++ file without facing any collect2 errors in your server. You can use this method for any two C++ files.

This section wraps everything important you were supposed to know about the collect2 error in your document. Let us now summarize the details.

Final Conclusion and Further Notes

This specific exit status error message is easily fixed by removing an existing executable file inside your document. Let us take a deep dive at the following list that contains all the important details from this article:

• The collect2 error is easily fixed by shutting down a program that is running in the background
• Web developers usually face this problem once working with Dev C++ and other files
• The Gem native extension usually displays this error alongside the complete syntax but it can be easily fixed
• It is important to know the meaning of collect2 to debug the error more efficiently
• It is possible to merge two C++ source files in five basic steps without caring about this error

Web developers are constantly struggling with the collect2 error inside their syntax and are unable to debug it. Lucky for you, now you know all the details to remove this error from your document without affecting the rest of the syntax.

I ran into the same problem and the following is my full log.

Building wheel torch-1.1.0a0+df05c7f
— Building version 1.1.0a0+df05c7f
[3/784] Building CXX object caffe2/CMakeFiles/caffe2.dir/ideep/operators/conv_op.cc.o
FAILED: caffe2/CMakeFiles/caffe2.dir/ideep/operators/conv_op.cc.o
/usr/bin/c++ -DCPUINFO_SUPPORTED_PLATFORM=1 -DHAVE_MALLOC_USABLE_SIZE=1 -DHAVE_MMAP=1 -DHAVE_SHM_OPEN=1 -DHAVE_SHM_UNLINK=1 -DNNP_CONVOLUTION_ONLY=0 -DNNP_INFERENCE_ONLY=0 -DONNX_NAMESPACE=onnx_torch -DTH_BLAS_MKL -DUSE_C11_ATOMICS=1 -D_FILE_OFFSET_BITS=64 -Dcaffe2_EXPORTS -I../aten/src -I. -I../ -I../third_party/protobuf/src -I../cmake/../third_party/benchmark/include -Icaffe2/contrib/aten -I../third_party/onnx -Ithird_party/onnx -I../third_party/foxi -Ithird_party/foxi -Icaffe2/aten/src/TH -I../aten/src/TH -Icaffe2/aten/src -Iaten/src -I../aten/../third_party/catch/single_include -I../aten/src/ATen/.. -Icaffe2/aten/src/ATen -I../caffe2/core/nomnigraph/include -I../third_party/miniz-2.0.8 -I../c10/.. -I../third_party/QNNPACK/include -I../third_party/pthreadpool/include -I../third_party/NNPACK/include -I../third_party/cpuinfo/include -I../third_party/fbgemm/include -I../third_party/fbgemm -I../third_party/FP16/include -isystem /home/yilingchen/miniconda3/envs/mrcnn-onnx/include -isystem ../third_party/ideep/include -isystem ../torch/include -isystem third_party/gloo -isystem ../cmake/../third_party/gloo -isystem ../cmake/../third_party/googletest/googlemock/include -isystem ../cmake/../third_party/googletest/googletest/include -isystem ../third_party/gemmlowp -isystem ../third_party/neon2sse -isystem ../third_party -isystem ../cmake/../third_party/eigen -isystem /home/yilingchen/miniconda3/envs/mrcnn-onnx/include/python3.7m -isystem /home/yilingchen/miniconda3/envs/mrcnn-onnx/lib/python3.7/site-packages/numpy/core/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent -isystem /usr/lib/x86_64-linux-gnu/openmpi/include/openmpi/opal/mca/event/libevent2022/libevent/include -isystem /usr/lib/x86_64-linux-gnu/openmpi/include -isystem include -fvisibility-inlines-hidden -fopenmp -D_FORCE_INLINES -D_MWAITXINTRIN_H_INCLUDED -D__STRICT_ANSI__ -DUSE_FBGEMM -O2 -fPIC -Wno-narrowing -Wall -Wextra -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -Wno-stringop-overflow -DHAVE_AVX_CPU_DEFINITION -DHAVE_AVX2_CPU_DEFINITION -O3 -fPIC -DCAFFE2_USE_GLOO -DHAVE_GCC_GET_CPUID -DUSE_AVX -DUSE_AVX2 -DTH_HAVE_THREAD -fvisibility=hidden -DCAFFE2_BUILD_MAIN_LIB -O2 -pthread -std=gnu++11 -MD -MT caffe2/CMakeFiles/caffe2.dir/ideep/operators/conv_op.cc.o -MF caffe2/CMakeFiles/caffe2.dir/ideep/operators/conv_op.cc.o.d -o caffe2/CMakeFiles/caffe2.dir/ideep/operators/conv_op.cc.o -c ../caffe2/ideep/operators/conv_op.cc
../caffe2/ideep/operators/conv_op.cc: In member function ‘virtual bool caffe2::IDEEPConvOp::RunOnDeviceWithOrderNCHW()’:
../caffe2/ideep/operators/conv_op.cc:75:27: error: no matching function for call to ‘ideep::convolution_forward::expected_weights_descriptor(ideep::param::dims, mkldnn::memory::data_type, std::vector&, ideep::param::dims, ideep::param::dims, std::vector&, int&, caffe2::IDEEPConvOp::ialgo&, caffe2::IDEEPConvOp::iprop&, mkldnn::memory::data_type, ideep::param::dims)’
X.get_dims());
^
In file included from ../third_party/ideep/include/ideep.hpp:44:0,
from ../caffe2/ideep/ideep_utils.h:6,
from ../caffe2/ideep/operators/conv_pool_base_op.h:6,
from ../caffe2/ideep/operators/conv_op.cc:1:
../third_party/ideep/include/ideep/computations.hpp:2173:29: note: candidate: static ideep::param::descriptor ideep::convolution_forward::expected_weights_descriptor(const dims&, ideep::param::data_type, const dims&, const dims&, const dims&, const dims&, int, ideep::algorithm, ideep::prop_kind, ideep::param::data_type)
static tensor::descriptor expected_weights_descriptor(
^~~~~~~~~~~~~~~~~~~~~~~~~~~
../third_party/ideep/include/ideep/computations.hpp:2173:29: note: candidate expects 10 arguments, 11 provided
../third_party/ideep/include/ideep/computations.hpp:593:22: note: candidate: ideep::param::descriptor ideep::primitive_group::expected_weights_descriptor() const
tensor::descriptor expected_weights_descriptor() const {
^~~~~~~~~~~~~~~~~~~~~~~~~~~
../third_party/ideep/include/ideep/computations.hpp:593:22: note: candidate expects 0 arguments, 11 provided
[36/784] Building CXX object caffe2/CMakeFiles/caffe2.dir/operators/cosh_op.cc.o
ninja: build stopped: subcommand failed.
Traceback (most recent call last):
File «setup.py», line 719, in
build_deps()
File «setup.py», line 285, in build_deps
build_dir=’build’)
File «/mnt/Data-1/Projects/faster-rcnn-onnx/pytorch/tools/build_pytorch_libs.py», line 278, in build_caffe2
check_call(ninja_cmd, cwd=build_dir, env=my_env)
File «/home/yilingchen/miniconda3/envs/onnxrt/lib/python3.7/subprocess.py», line 347, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘ninja’, ‘install’]’ returned non-zero exit status 1.

1

21.11.2019, 19:56. Показов 8595. Ответов 1

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102

#include "shootcalc.h"
#include "ui_shootcalc.h"
#include <QApplication>
#include <QPushButton>
#include <QWidget>
#include <QString>
#include <QLabel>
#include <QGroupBox>
#include <QDateTime>
 
ShootCalc::ShootCalc(QWidget *parent) :
    QDialog(parent),
    ui(new Ui::ShootCalc)
{
    ui->setupUi(this);
    connect(ui->ButtonForResult,SIGNAL(clicked()),this,SLOT(calc_shoot()));
}
 
ShootCalc::~ShootCalc()
{
    delete ui;
}
 
void ShootCalc::calc_shoot()
{
    unsigned int dmg_all(0), dmg_cal, num_shots, polojenie, n(0), m(0), num_cal, dmg_cal_all(0), d(0), j(0);
    int str, perc, pr_factor, armor, recoil_gun, dmg_gun, dmg_clear(0), proof, proof_recoil, dmg_max;
    bool fast_aim;
 
    if(ui->radio_vs_no->isChecked())
    {
        fast_aim = 0;
    }
    if(ui->radio_vs_yes->isChecked())
    {
        fast_aim = 1;
    }
 
    if(ui->radio_pol_2->isChecked())
    {
        polojenie = 2;
    }
    if(ui->radio_pol_4->isChecked())
    {
        polojenie = 4;
    }
    if(ui->radio_pol_8->isChecked())
    {
        polojenie = 8;
    }
 
    QString str_t = ui->value_str->text();
    str = str_t.toInt();
    QString perc_t = ui->value_perc->text();
    perc = perc_t.toInt();
    QString pr_factor_t = ui->value_factor->text();
    pr_factor = pr_factor_t.toInt();
    QString dmg_cal_t = ui->value_dmg_cal->text();
    dmg_cal = dmg_cal_t.toUInt();
    QString num_shots_t = ui->value_shots->text();
    num_shots = num_shots_t.toUInt();
    QString num_cal_t = ui->value_dmg_num->text();
    num_cal = num_cal_t.toUInt();
    QString armor_t = ui->value_armor->text();
    armor = armor_t.toInt();
    QString recoil_gun_t = ui->value_recoil->text();
    recoil_gun = recoil_gun_t.toInt();
    QString dmg_gun_t = ui->value_dmg_gun->text();
    dmg_gun = dmg_gun_t.toInt();
    QString dmg_max_t = ui->value_dmg_max->text();
    dmg_max = dmg_max_t.toInt();
 
    srand(time(0));
 
    if (fast_aim)
            pr_factor += 10;
    for (n = 1; n < num_shots; n++)
        {
            proof = 1 + rand() % 20 + perc - (recoil_gun - str);
            if (proof > pr_factor)
            {
                d++;
                for (m = 0; m < num_cal; m++)
                {
                    dmg_cal_all += (rand() % dmg_cal) + 1;
                }
                dmg_clear = dmg_cal_all + dmg_gun - armor;
                if (dmg_clear > dmg_max)
                    dmg_clear = dmg_max;
                if (dmg_clear > 0)
                {
                    dmg_all += dmg_clear;
                }
            }
            j++;
            proof_recoil = (j + polojenie) % polojenie;
            if (0 == proof_recoil)
                str--;
        }
    ui->lab_final_shots->setText(QString::number(d));
    ui->lab_final_dmg->setText(QString::number(dmg_all));
}

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33

#ifndef SHOOTCALC_H
#define SHOOTCALC_H
 
#include <QDialog>
 
namespace Ui {
class ShootCalc;
}
 
class ShootCalc : public QDialog
{
    Q_OBJECT
 
public:
    explicit ShootCalc(QWidget *parent = nullptr);
    ~ShootCalc();
 
private slots:
    void on_ButtonForResult_clicked();
 
    void on_radioButton_clicked();
 
    void on_radio_vs_no_clicked();
 
    void on_radio_vs_yes_clicked();
 
private:
    Ui::ShootCalc *ui;
    void calc_shoot();
    void shoot();
};
 
#endif // SHOOTCALC_H

__________________
Помощь в написании контрольных, курсовых и дипломных работ, диссертаций здесь

0

Hi everyone,

I am trying to migrate my firmware to the ESP-IDF platform. I have multiple problem occuring. When i use a get started example Hello_World, i can build and upload to my esp32 board. Once i monitor i get :
Rebooting…
ets Jun 8 2016 00:22:57

rst:0xc (SW_CPU_RESET),boot:0x32 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:4
load:0x3fff0034,len:6876
load:0x40078000,len:13072
load:0x40080400,len:3896
0x40080400: _init at ??:?

entry 0x40080688
I (29) boot: ESP-IDF v4.1-dirty 2nd stage bootloader
I (29) boot: compile time 10:36:22
I (29) boot: chip revision: 1
I (32) boot_comm: chip revision: 1, min. bootloader chip revision: 0
I (40) boot.esp32: SPI Speed : 40MHz
I (44) boot.esp32: SPI Mode : DIO
I (48) boot.esp32: SPI Flash Size : 16MB
I (53) boot: Enabling RNG early entropy source…
I (58) boot: Partition Table:
I (62) boot: ## Label Usage Type ST Offset Length
I (69) boot: 0 nvs WiFi data 01 02 00009000 00006000
I (77) boot: 1 phy_init RF data 01 01 0000f000 00001000
I (84) boot: 2 factory factory app 00 00 00010000 00100000
I (92) boot: End of partition table
I (96) boot_comm: chip revision: 1, min. application chip revision: 0
I (103) esp_image: segment 0: paddr=0x00010020 vaddr=0x3f400020 size=0x054a4 ( 21668) map
I (120) esp_image: segment 1: paddr=0x000154cc vaddr=0x3ffb0000 size=0x02150 ( 8528) load
I (124) esp_image: segment 2: paddr=0x00017624 vaddr=0x40080000 size=0x00404 ( 1028) load
0x40080000: _WindowOverflow4 at C:/repos/esp-idf/components/freertos/xtensa_vectors.S:1778

I (130) esp_image: segment 3: paddr=0x00017a30 vaddr=0x40080404 size=0x085e8 ( 34280) load
I (154) esp_image: segment 4: paddr=0x00020020 vaddr=0x400d0020 size=0x12dbc ( 77244) map
0x400d0020: _stext at ??:?

I (183) esp_image: segment 5: paddr=0x00032de4 vaddr=0x400889ec size=0x01100 ( 4352) load
0x400889ec: rtc_clk_wait_for_slow_cycle at C:/repos/esp-idf/components/soc/esp32/rtc_time.c:164

I (191) boot: Loaded app from partition at offset 0x10000
I (191) boot: Disabling RNG early entropy source…
I (193) cpu_start: Pro cpu up.
I (196) cpu_start: Application information:
I (201) cpu_start: Project name: hello-world
I (207) cpu_start: App version: v4.1-dirty
I (212) cpu_start: Compile time: Nov 3 2020 10:36:10
I (218) cpu_start: ELF file SHA256: c432a440140ad9cd…
I (224) cpu_start: ESP-IDF: v4.1-dirty
I (229) cpu_start: Starting app cpu, entry point is 0x4008102c
0x4008102c: call_start_cpu1 at C:/repos/esp-idf/components/esp32/cpu_start.c:271

I (221) cpu_start: App cpu up.
I (240) heap_init: Initializing. RAM available for dynamic allocation:
I (247) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM
I (253) heap_init: At 3FFB2958 len 0002D6A8 (181 KiB): DRAM
I (259) heap_init: At 3FFE0440 len 00003AE0 (14 KiB): D/IRAM
I (265) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM
I (272) heap_init: At 40089AEC len 00016514 (89 KiB): IRAM
I (278) cpu_start: Pro cpu start user code
I (296) spi_flash: detected chip: generic
E (297) spi_flash: failed to get chip size
assertion «flash_ret == ESP_OK» failed: file «C:/repos/esp-idf/components/esp32/cpu_start.c», line 431, function: start_cpu0_default
abort() was called at PC 0x400d5497 on core 0
0x400d5497: __assert_func at /builds/idf/crosstool-NG/.build/HOST-x86_64-w64-mingw32/xtensa-esp32-elf/src/newlib/newlib/libc/stdlib/assert.c:62 (discriminator

ELF file SHA256: c432a440140ad9cd

Backtrace: 0x40083dc1:0x3ffe3b80 0x40084151:0x3ffe3ba0 0x400d5497:0x3ffe3bc0 0x40080fb2:0x3ffe3bf0 0x40081237:0x3ffe3c40 0x40079212:0x3ffe3c80 |<-CORRUPTED
0x40083dc1: invoke_abort at C:/repos/esp-idf/components/esp32/panic.c:157

0x40084151: abort at C:/repos/esp-idf/components/esp32/panic.c:174

0x400d5497: __assert_func at /builds/idf/crosstool-NG/.build/HOST-x86_64-w64-mingw32/xtensa-esp32-elf/src/newlib/newlib/libc/stdlib/assert.c:62 (discriminator

0x40080fb2: start_cpu0_default at C:/repos/esp-idf/components/esp32/cpu_start.c:431 (discriminator 1)

0x40081237: call_start_cpu0 at C:/repos/esp-idf/components/esp32/cpu_start.c:259

If i start my own project via VScode/platformIO, i cant build it :

Executing action: all (aliases: build)
Running ninja in directory c:reposesp-idffirmwarebuild
Executing «ninja all»…
[1/6] cmd.exe /C «cd /D C:reposesp-idfFirmwarebuildesp-…***********************************************************»
Partition table binary generated. Contents:
*******************************************************************************
# Espressif ESP32 Partition Table
# Name, Type, SubType, Offset, Size, Flags
nvs,data,nvs,0x9000,24K,
phy_init,data,phy,0xf000,4K,
factory,app,factory,0x10000,1M,
*******************************************************************************
[2/6] Performing build step for ‘bootloader’
ninja: no work to do.
[3/4] Linking CXX executable Firmware.elf
FAILED: Firmware.elf
cmd.exe /C «cd . && C:reposesp-idftoolstoolsxtensa-esp32-elfesp-2020r2-8.2.0xtensa-esp32-elfbinxtensa-esp32-elf-g++.exe -mlongcalls -Wno-frame-address @CMakeFilesFirmware.elf.rsp -o Firmware.elf && cd .»
c:/repos/esp-idf/tools/tools/xtensa-esp32-elf/esp-2020r2-8.2.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.2.0/../../../../xtensa-esp32-elf/bin/ld.exe: esp-idf/esp32/libesp32.a(cpu_start.c.obj):(.literal.main_task+0x18): undefined reference to `app_main’
c:/repos/esp-idf/tools/tools/xtensa-esp32-elf/esp-2020r2-8.2.0/xtensa-esp32-elf/bin/../lib/gcc/xtensa-esp32-elf/8.2.0/../../../../xtensa-esp32-elf/bin/ld.exe: esp-idf/esp32/libesp32.a(cpu_start.c.obj): in function `main_task’:
C:/repos/esp-idf/components/esp32/cpu_start.c:551: undefined reference to `app_main’
collect2.exe: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
ninja failed with exit code 1

I’ve found nothing that works for me elsewhere

C компиляция: collect2: ошибка: ld возвращен 1 статус выхода

Я попытался найти эту ошибку онлайн, но все сообщения для С++.

test1.o: В функции ReadDictionary’: /home/johnny/Desktop/haggai/test1.c:13: undefined reference to CreateDictionary ‘ collect2: error: ld возвращен 1 статус выхода make: *** [test1] Ошибка 1

супер простой код и не может понять, что проблема

теперь это заголовок dict.h

и если вы хотите проверить hash.h

Может быть, будет легче, если я дам вам файлы здесь?

В любом случае, я буду рад за советы о том, как понять проблему.

ОТВЕТЫ

Ответ 1

Ваша проблема — это опечатка в функции CreateD e ctionary(). Вы должны изменить ее на CreateD i ctionary(). collect2: error: ld return 1 статус выхода — та же проблема как на C, так и на С++, обычно это означает, что у вас есть неразрешенные символы. В вашем случае это опечатка, о которой я упоминал ранее.

Ответ 2

Ответ 3

У меня возникла эта проблема, и я попытался решить многие ее проблемы. Наконец, оказалось, что make clean и make снова решили. Причина в следующем: Я получил исходный код вместе с объектными файлами, скомпилированными ранее со старой версией gcc. Когда моя новая версия gcc хочет связать эти старые файлы объектов, она не может решить какую-либо функцию там. Случается со мной несколько раз, что дистрибуторы исходного кода не очищаются перед упаковкой, поэтому make clean сохранил день.

Ответ 4

иногда эта ошибка возникла, потому что не удалось скомпилировать ни в какой другой сборке. Лучший способ попробовать — сделать чистую и снова сделать весь код.

Ответ 5

При компиляции вашей программы вам необходимо включить dict.c, например:

gcc -o test1 test1.c dict.c

Кроме того, у вас есть опечатка в определении dict.c CreateDictionary , она говорит CreateDectionary ( e вместо i )

Ответ 6

обычно эта проблема возникала, когда мы вызывали функцию, которая не была определена в программном файле, поэтому, чтобы решить эту проблему, проверьте, вызывали ли вы такую ​​функцию, которая не была определена в файле программы.

Ответ 7

Если вы используете Dev C++, то ваш .exe или означает, что ваша программа уже запущена, и вы пытаетесь запустить ее снова.

Источник

Gcc collect2 exe error ld returned 1 exit status

mironyuk

Marlin 2.0.8, COREXY, 3D TOUCH
все работало нормально. Не знаю, что сделал ,но ошибка при компиляции вылезает не зависимо от
-компа
-смены прошивки вплоть до чистой или родной заводской
-перезагрузки компа
-удаления полного VC и установки заново

В общем, мумукаюсь уже два дня, начинаю беситься.
Наверняка кто-то тоже сталкивался с такой проблемой, отзовитесь.
Прошивку прицепил.

Вложения

Эдуард Анисимов

mironyuk

03-05.7z

Эдуард Анисимов

mironyuk

я не программист, от слова Далеко, извините. Что я должен сделать с этим ромом? ну, и с предупреждениями?
Спасибо.

предупреждения и раньше были (это желтым, я понимаю), может не столько, как сейчас, но все работало. Вот начал автоуровень приделывать и кое что подкорректировал в прошиве, может и не туда ткнул где-то.

попробую вот так

Эдуард Анисимов

mironyuk

если под железкой понимается комп, то я делал на другом компе и тоже самое происходит

достал старую прошивку, предупреждений нет, переполнения ром тоже нет, но появилось новое чего то там в файле .ld

Эдуард Анисимов

А обновления PlatformIO перед этим не было?
Я столкнулся с тем, что писал на старом, на компе, где нет интернета. И всё работало.
Дома обновился и всё перестало работать.

А почему не пишете под CubeIDE?

А судя по логу, ему скрипт для F103VC не нравится.

mironyuk

я сносил два раза VC полностью и устанавливал, но вроде не писал мне VC что обновляет Платформио.
А почему не пишете под CubeIDE?\ я даже не знаю, что это, я далек от понимания языка С и пр. Просто обновил плату на 32 бит, за ней потянулся Марлин 2.0, ну и далее вопрос чем компилить, увидел VC и вперед.
А судя по логу, ему скрипт для F103VC не нравится. \ ну это «вдруг» сейчас ему не нравится, а всегда нравился, вроде.

ааааа, со старой прошивой сам баран — перенес ее в новую папку и обозвал кирилицей папку АРХИВ. блин, сам на эти грабли уже наступал. Так вот, когда АРХИВ переименовал в STORAGE, то все скомпилировалось!! Таакс, значит дело не в VC. Надо, наверное, сравнить построчно обе прошивы и найти разницу, в этой разнице и кроется ошибка или опять же русская буква закралась в команду.

Эдуард Анисимов

Вот про эту возможность я всегда забываю. Так как никогда ни пользователя, ни каталог для проекта не создаю кириллицей.
И в логах ошибки ничего не было. Поэтому и забыл.

А сравнивать построчно удобно TotalCommander. Файловый менеджер с кучей фич в максимальной комплектации.

Источник

The STM32 Systems Resource

SW4STM32 and SW4Linux fully supports the STM32MP1 asymmetric multicore Cortex/A7+M4 MPUs

With System Workbench for Linux , Embedded Linux on the STM32MP1 family of MPUs from ST was never as simple to build and maintain, even for newcomers in the Linux world. And, if you install System Workbench for Linux in System Workbench for STM32 you can seamlessly develop and debug asymmetric applications running partly on Linux, partly on the Cortex-M4. You can get more information from the ac6-tools website and download (registration required) various documents highlighting: Video: Simultaneous debug of Linux and bare-metal applications. Video: Motor control by gestures (image processing on Cortex-A7/Linux, real-time on bare metal Cortex-M4). White paper: Asymmetric Multi-Programming with System Workbench for Linux . White paper: Creating an STM32MP1 Linux platform with System Workbench for Linux .

System Workbench for STM32

collect2.exe: error: ld returned 1 exit status

I met this issue building SMARTMIC project for Bluecoin in Eclipse Oxygen with SW4STM32 plugin. I was able to build this project in the same configuration and environment, but after a few days this issue appeared. Installed Eclipse Photon and SW4STM32 plugin, issue disappeared, but after a few days reappeared again. There is the same issue with other of the shelf ST projects as well (eg STSW-SPIN3201). Could anyone help please?
Also, there is a warning:

1. warning “Compiler generates FPU instructions for a device without an FPU (check __FPU_PRESENT)”

This wasn’t there before. It is strange, because the target MCU has FPU.

There is a build log.

make all
Building file: D:/workspace/STM32CubeFunctionPack_SMARTMIC1_V1.1.1/Middlewares/ST/STM32_AcousticDB_Library/Lib/Acoustic_DB100.c
Invoking: MCU GCC Compiler
D:workspaceSTM32CubeFunctionPack_SMARTMIC1_V1.1.1ProjectsMultiApplicationsFP-AUD-SMARTMIC1SW4STM32STM32F446ME-BlueCoinDebug
arm-none-eabi-gcc -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -DARM_MATH_CM4 -DUSE_HAL_DRIVER -DSTM32_BLUECOIN -DSTM32F446xx -DUSE_COMPOSITE_VCP_AUDIO

Источник

Let me show you CMakeError.log:

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Compilation of the CXX compiler identification source «CMakeCXXCompilerId.cpp» did not produce an executable in «C:/Qt/CMakeFiles/3.18.4/CompilerIdCXX».

Checking whether the CXX compiler is IAR using «» did not match «IAR .+ Compiler»:

** Visual Studio 2019 Developer Command Prompt v16.8.4
** Copyright (c) 2020 Microsoft Corporation

[vcvarsall.bat] Environment initialized for: ‘x64’
Checking whether the CXX compiler is IAR using «» did not match «IAR .+ Compiler»:

** Visual Studio 2019 Developer Command Prompt v16.8.4
** Copyright (c) 2020 Microsoft Corporation

[vcvarsall.bat] Environment initialized for: ‘x64’
Checking whether the ASM compiler is GNU using «—version» did not match «(GNU assembler)|(GCC)|(Free Software Foundation)»:
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

cl : Command line warning D9002 : ignoring unknown option ‘—version’
cl : Command line error D8003 : missing source filename
Checking whether the ASM compiler is Clang using «—version» did not match «(clang version)»:
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

cl : Command line warning D9002 : ignoring unknown option ‘—version’
cl : Command line error D8003 : missing source filename
Checking whether the ASM compiler is AppleClang using «—version» did not match «(Apple LLVM version)»:
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

cl : Command line warning D9002 : ignoring unknown option ‘—version’
cl : Command line error D8003 : missing source filename
Checking whether the ASM compiler is ARMClang using «—version» did not match «armclang»:
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

cl : Command line warning D9002 : ignoring unknown option ‘—version’
cl : Command line error D8003 : missing source filename
Checking whether the ASM compiler is HP using «-V» did not match «HP C»:
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

cl : Command line error D8004 : ‘/V’ requires an argument
Checking whether the ASM compiler is Intel using «—version» did not match «(ICC)»:
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

cl : Command line warning D9002 : ignoring unknown option ‘—version’
cl : Command line error D8003 : missing source filename
Checking whether the ASM compiler is SunPro using «-V» did not match «Sun C»:
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

cl : Command line error D8004 : ‘/V’ requires an argument
Checking whether the ASM compiler is XL using «-qversion» did not match «XL C»:
Microsoft (R) C/C++ Optimizing Compiler Version 19.28.29336 for x64
Copyright (C) Microsoft Corporation. All rights reserved.

cl : Command line warning D9002 : ignoring unknown option ‘-qversion’
cl : Command line error D8003 : missing source filename
Detecting CXX compiler ABI info failed to compile with the following output:
Change Dir: C:/Qt/CMakeFiles/CMakeTmp

Run Build Command(s):C:/ninja-win/ninja.exe cmTC_ea43b && [1/2] Building CXX object CMakeFilescmTC_ea43b.dirCMakeCXXCompilerABI.cpp.obj

FAILED: CMakeFiles/cmTC_ea43b.dir/CMakeCXXCompilerABI.cpp.obj

«C:PROGRA~2Microsoft Visual Studio2019COMMUN~1VCAUXILI~1Buildvcvars64.bat» -o CMakeFilescmTC_ea43b.dirCMakeCXXCompilerABI.cpp.obj -c «C:Program FilesCMakesharecmake-3.18ModulesCMakeCXXCompilerABI.cpp»

[ERROR:vcvarsall.bat] Invalid argument found : -o

[ERROR:vcvarsall.bat] Invalid argument found : CMakeFilescmTC_ea43b.dirCMakeCXXCompilerABI.cpp.obj

[ERROR:vcvarsall.bat] Invalid argument found : -c

La syntaxe de la commande n’est pas correcte.

ninja: build stopped: subcommand failed.