From owner-freebsd-ports@FreeBSD.ORG Sat Sep 16 19:55:35 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52D7D16A40F for ; Sat, 16 Sep 2006 19:55:35 +0000 (UTC) (envelope-from ssedov@mbsd.msk.ru) Received: from com1.ht-systems.ru (com1.ht-systems.ru [83.97.104.204]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7D67B43D45 for ; Sat, 16 Sep 2006 19:55:33 +0000 (GMT) (envelope-from ssedov@mbsd.msk.ru) Received: from [85.140.82.177] (helo=fonon.realnet) by com1.ht-systems.ru with esmtpa (Exim 4.62) (envelope-from ) id 1GOgG8-0007QN-2i; Sat, 16 Sep 2006 23:55:28 +0400 Received: from localhost (localhost [127.0.0.1]) by fonon.realnet (Postfix) with ESMTP id C21FE11B64; Sat, 16 Sep 2006 23:54:46 +0400 (MSD) Date: Sat, 16 Sep 2006 23:54:41 +0400 From: Stanislav Sedov To: Alexander Kabaev Message-ID: <20060916235441.1b209538@localhost> In-Reply-To: <20060916112841.31b5fa57@kan.dnsalias.net> References: <450B4DC0.10501@gmail.com> <20060916122933.558cadd7@localhost> <20060916112841.31b5fa57@kan.dnsalias.net> Organization: MBSD labs, Inc. X-Operating-System: FreeBSD X-Mailer: carrier-pigeon Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_o=4gxkcSgabcYBjOcOuqBJO"; protocol="application/pgp-signature"; micalg=PGP-SHA1 X-Spam-Flag: SKIP X-Spam-Yversion: Spamooborona 1.6.0 Cc: ports@freebsd.org Subject: Re: GCC 4.1 configure help X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Sep 2006 19:55:35 -0000 --Sig_o=4gxkcSgabcYBjOcOuqBJO Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable On Sat, 16 Sep 2006 11:28:41 -0400 Alexander Kabaev mentioned: > What is the point of this message? I asked for help and unless you > have a file I asked for, please spare me the lecture on how to do > compiler updates. I did it several times and full package runs on > multiple architectures were mandatory with all of them, as Kris can > attest. >=20 > Every compiler update breaks some ports, due to new bugs or more often > due to even more anal code correctness checks implemented with every > new major GCC release. Depending on their seriousness, GCC bugs are > either getting fixed in upstream sources or worked around locally, but > dealing with GCC strictness was always been something that port > maintainers were supposed to do themselves. >=20 > 3.4.4 - 3.4.6 update broke ports that had the code GCC no longer accepts > as valid C++. Sorry, I didn't want to offend anybody... Just to know when the update is planned. Thanks! --=20 Stanislav Sedov MBSD labs, Inc. =F2=CF=D3=D3=C9=D1, =ED=CF=D3=CB=D7=C1 http://mbsd.msk.ru -------------------------------------------------------------------- If the facts don't fit the theory, change the facts. -- A. Einstein -------------------------------------------------------------------- PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 --Sig_o=4gxkcSgabcYBjOcOuqBJO Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFFDFaGK/VZk+smlYERAl7cAJ0WsTRQs8SUOcdtZyDrtankH8DN1wCeJu42 H1NvdEHFNIvm4+ZPguNoQhY= =rElN -----END PGP SIGNATURE----- --Sig_o=4gxkcSgabcYBjOcOuqBJO--