Date: Sun, 6 Dec 2009 18:15:40 +0100 (CET) From: olli hauer <ohauer@gmx.de> To: FreeBSD-gnats-submit@FreeBSD.org Cc: ohauer@gmx.de Subject: ports/141226: port textproc/libxml2 latest patch seems broken Message-ID: <20091206171540.8C018261C1@u18-124.dsl.vianetworks.de> Resent-Message-ID: <200912061720.nB6HK1RP005697@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 141226 >Category: ports >Synopsis: port textproc/libxml2 latest patch seems broken >Confidential: no >Severity: non-critical >Priority: high >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Dec 06 17:20:01 UTC 2009 >Closed-Date: >Last-Modified: >Originator: olli hauer <ohauer@gmx.de> >Release: FreeBSD 7.2-RELEASE i386 >Organization: >Environment: >Description: It seems the last change from libxml2 does not work as expected. see thread in forums.freebsd.org http://forums.freebsd.org/showthread.php?t=8965 Forum users have reported segfaults and other strange things after applications are running a while. Temporary workaround found by one user is to remove the following lines from patch-configure which seems to work for others as well > @@ -20665,6 +20666,8 @@ > fi > fi > ;; >How-To-Repeat: http://forums.freebsd.org/showthread.php?t=8965 I cannot confirm, since I read the thread in freebsd forums before I've done some updates and moved back to the old libxml2 version >Fix: >Release-Note: >Audit-Trail: >Unformatted: >+ *freebsd*) THREAD_LIBS="" >+ ;; > esac > if test "$WITH_THREADS" = "1" ; then > THREAD_CFLAGS="$THREAD_CFLAGS -D_REENTRANT"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091206171540.8C018261C1>