From owner-freebsd-ports@FreeBSD.ORG Sun May 30 13:53:58 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5D40A1065673; Sun, 30 May 2010 13:53:58 +0000 (UTC) (envelope-from erik@cederstrand.dk) Received: from csmtp2.one.com (csmtp2.one.com [91.198.169.22]) by mx1.freebsd.org (Postfix) with ESMTP id EB40C8FC08; Sun, 30 May 2010 13:53:57 +0000 (UTC) Received: from macfeast.lan (0x573b9942.cpe.ge-1-2-0-1101.ronqu1.customer.tele.dk [87.59.153.66]) by csmtp2.one.com (Postfix) with ESMTP id 085F91B013C7D; Sun, 30 May 2010 13:36:46 +0000 (UTC) Mime-Version: 1.0 (Apple Message framework v1078) Content-Type: multipart/signed; boundary=Apple-Mail-149-566662397; protocol="application/pkcs7-signature"; micalg=sha1 From: Erik Cederstrand In-Reply-To: Date: Sun, 30 May 2010 15:36:45 +0200 Message-Id: <45C1FA95-C9A3-41EA-9E3A-61E35C7F6AD1@cederstrand.dk> References: <4BDD28E2.8010201@rawbw.com> To: =?utf-8?Q?Andrius_Mork=C5=ABnas?= X-Mailer: Apple Mail (2.1078) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-hackers@freebsd.org, freebsd-ports@freebsd.org Subject: Re: GSoC: Making ports work with clang X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 May 2010 13:53:58 -0000 --Apple-Mail-149-566662397 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Den 30/05/2010 kl. 14.51 skrev Andrius Mork=C5=ABnas: > On Sun, 30 May 2010 14:58:05 +0300, Volodymyr Kostyrko = wrote: >> 1. __dso not found after link. Some symbols seems to be omitted from >> libraries and linking of plugins fails badly. > Known problem with known fix. >=20 >> 2. Assembler errors. Xorg has some in x11-servers/xorg-server >> x11-drivers/xf86-video-vesa x11-drivers/xf86-video-ati, everything = else >> compiles and works. > Assembler errors often aren't similar to each other, so fixing them = may > be very easy or difficult. Hopefully we will fix them for big stuff = like > xorg (not really as part of this GSoC project). >=20 >> 3. Big bunch of compile errors or config errors. This means = incorrectly >> written code, like not correctly declaring variables. This also means >> some automake stupidities like testing c++ compiler with c style code = - >> for example clang++ refuses to compile "int main(void) {}". > $ cat main.cc > int main(void) {} > $ clang main.cc -o test && ./test && echo "No, it works." > No, it works. >=20 > Other than that, yes, many problems are related to insane configure > scripts. >=20 >> 4. Some ports specify that thay need at least gcc 3.3. > This is another of those insane configure scripts, testing for = specific > version of specific compiler, rather than testing if it can compile > anything. >=20 >> 5. Some ports needs --dumpspecs. > It's a bit uglier than "some ports": > $ grep dumpspecs /usr/ports/Mk/bsd.gecko.mk > GECKO_PTHREAD_LIBS!=3D${CC} -dumpspecs | ${GREP} -m 1 pthread: | = ${SED} -e 's|^.*%{\!pg: %{pthread:|| ; s|}.*$$||' || ${TRUE} >=20 >> audio/libmad - distorted sound >> lang/python26 - compiling any gir dumps core >> textproc/expat2 - dbus dumps core at launch > Python and expat shout i386 in my face, clang/llvm tends to not like > i386 too much. But I think few miscompilations were fixed recently, > so some of these may already be working fine. >=20 >> And this all data is not current. It's one month old. Since then >> dumpspecs was implemented. And maybe some other problems begone - I = just >> have not enough time to look at this thoroughly. > Some problems from a month ago are definitely gone, but I don't think > dumpspecs is one of them. Andrius, would it make sense to create e.g. a wiki page tracking the = status and current known problems with compiling ports with clang? Just = like there's a wiki page ClangBSD status. I think it would make it easier for lurkers to jump in and test things, = and help whittle away at the problems. Thanks, Erik= --Apple-Mail-149-566662397--