public inbox for gnats-devel@sourceware.org
 help / color / mirror / Atom feed
From: Wes Barris <wesb@networkcs.com>
To: gnats-devel@sourceware.cygnus.com
Subject: gnats compiling error
Date: Fri, 09 Mar 2001 14:25:00 -0000	[thread overview]
Message-ID: <20010309162442.B79305@us.networkcs.com> (raw)

I am trying to compile gnats (downloaded using cvs) on a Redhat 7
system.

It appears that a string is too long for gcc on Redhat 7:

gcc -c -I. -I. -I./../include  -g -O2 -W -Wall -W -Wall -ansi -pedantic -Werror -Wstrict-prototypes -Wmissing-prototypes -Wwrite-strings -Wno-format  -DHAVE_CONFIG_H -DGNATSD_USER_ACCESS_FILE=\"/usr/local/share/gnats/gnatsd.access\" -DGNATSD_HOST_ACCESS_FILE=\"/usr/local/share/gnats/gnatsd.host_access\" -DDEFAULT_GNATS_SERVICE=\"support\" -DGLOBAL_DB_LIST_FILE=\"/usr/local/etc/gnats/databases\" -DGNATS_USER=\"gnats\" ./query-pr.c
cc1: warnings being treated as errors
./query-pr.c: In function `usage':
./query-pr.c:948: warning: string length `1617' is greater than the minimum length `509' ISO C89 is required to support
make[1]: *** [query-pr.o] Error 1
make[1]: Leaving directory `/home/wes/gnats/gnats'
make: *** [all-gnats] Error 2

-----------------------------------------------------------------------
Wes Barris                                            wes@networkcs.com
Network Computing Services, Inc.                           612.626.8090
-----------------------------------------------------------------------
Today's fortune: How many weeks are there in a light year?

             reply	other threads:[~2001-03-09 14:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-09 14:25 Wes Barris [this message]
2001-03-09 14:37 ` Gerald Pfeifer
2001-03-11 10:48 ` Milan Zamazal
2001-03-11 16:20   ` Gerald Pfeifer
2001-03-13 12:26     ` Milan Zamazal
2001-03-13 12:37       ` Gerald Pfeifer
2001-03-18 10:02         ` Milan Zamazal

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=20010309162442.B79305@us.networkcs.com \
    --to=wesb@networkcs.com \
    --cc=gnats-devel@sourceware.cygnus.com \
    /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).