From owner-freebsd-current@FreeBSD.ORG Sat Sep 13 03:37:57 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00DF616A4BF for ; Sat, 13 Sep 2003 03:37:57 -0700 (PDT) Received: from holly.xtaz.co.uk (82-32-29-13.cable.ubr04.azte.blueyonder.co.uk [82.32.29.13]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD2C743F3F for ; Sat, 13 Sep 2003 03:37:55 -0700 (PDT) (envelope-from matt@xtaz.co.uk) Received: from xtaz.co.uk (heather [10.0.0.2]) by holly.xtaz.co.uk (Postfix) with ESMTP id 7C7EC8FC18 for ; Sat, 13 Sep 2003 11:37:54 +0100 (BST) Message-ID: <3F62F382.3000800@xtaz.co.uk> Date: Sat, 13 Sep 2003 11:37:54 +0100 From: Matt User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20030913 X-Accept-Language: en-us, en MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: mysql-client compiler error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2003 10:37:57 -0000 After building world as of late last night I decided to portupgrade -rRaf, mainly due to having the libintl.so.4 missing problem when I tried to start X. Everything compiled perfectly fine (and X is now working fine) except for databases/mysql40-client. I get this error: checking for C compiler default output... configure: error: C compiler cannot create executables configure: error: could not configure Berkeley DB I just wish to know is this something wrong with my system in general or is this just due to the -pthread discussions that have been occuring and that this port is one example of those that no longer works on -current? It is not a problem as I have the previously compiled/installed version still on the system but I just wish to confirm if the problem is likely to be down to the pthreads changes, and if I should report it to the port maintainer etc? Matt.