From owner-freebsd-ports-bugs@freebsd.org Wed Feb 17 01:39:56 2016 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 86EC4AAB7BF for ; Wed, 17 Feb 2016 01:39:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5CACA1E8B for ; Wed, 17 Feb 2016 01:39:56 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u1H1dt6o043039 for ; Wed, 17 Feb 2016 01:39:56 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 207268] irc/ircd-ratbox needs GCC to RUN on i386 (builds fine with CLANG but crashes) Date: Wed, 17 Feb 2016 01:39:56 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: John.Marshall@riverwillow.com.au X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter cc flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Feb 2016 01:39:56 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D207268 Bug ID: 207268 Summary: irc/ircd-ratbox needs GCC to RUN on i386 (builds fine with CLANG but crashes) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: freebsd-ports-bugs@FreeBSD.org Reporter: John.Marshall@riverwillow.com.au CC: moggie@elasticmind.net CC: moggie@elasticmind.net Flags: maintainer-feedback?(moggie@elasticmind.net) After a successful build of irc/ircd-ratbox on i386 it fails to run... Feb 17 10:08:08 rwsrv04 kernel: pid 28391 (ircd), uid 72: exited on signal = 11 (core dumped) This has been going on for a long time now. I have been working around this= by just adding "USE_GCC=3D yes" near the top of the Makefile on the only i386 = server we are still running. I would submit a patch but I cannot find the canonical way of doing this in an arhitecture-specific way. The Porters Handbook seem= s to be silent on the matter. make(1) says that MACHINE_ARCH is available for testing architecture but I cannot see that used in other ports. It looks like ARCH is the preferred variable. ARCH is setup in bsd.port.mk but bsd.port.mk is what processes the dependent USE_GCC variable. So, the following patch "works for me" but I le= ave it to the ports gurus to do this according to the traditions of the rites of the inner sanctum of ports committers. rwsrv04# svn diff Makefile Index: Makefile =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- Makefile (revision 409014) +++ Makefile (working copy) @@ -19,6 +19,9 @@ CPE_VENDOR=3D ratbox USE_RC_SUBR=3D ircd-ratbox USE_LDCONFIG=3D ${PREFIX}/lib/ircd-ratbox +.if ${MACHINE_ARCH} =3D=3D "i386" +USE_GCC=3D yes +.endif MAKE_JOBS_UNSAFE=3D yes --=20 You are receiving this mail because: You are the assignee for the bug.=