public inbox for gnats-prs@sourceware.org
help / color / mirror / Atom feed
From: stanley_z@hotmail.com
To: pdm-gnats@zamazal.org,gnats-prs@gnu.org,bug-gnats@gnu.org
Subject: gnats/323: gnats4 make error when buile gnats in different directory from the source code
Date: Fri, 11 Jan 2002 05:56:00 -0000	[thread overview]
Message-ID: <E16OYdB-0006RL-00@fencepost.gnu.org> (raw)

>Number:         323
>Category:       gnats
>Synopsis:       gnats4 make error when buile gnats in different directory from the source code
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 10 01:24:04 -0500 2002
>Originator:     stanley_z@hotmail.com
>Release:        4.0 Beta 1
>Organization:

>Environment:
cvs check out on 2002-01-10
on FreeBSD 4.4 release.
>Description:
I configure and make gnats in a different directory from the source code directory.
I got a error when making the document.
The error message is like below:

echo "@set VERSION 4.0-beta1" > version.texi-t
mv version.texi-t version.texi
gmake[1]: Leaving directory `/home/thinker/gnats/current/work/send-pr'
gmake[1]: Entering directory `/home/thinker/gnats/current/work/doc'
gmake[1]: *** No rule to make target `../../gnats/doc/version.texi', needed by `
gnats.info'.  Stop.
gmake[1]: Leaving directory `/home/thinker/gnats/current/work/doc'
gmake: *** [all-gnats] Error 2    

But this error will not happen when I build gnats in the directory where gnats source code located.
>How-To-Repeat:
To make a directory in the same level with gnats source directory.
mkdir work
cd work
../gnats/configure
gmake all info
>Fix:
Unknown
>Unformatted:
 

_______________________________________________
Gnats-prs mailing list
Gnats-prs@gnu.org
http://mail.gnu.org/mailman/listinfo/gnats-prs


                 reply	other threads:[~2002-01-11 13:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E16OYdB-0006RL-00@fencepost.gnu.org \
    --to=stanley_z@hotmail.com \
    --cc=bug-gnats@gnu.org \
    --cc=gnats-prs@gnu.org \
    --cc=pdm-gnats@zamazal.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).