public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Chad Walstrom <chewie@wookimus.net>
To: help-gnats@gnu.org
Subject: Re: gnatsd problems with 4.0.1
Date: Mon, 07 Feb 2005 19:17:00 -0000	[thread overview]
Message-ID: <20050207191251.GB15693@wookimus.net> (raw)
In-Reply-To: <28735.1107796160@juniper.net>


[-- Attachment #1.1: Type: text/plain, Size: 1307 bytes --]

Mark D. Baushke wrote:
> I would suggest consideration of including the GNULIB versions of
> those functions as an alternative.

Cool.  I didn't know this [1]_ existed.

> this does probably make a vote of moving to a use of autoconf and
> automake as a part of building the configure and related files in
> order to make this easier to use.

We are currently using autoconf, but not automake.  Part of the reason I
updated the libiberty directory in the first place was because of
updating our autoconf version requirements.  Perhaps it's time to push
the move to automake as well.  You mentioned this not too long ago, and
I expressed interest in holding off until 4.2.  I consider cleaning up
the libiberty mess important enough for 4.1, and if automake is required
to do that, then I'd support that move as well.

With tree clean-up in mind, it looks like the makefile stubs in ./config
are pretty much useless now, and have been for at least three years.  We
may as well use that for storing autoconf files, etc.  Additionally,
gnats/man looks out-of-date with respect to doc/man.

.. [1] http://www.gnu.org/software/gnulib/manual/gnulib.html

-- 
Chad Walstrom <chewie@wookimus.net>           http://www.wookimus.net/
           assert(expired(knowledge)); /* core dump */

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
Help-gnats mailing list
Help-gnats@gnu.org
http://lists.gnu.org/mailman/listinfo/help-gnats

  reply	other threads:[~2005-02-07 19:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-05 18:23 Tim Buck
2005-01-05 22:24 ` Chad Walstrom
2005-01-06  9:18   ` Mike M. Volokhov
2005-01-06 17:07     ` Chad Walstrom
2005-02-07 15:47       ` Mike M. Volokhov
2005-02-07 17:15         ` Mark D. Baushke
2005-02-07 19:17           ` Chad Walstrom [this message]
2005-02-09 12:50           ` Removing libiberty (was Re: gnatsd problems with 4.0.1) Mike M. Volokhov
2005-02-09 17:15             ` Mark D. Baushke
2005-02-07 17:45         ` Chad Walstrom
2005-02-09 10:56           ` Mike M. Volokhov
     [not found]             ` <20050221235730.GC31157@wookimus.net>
     [not found]               ` <20050222175714.30bc1593.mishka@apk.od.ua>
2005-02-24 22:17                 ` Soon to come: RC3 Chad Walstrom
2005-02-24 22:40                   ` RC2 (was Re: Soon to come: RC3) Chad Walstrom
2005-01-06 16:03   ` gnatsd problems with 4.0.1 Tim Buck

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=20050207191251.GB15693@wookimus.net \
    --to=chewie@wookimus.net \
    --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).