From owner-freebsd-ports@FreeBSD.ORG Thu Jul 17 20:15:54 2003 Return-Path: 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 7F47337B409; Thu, 17 Jul 2003 20:15:53 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-67-119-53-152.dsl.lsan03.pacbell.net [67.119.53.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7593A43F93; Thu, 17 Jul 2003 20:15:51 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 98B1C66EB8; Thu, 17 Jul 2003 20:15:26 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id F397DC10; Thu, 17 Jul 2003 19:52:00 -0700 (PDT) Date: Thu, 17 Jul 2003 19:52:00 -0700 From: Kris Kennaway To: current@FreeBSD.org, ports@FreeBSD.org Message-ID: <20030718025200.GA36893@rot13.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="huq684BweRXVnRxX" Content-Disposition: inline User-Agent: Mutt/1.4.1i Subject: Fixing gcc 3.3 compile failures X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jul 2003 03:15:55 -0000 --huq684BweRXVnRxX Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable OK, now that the latest 5.x package build is well underway, we can start work on fixing the compile failures seen with gcc 3.3. These are the ports that have become broken on the latest build (everything after July 14): http://bento.freebsd.org/errorlogs/i386-5-failure.html Here is the full list of broken ports from the build in progress: http://bento.freebsd.org/errorlogs/i386-5-latest/ If you are running 4.x, you can also help to develop fixes for these ports by installing the gcc33 port and setting CC=3D/usr/local/bin/gcc33 CXX=3D/usr/local/bin/g++33 in your environment. Most of the new compile failures are caused by 3 or 4 types of failure mode (all of which have to do with stricter standards compliance in the new compiler suite). I haven't yet looked at how to fix most of them: if you figure out a patch for a class of failures, please post it in response to this email so we can all see how to do it. To start things off: http://bento.freebsd.org/errorlogs/i386-5-latest/arts++-1-1-a8_1.log =2E.. ArtsRttTimeSeriesTableData.cc:873: error: `assert' undeclared (first use th= is=20 function) =2E.. This class of error is fixed by adding=20 #include to the top of the file. NOTE: There are at least two recent failure modes that have been introduced into 5.x that are not due to gcc33. 1) The recent texinfo port changed the default info generation style to not produce split files, which breaks a lot of pkg-plists. A patch was submitted to the ports@ list a few days ago to allow bsd.port.mk to better handle info files, but I haven't yet evaluated or tested it. I hope to have the time over the weekend. 2) Recent *.mk changes by ru have apparently broken a number of ports: http://bento.freebsd.org/errorlogs/i386-5-latest/tcl-8.0.5.log =2E.. nm: ../generic/panic.o: No such file or directory nm: ../generic/regexp.o: No such file or directory nm: ../generic/tclAsync.o: No such file or directory =2E.. This will be probably be corrected once ru returns from vacation in a few weeks. Please don't attempt to do anything with these ports for now. Kris --huq684BweRXVnRxX Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/F2DQWry0BWjoQKURAts4AKDXGUpedDCR1qs2trdclOXqFe4ikQCffQ98 QNSeL1mYxZJaVLLn38S1efY= =8xwm -----END PGP SIGNATURE----- --huq684BweRXVnRxX--