From: Ian Lance Taylor <iant@google.com>
To: cihan <cihan@enderunix.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: gcc 2.95.3 building problem
Date: Thu, 14 Aug 2008 21:42:00 -0000 [thread overview]
Message-ID: <m363q3ifqh.fsf@google.com> (raw)
In-Reply-To: <48A473CE.6060101@enderunix.org> (cihan@enderunix.org's message of "Thu\, 14 Aug 2008 21\:05\:02 +0300")
cihan <cihan@enderunix.org> writes:
> if [ x"no" = xyes ] && [ ! -d pic ]; then \
> mkdir pic; \
> else true; fi
> touch stamp-picdir
> make[1]: *** No rule to make target `../include/libiberty.h', needed
> by `argv.o'. Stop.
> make[1]: Leaving directory
> /home/cihan/gcc-2.95.3/i486-slackware-linux/libiberty'
> make: *** [all-target-libiberty] Error 2
Did you by any chance run ./configure, rather than running the
configure script in a different empty directory?
Ian
prev parent reply other threads:[~2008-08-14 19:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 20:32 cihan
2008-08-12 20:54 ` Ian Lance Taylor
2008-08-13 19:47 ` cihan
2008-08-14 4:05 ` Ian Lance Taylor
2008-08-14 19:01 ` cihan
2008-08-14 21:42 ` Ian Lance Taylor [this message]
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=m363q3ifqh.fsf@google.com \
--to=iant@google.com \
--cc=cihan@enderunix.org \
--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).