[Bug 207268] irc/ircd-ratbox needs GCC to RUN on i386 (builds fine with CLANG but crashes)
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Feb 17 01:39:56 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=207268
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 at FreeBSD.org
Reporter: John.Marshall at riverwillow.com.au
CC: moggie at elasticmind.net
CC: moggie at elasticmind.net
Flags: maintainer-feedback?(moggie at 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= 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 seems 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 leave
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
===================================================================
--- Makefile (revision 409014)
+++ Makefile (working copy)
@@ -19,6 +19,9 @@
CPE_VENDOR= ratbox
USE_RC_SUBR= ircd-ratbox
USE_LDCONFIG= ${PREFIX}/lib/ircd-ratbox
+.if ${MACHINE_ARCH} == "i386"
+USE_GCC= yes
+.endif
MAKE_JOBS_UNSAFE= yes
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list