From: Adriano Holanda <adriano@papaleguas.fmrp.usp.br>
To: gcc-help@gcc.gnu.org
Subject: problems with make
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.96.991223110813.579C-100000@papaleguas.fmrp.usp.br> (raw)
Message-ID: <19991231222400.kLhpQVPIyQbwKGbcygzsR-Ilow-tRx8OHYWI3fI2U9c@z> (raw)
My system is: Solaris 7 (SPARC)
I have installed binaries gcc in my machine, but some tasks it doesn't
make, like install some perl modules e some programs. So i decided install
the source gcc-2.95.2 and when I run make, this happened:
//final of the make output
/usr/local/gcc-2.95.2/libiberty/vfork.c -o pic/vfork.o
gcc -c -DHAVE_CONFIG_H -g -O2 -I.
-I/usr/local/gcc-2.95.2/libiberty/../include
/usr/local/gcc-2.95.2/libiberty/vfork.c
rm -f libiberty.a
ar rc libiberty.a \
argv.o choose-temp.o concat.o cplus-dem.o fdmatch.o fnmatch.o getopt.o
getopt1.o getruntime.o hex.o floatformat.o objalloc.o obstack.o pexecute.o
spaces.o splay-tree.o strerror.o strsignal.o xatexit.o xexit.o xmalloc.o
xstrdup.o xstrerror.o asprintf.o mkstemps.o setenv.o sigsetmask.o
vasprintf.o vfork.o
make[1]: ar: Command not found
make[1]: *** [libiberty.a] Error 127
make[1]: Leaving directory `/usr/local/gcc-2.95.2/obj/libiberty'
make: *** [all-libiberty] Error 2
How can I install gcc 2.95.2 source without this error?
Thanks,
Adriano.
next reply other threads:[~1999-12-31 22:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-23 5:27 Adriano Holanda [this message]
1999-12-31 22:24 ` Adriano Holanda
2002-01-28 3:31 Problems " kabir.patel
[not found] <616BE6A276E3714788D2AC35C40CD18D393F88@whale.softwire.co.uk>
2002-01-28 3:41 ` Rupert Wood
2002-01-28 4:16 ` Momchil Velikov
[not found] <616BE6A276E3714788D2AC35C40CD18D393F99@whale.softwire.co.uk>
2002-01-28 4:28 ` Rupert Wood
2005-02-09 1:46 problems " Jupp Tscheak
2005-02-09 1:46 Jupp Tscheak
[not found] <420931cd.73b89a7f.78a5.30baSMTPIN_ADDED@mx.gmail.com>
2005-02-09 9:11 ` corey taylor
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=Pine.SOL.3.96.991223110813.579C-100000@papaleguas.fmrp.usp.br \
--to=adriano@papaleguas.fmrp.usp.br \
--cc=gcc-help@gcc.gnu.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).