From: "Mark D. Baushke" <mdb@cvshome.org>
To: help-gnats@gnu.org
Subject: Re: automake-ize -- slow going
Date: Mon, 11 Apr 2005 05:10:00 -0000 [thread overview]
Message-ID: <83410.1113195440@juniper.net> (raw)
In-Reply-To: <20050410200853.GB21214@wookimus.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chad Walstrom <chewie@wookimus.net> writes:
> Well, I thought I was clipping right along with converting the GNATS
> build process to automake, but realize that there is a lot of cleanup
> to do. The target version of the tools I'll be using is automake (and
> aclocal) 1.8, and autoconf 2.59.
For what it is worth, the cvshome.org project has moved to automake
1.9.5 which fixes a fair number of problems. The only one remaining is
some problems with bison dependencies even when folks do not use
- --enable-maintainer-mode (btw: The CVSHOME are eagerly awaiting automake
1.10 which will have a fix for this problem). The CVS project is also
using autoconf 2.59.
> My biggest hangup right now is trying to get AC_CONFIG_AUX_DIR to
> actually set ac_aux_dir in the generated configure file.
Is there a good reason not to just use the
AC_INIT([GNATS],[version],[bug-gnats@gnu.org],[gnats])
AC_CONFIG_AUX_DIR(build-aux)
AM_INIT_AUTOMAKE([gnu 1.8 dist-bzip2 no-define])
AC_PREREQ(2.59)
to set the ac_aux_dir ? You may also want to move to 1.9.5 as I believe
it has a number of nits fixed.
> It's not happening, and running autoupdate to update the configure.ac
> file isn't running all the way through. There's more manual cleanup
> for me to do.
>
> I'll keep you posted.
Thanks,
-- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (FreeBSD)
iD8DBQFCWgOw3x41pRYZE/gRAgTUAJ9WC7Na/xLBdAWrLG1c0C1iYhkzrwCgz7jt
Bz+3yRo8BSy9PeM519yJ8F4=
=lfAE
-----END PGP SIGNATURE-----
_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats
next prev parent reply other threads:[~2005-04-11 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 20:15 Chad Walstrom
2005-04-11 5:10 ` Mark D. Baushke [this message]
2005-04-11 17:28 ` Chad Walstrom
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=83410.1113195440@juniper.net \
--to=mdb@cvshome.org \
--cc=help-gnats@gnu.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).