From: root <capitis@enteract.com>
To: help-gcc@gnu.org
Subject: make command refuses to do anything
Date: Fri, 31 Dec 1999 22:24:00 -0000 [thread overview]
Message-ID: <3849BB14.66E5CB87@enteract.com> (raw)
Message-ID: <19991231222400.vmGBdZyHmNB6HJOHvrI9qwvPWNmkNZAJ68fG6Rzf3rs@z> (raw)
I compiled kernel and gcc-2.95.1 among other things. I did them today, a
few hours ago.
Now I want to compile other programs and suddenly 'make' seems to have
lost any
strength. The following is the error message. ./configure did not
display any error.
I tried another file to compile and the result is the same. What did I
do?
======== error ============
make all-recursive
make[1]: Entering directory `/usr/src/glib-1.2.6'
Making all in .
make[2]: Entering directory `/usr/src/glib-1.2.6'
make[2]: Leaving directory `/usr/src/glib-1.2.6'
Making all in gmodule
make[2]: Entering directory `/usr/src/glib-1.2.6/gmodule'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/glib-1.2.6/gmodule'
Making all in gthread
make[2]: Entering directory `/usr/src/glib-1.2.6/gthread'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/glib-1.2.6/gthread'
Making all in docs
make[2]: Entering directory `/usr/src/glib-1.2.6/docs'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/glib-1.2.6/docs'
Making all in tests
make[2]: Entering directory `/usr/src/glib-1.2.6/tests'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/usr/src/glib-1.2.6/tests'
make[1]: Leaving directory `/usr/src/glib-1.2.6'
next reply other threads:[~1999-12-31 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-04 17:08 root [this message]
1999-12-31 22:24 ` root
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=3849BB14.66E5CB87@enteract.com \
--to=capitis@enteract.com \
--cc=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).