From: Jim Wilson <jimw@sifive.com>
To: Rajat Dahiya <rajatdahiyajaaat16@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re:
Date: Thu, 4 Jun 2020 15:04:28 -0700 [thread overview]
Message-ID: <CAFyWVabHDQA86Dai_pwM+u-p+rL8t-hDU=2+swSsO2uBOvz5xQ@mail.gmail.com> (raw)
In-Reply-To: <CA+XWQNrLEC0SoW9O6Kv+LyBMNJKy=SKOdGrJz5CK36vp+28QyQ@mail.gmail.com>
On Thu, Jun 4, 2020 at 10:07 AM Rajat Dahiya via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
> I have got
> collect2.exe error ld returned 1 exit status
> This error during any c/c++ code in vscode/sublime text 3
> Please send me solutions.
Generally, the first error message is the most important one, and the
last error message is the least important one. You included the last
error message which has no useful info for us. Also, in general, we
need to be able to reproduce a problem in order to understand it, and
you haven't provided any info on what exactly you did to generate the
error.
Jim
next prev parent reply other threads:[~2020-06-04 22:04 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 17:07 Rajat Dahiya
2020-06-04 22:04 ` Jim Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-26 6:15 Jerress Mejado
2024-03-26 7:37 ` Jonathan Wakely
2024-03-01 22:26 Sunandha Sunandha
2024-03-02 8:37 ` Jonathan Wakely
2023-09-03 9:27 Adminn
2023-09-02 6:37 Nathan
2023-09-03 8:15 ` Jonathan Wakely
2023-09-03 10:13 ` Re: Jonathan Wakely
2023-07-17 2:46 Budi
2023-07-17 3:40 ` Xi Ruoyao
2023-07-17 7:23 ` Re: Jonathan Wakely
2023-04-04 3:13 Sanniddha Chakrabarti
2023-04-04 8:59 ` Jonathan Wakely
2023-04-04 9:13 ` Re: Sanniddha Chakrabarti
2023-01-13 2:32 Re: father.dominic
2022-12-04 8:48 hongjie wu
2022-12-04 13:07 ` Jonathan Wakely
[not found] <7879ed669a3b4fedb95df2ba8608dbc4@auswideservices.net>
2022-10-13 0:50 ` Development - AuswideServices
2022-01-10 12:03 Manuel Lauss
2022-01-10 12:10 ` Jonathan Wakely
2022-01-10 12:12 ` Re: Manuel Lauss
2022-01-10 12:15 ` Re: Jonathan Wakely
2021-10-05 7:38 Jyothi Pattamshetty
2021-10-05 7:57 ` Jonathan Wakely
2020-10-05 18:16 Jennie Pabuaya
2020-10-05 18:41 ` Dan Kegel
[not found] <trinity-20d6279f-4e28-4ae0-9933-b45cc20447c8-1385584973099@3capp-gmx-bs06>
2013-11-28 10:30 ` Re: Andrew Haley
[not found] <CAM=QvqcYCATx8uWeMPJrh=Zgt6OMFYwy04n_w4uDe9K-a7oHGw@mail.gmail.com>
2012-12-04 7:14 ` Fwd: dhinesh someone
2012-12-04 7:40 ` Ian Lance Taylor
2011-12-07 1:26 Re: Daniel Rangel
2011-12-03 17:12 Re: Daniel Rangel
2011-11-14 0:59 Re: none none
2011-11-09 17:43 Re: none none
2011-10-01 18:07 Re: none none
2011-06-07 0:37 Re: none none
2006-12-07 19:12 Re: ravandale
2006-02-22 5:21 Re: Cora T. Baez
2004-12-11 3:38 Re: Валентина Брониславовна
2004-12-11 3:38 Re: Валентина Брониславовна
2004-11-29 4:39 Re: Лора Устиновна
2004-11-29 4:39 Re: Лора Устиновна
[not found] <20040913111103.77851.qmail@web52901.mail.yahoo.com>
2004-09-13 11:20 ` Re: Ron Michael Khu
2004-09-14 3:43 ` Re: zippo
2004-09-14 15:25 ` Re: Ron Michael Khu
[not found] <200304071521.h37FLUg6026247@smtp-relay-2.adobe.com>
2003-04-07 15:41 ` Re: John Love-Jensen
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='CAFyWVabHDQA86Dai_pwM+u-p+rL8t-hDU=2+swSsO2uBOvz5xQ@mail.gmail.com' \
--to=jimw@sifive.com \
--cc=gcc-help@gcc.gnu.org \
--cc=rajatdahiyajaaat16@gmail.com \
/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).