From: Alexandre Oliva <aoliva@redhat.com>
To: "Ripper" <ripper@s-series.org>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: help...
Date: Thu, 10 May 2001 17:50:00 -0000 [thread overview]
Message-ID: <orbsp0emjp.fsf@guarana.lsd.ic.unicamp.br> (raw)
In-Reply-To: <01a801c0d965$65cd1fc0$e67d8c86@collegis.com>
On May 10, 2001, "Ripper" <ripper@s-series.org> wrote:
> /usr/bin/ld: cannot open crt1.o: No such file or directory
> collect2: ld returned 1 exit status
> *** The command 'gcc -o conftest -g -O2 conftest.c' failed.
> *** You must set the environment variable CC to a working compiler.
> Any Ideas???
Looks like your compile is not working :-)
crt1.o is not part of the compiler, it's something it expects to find
as part of a development installation of the host operating system.
For instance, if it's a GNU/Linux system, this file will generally be
found in the glibc-devel package.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next prev parent reply other threads:[~2001-05-10 17:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 8:20 help Ripper
2001-05-10 17:50 ` Alexandre Oliva [this message]
2002-01-07 1:22 Help Aravind K Umesh
2002-01-07 9:09 ` Help Andrea 'Fyre Wyzard' Bocci
2002-01-10 1:37 Help Aravind K Umesh
2002-01-10 5:15 Help Sanjiv Kumar Gupta
2002-01-16 5:02 Help Aravind K Umesh
2002-01-30 1:41 help Aravind K Umesh
2002-02-01 1:02 Help Aravind K Umesh
2002-02-01 7:48 ` Help Andrea 'Fyre Wyzard' Bocci
[not found] <616BE6A276E3714788D2AC35C40CD18D394681@whale.softwire.co.uk>
2002-02-01 1:11 ` Help Rupert Wood
2002-04-16 4:50 Help zoushuo82
2004-08-30 12:46 Help help
2004-08-30 12:46 Help help
2005-03-28 14:42 Help umesh s
2006-12-22 9:37 help Manish Agarwal, Noida
2006-12-27 14:48 ` help manish manish
2006-12-29 10:04 ` help Dima Sorkin
2023-06-12 2:58 help Jerry Lin
2023-10-18 21:36 Help Peter Bergner
2024-04-26 18:25 Help Lusine Avetisyan
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=orbsp0emjp.fsf@guarana.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=ripper@s-series.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).