From: Mikael Löfgren <mikael@hq.vcc.volvo.se>
To: gnu@gnu.org
Subject: Compile problems with gnu-2.8.0 on AIX 4.3.2.0
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <200003161756.MAA31573@delysid.gnu.org> (raw)
Message-ID: <20000401000000.pZ5aIi75Vcut4H2ih8hYm7zE8F6KihZsbKUIdvX-csg@z> (raw)
Hi
I get a error messege when I run make command. First I run then
configure command.
#/usr/local/gcc: ../../../tmp/gcc-2.8.0/configure
--srcdir=../../../tmp/gcc-2.8.0
This runs ok without errors
Then I run make
#/usr/local/gcc: make
This command end with this errors messeges. I show you the last lines
fp-bit
xgcc: fp-bit.c: No such file or directory
xgcc: No input files
make: 1254-004 The error code from the last command is 1.
Stop.
make: 1254-004 The error code from the last command is 2.
Stop.
make: 1254-004 The error code from the last command is 2.
Stop.
//Why cant it find this file. This file is in the source directory
/tmp/gcc-2.8.0
Best regards
Mikael
next reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-16 9:56 Mikael Löfgren [this message]
2000-03-16 12:38 ` Martin v. Loewis
2000-04-01 0:00 ` Martin v. Loewis
2000-04-01 0:00 ` Mikael Löfgren
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=200003161756.MAA31573@delysid.gnu.org \
--to=mikael@hq.vcc.volvo.se \
--cc=gnu@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).