Date: Wed, 16 Jul 2003 20:53:31 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Shin-ichi YOSHIMOTO <yosimoto@waishi.jp> Cc: freebsd-ports@freebsd.org Subject: Re: some ports are broken after upgrading GCC 3.3.1 Message-ID: <20030717035331.GA31260@rot13.obsecurity.org> In-Reply-To: <20030717092556.70a96dc9.yosimoto@waishi.jp> References: <20030713010957.2181af46.yosimoto@waishi.jp> <20030717092556.70a96dc9.yosimoto@waishi.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
--ikeVEW9yuYc//A+q Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jul 17, 2003 at 09:25:56AM +0900, Shin-ichi YOSHIMOTO wrote: > Subject: some ports are broken after upgrading GCC 3.3.1, > On Sun, 13 Jul 2003 01:09:57 +0900, Shin-ichi YOSHIMOTO wrote: > > ** The following packages were not installed or upgraded (*:skipped / != :failed) > > ! graphics/libungif (libungif-4.1.0b1) (bad C++ code) > > ! x11-servers/XFree86-4-Server (XFree86-Server-4.3.0_8) (unknow= n build error) > > ! x11/XFree86-4-clients (XFree86-clients-4.3.0_2) (coredu= mp) >=20 > XFree86-4-Server and XFree86-4-clients are fine, but libungif is still ba= d, >=20 > [snip] > /bin/sh ../libtool --mode=3Dcompile cc -DHAVE_CONFIG_H -I. -I. -I.. -= O -pipe -march=3Dpentium4 -I/usr/X11R6/include -c qprintf.c > rm -f .libs/qprintf.lo > cc -DHAVE_CONFIG_H -I. -I. -I.. -O -pipe -march=3Dpentium4 -I/usr/X11R6/i= nclude -c qprintf.c -fPIC -DPIC -o .libs/qprintf.lo > qprintf.c: In function `GifQprintf': > qprintf.c:38: error: syntax error before '...' token > qprintf.c:43: error: syntax error before "__builtin_varargs_start" > *** Error code 1 >=20 > Any idea ? libungif and several hundred other ports. Results from a bento build will be coming through over the next few days, and we need to try to coordinate work on fixing these ports. There are about 3 or 4 major causes of failure, which should be mostly mechanical in nature to fix. I'm hoping to gather some example patches to show people how to fix the different problems, so we can then figure out how to divide up the work. Kris --ikeVEW9yuYc//A+q Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/Fh27Wry0BWjoQKURAveOAJ9MhaXt/FiulxuHgd90n5rG4ntaWgCfWV8J dOpZAysD8Hx0JoZcHb7iB/o= =3TpL -----END PGP SIGNATURE----- --ikeVEW9yuYc//A+q--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030717035331.GA31260>