From: Brian Dessent <brian@dessent.net>
To: Jonas Karlsson <jonas@gobolinux.org>
Cc: GCC Help mailinglist <gcc-help@gcc.gnu.org>
Subject: Re: Cryptic error message from collect2
Date: Sat, 09 Aug 2008 20:26:00 -0000 [thread overview]
Message-ID: <489DFA83.52107B06@dessent.net> (raw)
In-Reply-To: <op.ufmjtgpwdefb7q@localhost.localdomain>
Jonas Karlsson wrote:
> collect2: open temporary output file: File exists
collect2 needs to create a number of temporary output files, and
apparently the name it has chosen for one of them already exists and
cannot be overwritten. It tries a number of locations -- you can look
through the code at libiberty/make_temp_file.c and so on, but it's
probably easier just to strace it to find out what's going on. If you
strace the gcc command however you won't see much as it doesn't do a lot
other than invoke subprocesses. So run the failing gcc command with
-### which will give you the exact invocation of collect2 which you can
then strace.
Brian
next prev parent reply other threads:[~2008-08-09 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 17:58 Jonas Karlsson
2008-08-09 20:26 ` Brian Dessent [this message]
2008-08-09 23:27 ` Jonas Karlsson
2008-08-10 1:58 ` Brian Dessent
2008-08-10 4:29 ` Jonas Karlsson
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=489DFA83.52107B06@dessent.net \
--to=brian@dessent.net \
--cc=gcc-help@gcc.gnu.org \
--cc=jonas@gobolinux.org \
/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).