From: Kevin Ryde <user42@zip.com.au>
Cc: bug-guile@gnu.org, Mattias Holm <mattias.holm@contra.nu>
Subject: Re: parallel make fails for guile 1.8
Date: Tue, 06 Jun 2006 10:46:01 +1000 [thread overview]
Message-ID: <87fyij1586.fsf@zip.com.au> (raw)
In-Reply-To: <874pz1paw3.fsf@ossau.uklinux.net> (Neil Jerram's message of "Sun, 04 Jun 2006 09:45:16 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
>
> I think that means it can be certainly be removed from BUILT_SOURCES.
Beaut, I did that.
> It probably doesn't need to be built automatically at all; a developer
> can do "make guile.texi" when they need it.
Sticking it in "nodist_noinst_DATA = guile.texi" seems to work to get
it built under "make all", if you still want it. If normal users
don't need it then maybe it should be restricted to "if
ENABLE_MAINTAINER_MODE" though.
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2006-06-06 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-27 19:58 parallel make fails for guile 1.8 Mattias Holm
2006-05-31 19:48 ` Neil Jerram
2006-06-02 23:24 ` Kevin Ryde
2006-06-04 8:45 ` Neil Jerram
2006-06-06 0:46 ` Kevin Ryde [this message]
2006-06-06 20:08 ` Neil Jerram
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fyij1586.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=bug-guile@gnu.org \
--cc=mattias.holm@contra.nu \
/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).