From owner-freebsd-chromium@FreeBSD.ORG Tue Jun 5 00:12:40 2012 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6D0BA1065672; Tue, 5 Jun 2012 00:12:40 +0000 (UTC) (envelope-from illoai@gmail.com) Received: from mail-qa0-f49.google.com (mail-qa0-f49.google.com [209.85.216.49]) by mx1.freebsd.org (Postfix) with ESMTP id 12AA78FC0A; Tue, 5 Jun 2012 00:12:39 +0000 (UTC) Received: by qabj40 with SMTP id j40so2289042qab.15 for ; Mon, 04 Jun 2012 17:12:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Bvg8MT2bM7PI9kkN367nvC0PY1gUcS8IXT9cHfhBEsI=; b=sFvusZPIErsX3V+NXz/fTuxMtWNlQsEKsAyxkZM4GLN88gWRkODBZPP2OnmHg13ng2 hZesS6QWHi3lqlBV4OTebFDiXarN9/bjZZfvDOuS4/ztQoEPfE/IH2yM0GIcbzy+/y4d XxR8dyFqa4yOgEDIjoKBdBfDwdUlJRW2FfWSszKKiDHXRyFbLcmsTa1Janzr9+KFr0ug 4Y6+/kywC8oFRGe0b/40ql76E69qjO0/j5lDQ+4Up2EMcsUKOnUdsA7tncHKtNklLYuj V+5xz/TndPVg+9fs14lQhpL299vvgdwiiKPX/Hlo51ijSx6VDPwnUwNEORYFOwsMCtHA ri2Q== MIME-Version: 1.0 Received: by 10.224.181.83 with SMTP id bx19mr14981417qab.79.1338855159331; Mon, 04 Jun 2012 17:12:39 -0700 (PDT) Received: by 10.229.40.138 with HTTP; Mon, 4 Jun 2012 17:12:39 -0700 (PDT) In-Reply-To: <4FCB91CC.7060502@rawbw.com> References: <20120530143824.GA18299@aurora.oekb.co.at> <44txyxfx1q.fsf@lowell-desk.lan> <4FCB91CC.7060502@rawbw.com> Date: Mon, 4 Jun 2012 20:12:39 -0400 Message-ID: From: "illoai@gmail.com" To: Yuri Content-Type: text/plain; charset=ISO-8859-1 Cc: Lowell Gilbert , questions@freebsd.org, Ewald Jenisch , chromium@freebsd.org Subject: Re: Chromium - fails to compile 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: Tue, 05 Jun 2012 00:12:40 -0000 On 3 June 2012 12:33, Yuri wrote: > On 05/30/2012 09:33, Lowell Gilbert wrote: >> >> Yes. Chromium currently depends on SSE3; the recommended way of enabling >> that appears to be setting CPUTYPE. > > > Port should be ding that itself. > Make use of misc/cpuid if needed. Make it BUILDDEP. > > Currently 19.0.1084.52 fails to build for me too. > Doesn't seem to matter what CPUTYPE is, but adding -mssse3 to CFLAGS let it finish. But the whole linux fiasco with chromium depending on udev is making me not want to use it. -- --