Skip site navigation (1)Skip section navigation (2)
Date:      Sun,  8 Jul 2001 22:01:41 -0500 (CDT)
From:      grasshacker@over-yonder.net
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   ports/28828: xlockmore port is broken on -current
Message-ID:  <20010709030141.00D6E62D0A@draco.over-yonder.net>

next in thread | raw e-mail | index | archive | help

>Number:         28828
>Category:       ports
>Synopsis:       xlockmore port is broken on -current
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-ports
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Jul 08 20:10:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     grasshacker@over-yonder.net
>Release:        FreeBSD 5.0-CURRENT i386
>Organization:
>Environment:
System: FreeBSD mach.domain.com 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Jul  1 22:57:58 CDT 2001 root@mach.domain.com:/usr/obj/usr/src/sys/MACH.new  i386 


	
>Description:
	The xlockmore port is broken on -current. The build fails at linking
	xlock due to missing pthread_setspecific, et. al. functions. Adding
	'-lc_r' to work/xlockmore-5.01/modes/Makefile: XLOCKLIBS allows the
	build to complete.
>How-To-Repeat:
	cd /usr/ports/x11/xlockmore
	make all
>Fix:
	It can be immediately fixed by adding -lc_r to XLOCKLIBS in 
	work/xlockmore-5.01/modes/Makefile. This only fixes the symptom, not
	the problem.
>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010709030141.00D6E62D0A>