ports/131794: irc/blackened broken for 64-bit systems in -current
Peter Jeremy
peterjeremy at optushome.com.au
Tue Feb 17 22:00:17 UTC 2009
>Number: 131794
>Category: ports
>Synopsis: irc/blackened broken for 64-bit systems in -current
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Tue Feb 17 22:00:02 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Peter Jeremy
>Release: FreeBSD 8.0-CURRENT amd64
>Organization:
n/a
>Environment:
System: FreeBSD server.vk2pj.dyndns.org 8.0-CURRENT FreeBSD 8.0-CURRENT #5: Sun Feb 15 21:09:05 EST 2009 root at server.vk2pj.dyndns.org:/var/obj/usr/src/sys/server amd64
>Description:
blackened core-dumps during screen initialisation in -current.
Some investigating with gdb shows that pointers are being
truncated to 32-bits. Re-compiling blackened with '-Wall'
reveals large numbers of "implicit declaration of function"
warnings as well as several int/long mismatches in printf()s.
Since the current tarball is 6 years old, has no homepage,
no FreeBSD maintainer and the IRC channel quoted for support
doesn't work, I'd suggest that this is abandonware and the
port be deprecated and scheduled for deorbit. Given the age
and number of coding errors revealed with '-Wall', it would
not surprise me if there were secutiry issues as well. Note
that I am not currently in a position to become maintainer.
>How-To-Repeat:
Run 64-bit blackened executable on 64-bit -current system.
>Fix:
Either correct coding errors revealed by -Wall or remove from
ports.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list