From owner-freebsd-current@FreeBSD.ORG Sun Feb 26 12:56:19 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mandree.no-ip.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by hub.freebsd.org (Postfix) with ESMTP id 9EF0D106577F for ; Sun, 26 Feb 2012 12:56:19 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by apollo.emma.line.org (Postfix) with ESMTP id BD51323D05E for ; Sun, 26 Feb 2012 13:56:18 +0100 (CET) Message-ID: <4F4A2BF2.8030408@FreeBSD.org> Date: Sun, 26 Feb 2012 13:56:18 +0100 From: Matthias Andree User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.27) Gecko/20120216 Mnenhy/0.8.3 Thunderbird/3.1.19 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4F462189.3040106@mail.zedat.fu-berlin.de> In-Reply-To: <4F462189.3040106@mail.zedat.fu-berlin.de> X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: No working IDE in FreeBSD! X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 26 Feb 2012 12:56:19 -0000 Am 23.02.2012 12:22, schrieb O. Hartmann: > Several time ago I tried to do some development within an IDE, not even > for lectural and educational purposes. Since most of our software is > written in C/C++ and OpenCL, I highly prefered ANJUTA, since this IDE > was highly customizable, flexible and even FreeBSD's ancient outdated > version in the ports suited our needs. > > Anjuta does not compile anymore for a long time. I do not know why, I > filed a PR (ports/161494). So I was looking for an alternative. Anjuta compiles fine for me on 9-STABLE with GCC, but I can reproduce the build failure with clang that you've filed there. The following lines were also posted as bug-followup: ----------------------------------------------------------- (Note I'm not a member of the gnome@ team.) While I can reproduce the build failure with clang (possibly related to the "not portable" warnings your're seeing), building anjuta with gcc works fine for me. Can you post the command lines and relevant configuration files (like make.conf) that you've used to attempt a build with GCC? Chances are you haven't thoroughly switched to GCC. For me, using portmaster's -m option wouldn't work. Note that you can pass V=1 as make argument to get the full compiler command lines, rather than the short "CC" "CCLD" lines, to see what's actually happening. ----------------------------------------------------------- Please check the lines above. The relevant lines from the PR seem to be: ----------------------------------------------------------- *** Warning: Linking the executable benchmark against the loadable module *** libanjuta-symbol-db.so is not portable! ./../.libs/libanjuta-symbol-db.so: undefined reference to `sdb_engine_get_statement_by_query_id' ./../.libs/libanjuta-symbol-db.so: undefined reference to `sdb_engine_get_tuple_id_by_unique_name' clang: error: linker command failed with exit code 1 (use -v to see invocation) gmake[6]: *** [benchmark] Error 1 ----------------------------------------------------------- Chances are that these are genuine bugs in the Anjuta build system.