From owner-freebsd-ports@freebsd.org Sun Jan 8 22:20:43 2017 Return-Path: Delivered-To: freebsd-ports@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 093DACA624A for ; Sun, 8 Jan 2017 22:20:43 +0000 (UTC) (envelope-from freebsd01@dgmm.net) Received: from outbound-queue-adx-1.mail.thdo.gradwell.net (outbound-queue-adx-1.mail.thdo.gradwell.net [212.11.71.246]) by mx1.freebsd.org (Postfix) with ESMTP id CA41C13A4 for ; Sun, 8 Jan 2017 22:20:42 +0000 (UTC) (envelope-from freebsd01@dgmm.net) Received: from outbound-edge-adx-1.mail.thdo.gradwell.net (outbound-edge-adx-1.mail.thdo.gradwell.net [212.11.71.230]) by outbound-queue-adx-1.mail.thdo.gradwell.net (Postfix) with ESMTP id 1B41421D26 for ; Sun, 8 Jan 2017 22:19:48 +0000 (GMT) Received: from cpc89374-jarr11-2-0-cust348.16-2.cable.virginm.net (HELO amd.asgard.uk) (82.13.141.93) (smtp-auth username dave%pop3.dgmm.net, mechanism plain) by outbound-edge-adx-1.mail.thdo.gradwell.net (qpsmtpd/0.83) with ESMTPA; Sun, 08 Jan 2017 22:19:48 +0000 From: Dave To: freebsd-ports@freebsd.org Subject: Pan core dumps on start Date: Sun, 08 Jan 2017 22:19:46 +0000 Message-ID: <10323689.CU0Y35S3Lv@amd.asgard.uk> User-Agent: KMail/4.14.10 (FreeBSD/10.3-RELEASE-p11; KDE/4.14.10; amd64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Gradwell-MongoId: 5872bb04.d0b-3345-1 X-Gradwell-Auth-Method: mailbox X-Gradwell-Auth-Credentials: dave@pop3.dgmm.net X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Jan 2017 22:20:43 -0000 Recently upgraded my system from 9.3 to 10.3 via freebsd-update. Upgraded packages with pkg upgrade -f Now Pan core dumps on startup. Googling around lead me to this bug/commit https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199303 However, that commit implied the bug is fixed but using the suggested workaround of... cd /usr/ports/news/pan make LDFLAGS="-static-libgcc -static-libstdc++" ...solves the problem. Has this patch been reverted? Or is there maybe something I've not done which I need to do? I don't understand "Staticly link to libgcc and libstdc++. This fixes a segmentation fault when trying to run pan on a libc++ based system." Does this mean 10.3 is a libc++ system and 9.3 isn't? Or does it mean I have stuff left over from the 9.3 system that should now be removed? Likewise "The fix is to force libs from gcc". Does this mean I should no longer have gcc and just have clang now? Or is gcc still required by other stuff?