From owner-freebsd-stable@FreeBSD.ORG Thu Jan 27 08:21:45 2005 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 4CDFC16A4CE for ; Thu, 27 Jan 2005 08:21:45 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA04143D55 for ; Thu, 27 Jan 2005 08:21:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id ECAE95150F; Thu, 27 Jan 2005 00:21:42 -0800 (PST) Date: Thu, 27 Jan 2005 00:21:42 -0800 From: Kris Kennaway To: Kris Kennaway Message-ID: <20050127082142.GA40108@xor.obsecurity.org> References: <20050126104801.30643.qmail@web54008.mail.yahoo.com> <3aaaa3a0501260403611abe49@mail.gmail.com> <41F7F842.3030507@cs.tu-berlin.de> <3aaaa3a050126234230d8496c@mail.gmail.com> <20050127081737.GA6254@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="9jxsPFA5p3P2qPhR" Content-Disposition: inline In-Reply-To: <20050127081737.GA6254@xor.obsecurity.org> User-Agent: Mutt/1.4.2.1i cc: Chris cc: freebsd-stable@freebsd.org Subject: Re: Linking problems with gcc 3.4.2 and glibc on 5.3-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: Thu, 27 Jan 2005 08:21:45 -0000 --9jxsPFA5p3P2qPhR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 27, 2005 at 12:17:37AM -0800, Kris Kennaway wrote: > On Thu, Jan 27, 2005 at 07:42:11AM +0000, Chris wrote: > > Well it started out with me getting a complaint from a user on my > > server saying he couldnt compile psybnc since I upgraded to 5.3 I told > > him I would investigate when I get time, I then found out later that > > ezbounce also failed (i use ezbounce) on 5.3, but my binary which was > > backed up from when I compiled on 5.2.1 works fine. I also heard from > > many friends on irc that psybnc doesnt work with 5.3 so obviously the > > problem is wide spread and it was one reason why a lot of shell > > companies were not upgrading from 4.x yet. I then decided to try > > psybnc myself and this is what happens using gcc 3.4.2 bundled with > > 5.3. > >=20 > > Initializing bouncer compilation > > [*] Running Conversion Tool for older psyBNC Data. > > tools/convconf.c: In function `cofile': > > tools/convconf.c:81: error: label at end of compound statement > > *** Error code 1 >=20 > That's a source code bug, of course, not a gcc bug. Do try to get > your accusations straight. >=20 > The ezbounce port compiles fine on 5.3: >=20 > http://pointyhat.freebsd.org/errorlogs/i386-5-full-logs/ezbounce-1.04.b.l= og.bz2 >=20 > The psybnc port is not compilable automatically since it's > interactive, so this problem has not been detected by the automated > builds. You should raise it with the psybnc port maintainer or the > software developers. In fact, the psybnc port builds fine too. Don't you look foolish now? :-) Kris --9jxsPFA5p3P2qPhR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFB+KSWWry0BWjoQKURAqlUAKCUuljd29lRNa7yvyXyQvCLXkXczQCgqtpK /oI85OPXXwZ2L3WI6pNVCxQ= =8hJC -----END PGP SIGNATURE----- --9jxsPFA5p3P2qPhR--