Gnus development mailing list
 help / color / mirror / Atom feed
From: Linus Nordberg <linus@swox.se>
Subject: Building gnus in separate directory
Date: 27 May 2000 21:45:22 +0200	[thread overview]
Message-ID: <yszog5rwze5.fsf@king.swox.se> (raw)

Hi,

When configuring gnus in other dir than the source dir, building
texi/gnus fails because makeinfo can't find gnus-faq.texi, @include'd
in gnus.texi.

Couldn't we simply make a symlink into the build directory before
building texi/gnus?

--linus

Index: configure.in
===================================================================
RCS file: /usr/local/cvsroot/gnus/configure.in,v
retrieving revision 5.1
diff -c -p -c -r5.1 configure.in
*** configure.in	1998/08/29 17:42:59	5.1
--- configure.in	2000/05/26 19:38:15
***************
*** 1,6 ****
--- 1,7 ----
  AC_INIT(lisp/gnus.el)
  AC_SET_MAKE
  AC_PROG_INSTALL
+ AC_PROG_LN_S
  AM_PATH_LISPDIR
  AC_PATH_PROG(MAKEINFO, makeinfo, no)
  AC_OUTPUT(Makefile lisp/Makefile texi/Makefile)
Index: Makefile.in
===================================================================
RCS file: /usr/local/cvsroot/gnus/texi/Makefile.in,v
retrieving revision 5.9
diff -c -p -c -r5.9 Makefile.in
*** Makefile.in	2000/05/01 12:21:43	5.9
--- Makefile.in	2000/05/26 19:40:39
*************** INSTALL = @INSTALL@
*** 19,24 ****
--- 19,27 ----
  INSTALL_DATA = @INSTALL_DATA@
  SHELL = /bin/sh
  PAPERTYPE=a4
+ LN_S = @LN_S@
+ #FIXME: Use LN_S to symlink $(srcdir)/gnus-faq.texi to build dir before 
+ #       making gnus.
  
  all: gnus message emacs-mime
  



             reply	other threads:[~2000-05-27 19:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-27 19:45 Linus Nordberg [this message]
2000-05-28  7:00 ` Norbert Koch
2000-05-28 13:57   ` Linus Nordberg

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=yszog5rwze5.fsf@king.swox.se \
    --to=linus@swox.se \
    /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 NNTP newsgroup(s).