From owner-freebsd-stable@FreeBSD.ORG Mon Dec 8 10:16:32 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6F7716A4CE for ; Mon, 8 Dec 2003 10:16:32 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-234.dsl.lsan03.pacbell.net [63.207.60.234]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB16743FBD for ; Mon, 8 Dec 2003 10:16:30 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 5187866C8E; Mon, 8 Dec 2003 10:16:30 -0800 (PST) Date: Mon, 8 Dec 2003 10:16:30 -0800 From: Kris Kennaway To: Illia Baidakov Message-ID: <20031208181630.GA49599@xor.obsecurity.org> References: <1069801150.20031208154655@newchem.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="pWyiEgJYm5f9v55/" Content-Disposition: inline In-Reply-To: <1069801150.20031208154655@newchem.ru> User-Agent: Mutt/1.4.1i cc: freebsd-stable@freebsd.org Subject: Re: 'long long' warning while compiling mit-kerberos on 4.9-stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2003 18:16:32 -0000 --pWyiEgJYm5f9v55/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Dec 08, 2003 at 03:46:55PM +0300, Illia Baidakov wrote: > Hello freebsd-stable, >=20 > I'm thinking it's the right list about my problem. > The exact messages while compiling mit-kerberos5-1.3.1 are: > /usr/include/stdlib.h:111: warning: ANSI C does not support `long > long' > /usr/include/stdlib.h:117: warning: ANSI C does not suppotr `long > long' >=20 > I have gcc version 2.95.4 in my system. Trying to build gcc-3.3.2 > from sources the above messages has repeated again right up to > stopping the building proccess. >=20 > What is the safest way to receive correct 'long long' type > definition in C compiler? That's a warning, not an error. If you're seeing your compilation stop, that's because there's either an actual error being reported, or because you or the software developer has told gcc to treat warnings as errors (e.g. -pedantic or -Werror, etc). Kris --pWyiEgJYm5f9v55/ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE/1L/+Wry0BWjoQKURAvZeAJ9dXMU3+iXw34PriLuldxk9IWuNQgCcCKbf DEO7SbgpgOpR8urJ3JUfduo= =wYii -----END PGP SIGNATURE----- --pWyiEgJYm5f9v55/--