From: "Neil W. Van Dyke" <nwv@neilvandyke.org>
Subject: autoconf 2.53 breaks guile-core 1.6 autogen.sh
Date: Sun, 17 Mar 2002 07:09:51 -0500 [thread overview]
Message-ID: <15508.34703.689900.139208@winona.neilvandyke.org> (raw)
Just FYI...
Autoconf 2.53 treats use of "LIBOBJS" as an error, preventing
"autogen.sh" of the 1.6 branch of package "guile-core" from running.
% ./autogen.sh
WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
WARNING: and `config.h.top', to define templates for `config.h.in'
WARNING: is deprecated and discouraged.
WARNING: Using the third argument of `AC_DEFINE' and
WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
WARNING: `acconfig.h':
WARNING: AC_DEFINE([NEED_MAIN], 1,
WARNING: [Define if a function `main' is needed.])
WARNING: More sophisticated templates can also be produced, see the
WARNING: documentation.
configure.in:30: warning: do not use m4_patsubst: use patsubst or
m4_bpatsubst
configure.in:689: warning: do not use m4_regexp: use regexp or m4_bregexp
autoheader2.50: `libguile/scmconfig.h.in' is unchanged
configure.in:135: error: do not use LIBOBJS directly, use AC_LIBOBJ
(see section `AC_LIBOBJ vs. LIBOBJS'
--
Neil W. Van Dyke
http://www.neilvandyke.org/
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2002-03-17 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-17 12:09 Neil W. Van Dyke [this message]
2002-03-22 3:22 ` autoconf 2.53 breaks guile-core 1.6 autogen.sh Rob Browning
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=15508.34703.689900.139208@winona.neilvandyke.org \
--to=nwv@neilvandyke.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).