From owner-freebsd-chromium@FreeBSD.ORG Fri Apr 6 09:18:22 2012 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 43184106564A for ; Fri, 6 Apr 2012 09:18:22 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id BBF008FC08 for ; Fri, 6 Apr 2012 09:18:21 +0000 (UTC) Received: by bkcjc3 with SMTP id jc3so2445628bkc.13 for ; Fri, 06 Apr 2012 02:18:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nuYCoJVyppdhZ/wYSVt7mgWw8eK79dniuz1zRhfzJbw=; b=snYR2MQIyoCdHvmTzg/SG4KhGubdac6U2N6fUfNrWpnG4hla1Vlv6/XArs8CCmaSQX YxJwyt/pJPbHGbEum/FeIj0ITLA3StEEYVGg2StU8lKGjnhcxGxNTuuMtsXNGv3wlzJm sHyuA1Pyg4q8jDhTz14HnyMwz3pdN82CwujEoF34Ox6XUjVdWP/xzoE2+mTXd5pZaBIq Q7eu9UERdF2MSsZPJZUaHwlhk5hXuamjtZGmK7isNi+LiZF+MZ5epk2uVtmvxXQJv2dj qYY6IAsSZDU9qfOn/QTvSl2ILtINalcOsxlFhI59N+r8hn2OBzlPXTV96bEwJWRi3rFi 4Tsg== MIME-Version: 1.0 Received: by 10.205.136.12 with SMTP id ii12mr2618182bkc.98.1333703900364; Fri, 06 Apr 2012 02:18:20 -0700 (PDT) Sender: r.c.ladan@gmail.com Received: by 10.204.42.3 with HTTP; Fri, 6 Apr 2012 02:18:20 -0700 (PDT) In-Reply-To: <20120406090549.GP13705@e-new.0x20.net> References: <20120318201109.GA23354@e-new.0x20.net> <4F796427.1020408@delphij.net> <20120406090549.GP13705@e-new.0x20.net> Date: Fri, 6 Apr 2012 11:18:20 +0200 X-Google-Sender-Auth: s98BrUCPyzTQeOE_ZjbVuavQpLU Message-ID: From: =?ISO-8859-1?Q?Ren=E9_Ladan?= To: Lars Engels Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: chromium@freebsd.org, d@delphij.net Subject: Re: Chromium build fails on Current (r233121) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Apr 2012 09:18:22 -0000 2012/4/6 Lars Engels : > On Mon, Apr 02, 2012 at 10:46:23AM +0200, Ren=E9 Ladan wrote: >> 2012/4/2 Xin Li : >> > On 03/18/12 13:11, Lars Engels wrote: >> >> Build of Chromium 17.0.963.79 fails to build on r233121, amd64: >> >> >> >> CXX(target) >> >> out/Release/obj.target/webkit_gpu/webkit/gpu/webgraphicscontext3d_in_= process_impl.o >> >> >> >> >> > LINK(host) out/Release/protoc >> >> AR(host) out/Release/obj.host/v8/tools/gyp/libv8_nosnapshot.a RULE >> >> sync_proto_genproto_0 >> >> out/Release/pyproto/chrome/browser/sync/protocol/sync_pb2.py gmake: >> >> *** [out/Release/pyproto/chrome/browser/sync/protocol/sync_pb2.py] >> >> Floating point exception: 8 (core dumped) gmake: *** Waiting for >> >> unfinished jobs.... *** [do-build] Error code 1 >> >> >> >> Stop in /usr/ports/www/chromium. *** [build] Error code 1 >> > >> > Hit the same thing and compiling with GCC46 either works around it, or >> > fixed the problem. =A0Haven't investigated the underlying issue though= . >> > >> Fixed probably, chromium also builds with top-of-tree clang (from upstre= am) with >> http://trillian.chruetertee.ch/chromium/changeset/318 applied. > > Unfortunately it's still not fixed for me. Building with CLANG: > > =A0LINK(host) out/Release/protoc > =A0LINK(host) out/Release/protoc: Finished > =A0AR(host) out/Release/obj.host/v8/tools/gyp/libv8_nosnapshot.a > =A0RULE sync_proto_genproto_0 > out/Release/pyproto/chrome/browser/sync/protocol/app_notification_specifi= cs_pb2.py > gmake: *** > [out/Release/pyproto/chrome/browser/sync/protocol/app_notification_specif= ics_pb2.py] > Floating point exception: 8 (core dumped) > > # clang -v > FreeBSD clang version 3.0 (tags/RELEASE_30/final 145349) 20111210 > Target: x86_64-unknown-freebsd10.0 > Thread model: posix > Your clang is probably too old, clang/llvm from upstream trunk worked for = me. The clang in base contains a bug which miscompiles protoc resulting in the SIGFPE even with the patch added in the last commit. Ren=E9