From: Aaron VanDevender <sig@netdot.net>
Subject: versions in CVS
Date: Fri, 10 Jan 2003 23:08:51 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.44.0301102257160.5059-100000@roxanne.bos.netdot.net> (raw)
I just checked out the sources from CVS and tried to build. The make died
when makeinfo was unable to find guile/guile-core/doc/ref/version.texi and
guile/guile-core/doc/tutorial/version.texi. These files were @included
from some of the other texi files in thoes directories. I dropped a file
in the appropriate locations which had EDITION and VERSION lines in it and
then the make went fine, but it seems like those files should be there in
the cvs.
Also, when things are built and installed, the data part gets put in a
directory based on the EFFECTIVE_VERSION and not the version so we have
things like /usr/local/share/guile/1.7/scripts, but things like
guile-tools are looking in the VERSION directory, i.e.
/usr/local/share/guile/1.7.0/scripts, and obviously not finding anything.
This should probably get sorted out.
cya
.sig
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next reply other threads:[~2003-01-11 4:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 4:08 Aaron VanDevender [this message]
2003-01-12 18:13 ` versions in CVS Marius Vollmer
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=Pine.LNX.4.44.0301102257160.5059-100000@roxanne.bos.netdot.net \
--to=sig@netdot.net \
/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).