From owner-freebsd-chromium@FreeBSD.ORG Mon Nov 17 01:17:18 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53524492 for ; Mon, 17 Nov 2014 01:17:18 +0000 (UTC) Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0C7D13CE for ; Mon, 17 Nov 2014 01:17:18 +0000 (UTC) Received: by mail-qg0-f46.google.com with SMTP id i50so14241239qgf.19 for ; Sun, 16 Nov 2014 17:17:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=qA/gqftAOZlhAEjU0seW3fExFS6Ec8W7Lt5Y1krrzx4=; b=XfhuFRWcO589ald8rFgE7e93mwNEYc3Z2vJRqFXIzdgsM0cqs2qCXHqK1Yct9Ym5jJ sx9sLXSfRfFfJgSuV0nAdQqN7WkxDE1vCj71It0NzdRnEHlow43XYIvmOiv1fLBUk6AX l+cbZlfFpd2PKw3saHhX/b/vM+pFCmCvuxAiEVZTO5pZE8NNIlrJPfFpBwbUgtYhq/E/ K8h907QX39W2DUiMKRDUxV1yV+wJ7nzU4Z84crAdD/9uEH3Gg/G3egDzb6P5lLATF9cY zr+WS1u+Dnfc+/MGDlHGtxoe0gIABxEknrwu9EjKmFhlxIulyDUmxWHncCcycHK4xH4b ZTFw== X-Received: by 10.140.37.71 with SMTP id q65mr29526656qgq.42.1416187037247; Sun, 16 Nov 2014 17:17:17 -0800 (PST) Received: from [192.168.1.34] ([201.230.228.147]) by mx.google.com with ESMTPSA id a97sm33007437qge.13.2014.11.16.17.17.15 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 16 Nov 2014 17:17:16 -0800 (PST) Message-ID: <54694C9A.2010204@gmail.com> Date: Sun, 16 Nov 2014 20:17:14 -0500 From: Eddy Ravello User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: chromium@FreeBSD.org Subject: www/chromium port question Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2014 01:17:18 -0000 -----------\nPBI Information:\nPort: www/chromium\nName: Chromium\nDate Installed: 16/11/14 17:22\nVersion: 38.0.2125.104_1\nArchitecture: 10-64bit From owner-freebsd-chromium@FreeBSD.ORG Mon Nov 17 03:23:51 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ADC7EDF9 for ; Mon, 17 Nov 2014 03:23:51 +0000 (UTC) Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 815B21B8 for ; Mon, 17 Nov 2014 03:23:51 +0000 (UTC) Received: by mail-oi0-f53.google.com with SMTP id x69so318450oia.26 for ; Sun, 16 Nov 2014 19:23:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=2F67SVwVyyNS05NWeOZRLP6U1b/Q7KGcTdRsgREvGhE=; b=vI9VxZx/+TayMAzT0N+v6nYIp3j+xDEWibV1vaNhKwNOFOxuR1SWENkshtpAEHI9A2 VYUo4/UxudmgVOC6gWkto/NnzxV/g9CxyEsLlyuYjiMceAjq9gSCsgaZJf3xU1ycnM6g t5+nnYecgR4KTOJesafKBrli086gehEoBQ/j8n5/Lpn4hMnEwZsnzTrsxe0eqwv3HmHd iA6UhUoh9G2wMS7SHXGrdxu979U6B9Wec69MWseMwlnAfY3VIExI5Ae7iUYHJF8z3BaZ p2BY8Yx8jfnQjppIkHxi40yL664RpH381wZP+pDPou0L/y18F//5VLsWyKv9cA4e8pde +oxQ== X-Received: by 10.182.165.36 with SMTP id yv4mr5246634obb.39.1416194630587; Sun, 16 Nov 2014 19:23:50 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.101.198 with HTTP; Sun, 16 Nov 2014 19:23:30 -0800 (PST) In-Reply-To: References: From: Fervent Dissent Date: Mon, 17 Nov 2014 11:23:30 +0800 Message-ID: Subject: Re: chromium-38.0.2125.111 and flashplugin To: =?UTF-8?B?0JLQu9Cw0LTQuNC80LjRgCDQotC40LzQvtGE0LjQtdCy?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: base64 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2014 03:23:51 -0000 aHR0cDovL3d3dy5mcmVzaHBvcnRzLm9yZy93d3cvbGludXgtZjEwLWZsYXNocGx1Z2luMTEvDQps aW51eF9iYXNlDQpuc3BsdWdpbndyYXBwZXINCg0KbnNwbHVnaW53cmFwcGVyIC1pIC1hDQoNCnRo aXMgaXMgZ29vZCBmb3IgZmlyZWZveCBhbmQgY2hyb21pdW0NCg0KMjAxNC0xMS0xNSAxOjIyIEdN VCswODowMCDQktC70LDQtNC40LzQuNGAINCi0LjQvNC+0YTQuNC10LIgPGVsaW1lbGVjaDAwN0Bn bWFpbC5jb20+Og0KDQo+IEhvdyBkbyBJIGdldCB0aGUgZmxhc2ggcGx1Z2luIHRvIGEgbmV3IHZl cnNpb24gb2YgdGhlIGJyb3dzZXI/DQo+DQo+IC0tDQo+DQo+INCW0LXQu9Cw0Y4g0LLQsNC8INC/ 0L7QtNC00LXRgNC20LrQuCDQodCy0YvRiNC1INC4INGD0YHQv9C10YXQsC4NCj4g0JfQsNC50YIg 0LPQuNC30YPQvdGCISDQmCDQsdGD0LTRjNGC0LUg0LzQvdC1INC30LTQvtGA0L7QstGLIQ0KPg0K PiDQoSDRg9Cy0LDQttC10L3QuNC10LwsIC0NCj4g0JLQsNGIINCi0LjQvNC+0YTQuNC10LIg0JLQ u9Cw0LTQuNC80LjRgCA8aHR0cDovL2NvcGkucnUvOTQ3MTc+DQo+IF9fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IGZyZWVic2QtY2hyb21pdW1AZnJlZWJz ZC5vcmcgbWFpbGluZyBsaXN0DQo+IGh0dHA6Ly9saXN0cy5mcmVlYnNkLm9yZy9tYWlsbWFuL2xp c3RpbmZvL2ZyZWVic2QtY2hyb21pdW0NCj4gVG8gdW5zdWJzY3JpYmUsIHNlbmQgYW55IG1haWwg dG8gImZyZWVic2QtY2hyb21pdW0tdW5zdWJzY3JpYmVAZnJlZWJzZC5vcmcNCj4gIg0K From owner-freebsd-chromium@FreeBSD.ORG Mon Nov 17 12:23:45 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4A6E8556 for ; Mon, 17 Nov 2014 12:23:45 +0000 (UTC) Received: from mail.0x20.net (mail.0x20.net [217.69.76.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 03792D0B for ; Mon, 17 Nov 2014 12:23:44 +0000 (UTC) Received: from e-new.0x20.net (mail.0x20.net [IPv6:2001:aa8:fffb:1::3]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.0x20.net (Postfix) with ESMTPS id EE5476A6002; Mon, 17 Nov 2014 13:23:41 +0100 (CET) Received: from e-new.0x20.net (localhost [127.0.0.1]) by e-new.0x20.net (8.14.7/8.14.7) with ESMTP id sAHCNfta046630; Mon, 17 Nov 2014 13:23:41 +0100 (CET) (envelope-from lars@e-new.0x20.net) Received: (from lars@localhost) by e-new.0x20.net (8.14.7/8.14.7/Submit) id sAHCNf7p046549; Mon, 17 Nov 2014 13:23:41 +0100 (CET) (envelope-from lars) Date: Mon, 17 Nov 2014 13:23:41 +0100 From: Lars Engels To: Fervent Dissent Subject: Re: chromium-38.0.2125.111 and flashplugin Message-ID: <20141117122341.GW34846@e-new.0x20.net> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="xi8lRpXYeGgNnUjs" Content-Disposition: inline In-Reply-To: X-Editor: VIM - Vi IMproved 7.4 X-Operation-System: FreeBSD 8.4-RELEASE-p16 User-Agent: Mutt/1.5.23 (2014-03-12) Cc: =?utf-8?B?0JLQu9Cw0LTQuNC80LjRgCDQotC40LzQvtGE0LjQtdCy?= , chromium@freebsd.org X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Nov 2014 12:23:45 -0000 --xi8lRpXYeGgNnUjs Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 17, 2014 at 11:23:30AM +0800, Fervent Dissent wrote: > http://www.freshports.org/www/linux-f10-flashplugin11/ > linux_base > nspluginwrapper >=20 > nspluginwrapper -i -a >=20 > this is good for firefox and chromium Nope, newer versions of chromium no longer support NPAPI plugins. --xi8lRpXYeGgNnUjs Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJUaejNXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RjQwMDE3RTRERjUzMTI1N0FGRTUxNDlF NTRDQjM3RDNBMDg5RDZEAAoJEOVMs306CJ1t59YH/23rxITKsWlvMb4QTISh6BC2 tzNGJH8GlOUSXccR65+7vi67ZT676X2LyXDXejZotKqn5XALw+FiHtxUUGjc8YLK ysOjxcma7Pp+U/MuUc+UPpMfdF1Zx82Bi87XZwOkMGm6H/rAGb65JKNPNruTz1/a /p83D275jemmwevt9v04SR40NBG3Ikg7iQJwg5axyvDCevIRwgCbzzEV5WLCqknf 4Bw9WDG5oFv2QhtERN7lqyS9/FU5UH/hGyEh2jFpyfoMS8x1T8wlRrZGGsspaqjX 8ovuBK7RwDayZhxSev0yFqQ5V8v+A/AHryu/gkck4rwfHZv7eepoCKWaTANIkyM= =8zJY -----END PGP SIGNATURE----- --xi8lRpXYeGgNnUjs-- From owner-freebsd-chromium@FreeBSD.ORG Wed Nov 19 12:01:41 2014 Return-Path: Delivered-To: chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 764A37AE for ; Wed, 19 Nov 2014 12:01:41 +0000 (UTC) Received: from smtp202.alice.it (smtp202.alice.it [82.57.200.98]) by mx1.freebsd.org (Postfix) with ESMTP id 399E7C32 for ; Wed, 19 Nov 2014 12:01:41 +0000 (UTC) Received: from alice.it (14.139.186.178) by smtp202.alice.it (8.6.060.43) (authenticated as ale.mir@alice.it) id 5433A8A30983DEC8 for chromium@freebsd.org; Wed, 19 Nov 2014 13:01:39 +0100 From: "Dennis & Cherri Ward" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: from: Dennis & Cherri Ward Message-Id: <4583179B-AAF2-4563-C219-86CAC617E919@alice.it> Date: Wed, 19 Nov 2014 13:01:36 +0100 To: "chromium@freebsd.org" X-Mailer: iPhone Mail (8B117) X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2014 12:01:41 -0000 Hi http://stilbg.ru/carried.php?well=3D6pgucnucf0v12m daward7841@att.net Sent from my iPhone From owner-freebsd-chromium@FreeBSD.ORG Wed Nov 19 14:53:04 2014 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4ED50A18 for ; Wed, 19 Nov 2014 14:53:04 +0000 (UTC) Received: from mail-lb0-x244.google.com (mail-lb0-x244.google.com [IPv6:2a00:1450:4010:c04::244]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C6B5E15C for ; Wed, 19 Nov 2014 14:53:03 +0000 (UTC) Received: by mail-lb0-f196.google.com with SMTP id f15so125466lbj.7 for ; Wed, 19 Nov 2014 06:53:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=JuK1AQzlGJzkjKcKFbcp6SSzPe1c8E75VGA+6ODe0mc=; b=wKezmZu5mHlzPdXQVHtsu8aMbM7QAwLlJ2ssmY+0YpdrIEYVHvw6AuZHR/AOxe5eRZ lYkqMW+sAgf9kltPfB4LtQKxdpvVodGJ8WS+pit2vc3hyEOqvX6w26SH3z3K6G137Dss zSnQee9kqG4hXjx1AEXYcQF/qs3NVQcF1MvYHQevbZrr/g2Y/2qf3vCaYslck2XJ6JkE W7iCZhbbL78PmYKc9cHmhY57jtfyPgoLceinj9tAktdkb5krb9eul/XfySVNtYWjBPs3 ZCUxeHoDkg8i0Qf5oyooaJMjXjJUp0E3VsEn+jcUrAu4zBLQPvh00Myi/zXaI36aRIzh fU6w== MIME-Version: 1.0 X-Received: by 10.112.168.97 with SMTP id zv1mr43039392lbb.6.1416408781804; Wed, 19 Nov 2014 06:53:01 -0800 (PST) Received: by 10.114.232.103 with HTTP; Wed, 19 Nov 2014 06:53:01 -0800 (PST) Received: by 10.114.232.103 with HTTP; Wed, 19 Nov 2014 06:53:01 -0800 (PST) Date: Wed, 19 Nov 2014 06:53:01 -0800 Message-ID: Subject: FreeBSD Port: www/chromium From: maria chavez To: chromium@FreeBSD.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Nov 2014 14:53:04 -0000 From owner-freebsd-chromium@FreeBSD.ORG Thu Nov 20 23:01:18 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D9B002EC for ; Thu, 20 Nov 2014 23:01:17 +0000 (UTC) Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5D930C09 for ; Thu, 20 Nov 2014 23:01:17 +0000 (UTC) Received: by mail-wg0-f48.google.com with SMTP id y19so5048356wgg.35 for ; Thu, 20 Nov 2014 15:01:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=Ml0T9B+gzW36/mV/3qGQrneHX/u0PXvMSUwLl11+in4=; b=K1N7UYqOADYhsxTX8hd+p41kfPnltb1Jr153WudNPDtgVQBs0RQRk5WslZZWaEJRwq pNOywkFqxaXVz7wK++C3T28pviVobYADlZcuRYhgVM05POzx+yRSExtxBCagYrRoz3Px X2chy0P6BYvV3maV6jgDNdABs1qbHRwi6kf7gpUDrqvK4VZKrRlaghZJ3/jWscTmNHSc NT2IVR+B4Rh1FNSZWPm7nwHI0JJTFRSbFGb0Ndyw678MUONFhaOmPIOuYB60Y+oqxZh6 qx9FeV5PuNixNJm/WzNydOe0riX75YMnqyHbas1/By9LjFN3yjuMGYjEqfKVPoVojIKu K99g== X-Received: by 10.180.218.133 with SMTP id pg5mr2100165wic.70.1416524475293; Thu, 20 Nov 2014 15:01:15 -0800 (PST) Received: from ?IPv6:2001:980:d7ed:1:b4ec:e001:49fe:edd1? ([2001:980:d7ed:1:b4ec:e001:49fe:edd1]) by mx.google.com with ESMTPSA id wl1sm5414248wjb.4.2014.11.20.15.01.14 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Nov 2014 15:01:14 -0800 (PST) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <546E72B9.60700@freebsd.org> Date: Fri, 21 Nov 2014 00:01:13 +0100 From: =?UTF-8?B?UmVuw6kgTGFkYW4=?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: chromium-list freebsd Subject: backing down on Chromium ... Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Nov 2014 23:01:18 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello all, after already four years I decided to back down somewhat on Chromium. This is not an overnight decision, the feeling started creeping in several months ago. One reason is that maintaining Chromium all the way on FreeBSD would seriously be a good candidate for a full-time job: - keep the existing patches working, they need to be checked and possibly rewritten on every major release - polishing patches for upstream and tickling the upstream bots - hunting down incompatibilities. This is mostly caused FreeBSD masquerading as Linux and consequently Chromium assumes that e.g. /proc is populated as on Linux. - writing missing code for FreeBSD, including but not limited to: - low-level network stuff - fcvt(3) - obtaining hard disk drive serial number for the Google Music (if I understand correctly) - obtaining detailed memory usage, proper GPU porting - keeping the GitHub and ports version in sync - writing VuXML entries once in a while Also, other things seem more interesting (e.g. FreeBSD documentation or other ports), and sometimes I felt more like being a Chromium than a FreeBSD developer. This does mean that *you* will have to continue, but I (boldly) think there is enough interest for it. This should hopefully get you started: - - As you might know, we have an work-in-progress repository on GitHub: https://github.com/gliaskos/freebsd-chromium/ - - Patches are available in the Ports Tree and on GitHub. There are also experimental patches against the top-of-tree (like FreeBSD-CURRENT) at https://people.freebsd.org/~rene/chromium/ - - The latter location also contains a script to generate the patches (gen-diff.sh) and a script to try to build chromium in a chroot (update.sh). It also contains a list of required packages (pkg-list). Note that libxml2 and yasm can go once the bundled versions work. - - Minor version updates are mostly a matter of running `make makesum` and checking if the pkg-plist is still OK. See below for major version updates. - - Notice that new upstream distribution files can take a day to appear, even in the case of a security update. Porting a new major version (for GitHub or the Ports Tree) is a different story though: - - Checkout the beta branch at GitHub - - Bump the PORTVERSION, run `make makesum` - - Run `make checkpatch` to see which patches still apply. Temporarily move Broken / orphaned patches out of the way. Repeat till `make checkpatch` is fine. - - Fix or delete the patches you just moved - - Try to build the port. Have coffee, brain, and willpower ready... - - If `make configure` fails, this is mostly because gyp is complaining. In case a directory got accidentally deleted by the remove_bundled_libraries.py script, put it back in, add it to its list, and try again. - - In case you need inspiration for a patch, try to look at the corresponding Linux or MacOSX code. A lot of times adding BSD to the list suffices. - - Once Chromium links and staging passes, run `make check-plist` and `make package` to see if the package list is still OK. - - Try to run it. - - Once that works, you can send the patches using a PR, a website, or otherwise. - - Every six weeks or so the Beta version gets Stable, which means it is time to merge the beta branch back into the master branch. - - To get the patch for the Ports Tree, replace the old files/ directory with the new one, and update Makefile, pkg-*, and distinfo In case you feel like working with upstream: - - See the WWW site for some hints on getting started - - Have a modern machine ready (many cores, RAM, ZFS, ccache) - - Check upstream on how to get the sources (chroot highly recommended to not pollute your existing system). Notice that the initial checkout can is between 10 GB and 15 GB large. - - Apply the patches from https://people.freebsd.org/~rene/chromium/ - - Run the script to try to build Chromium: sh ./update.sh build nopull Even more coffee, brain, and willpower recommended. - - To update from upstream, run: sh ./update.sh and check for merge conflicts in the git output. Resources: - - https://googlechromereleases.blogspot.com/ - - chromium-dev@chromium.org - - chromium-packagers@chromium.org - - #chromium on FreeNode For now I will continue to: - - Committing VuXML entries - - Committing new versions to the Ports Tree (e.g. as PR) and to GitHub. Feel free to fork the repository. - - Answer any questions you have. Do mind that (at least in my experience), interest from upstream in BSD varies. There might eventually be BSD bots, but that doesn't necessarily mean that build errors on BSD will be blocking (as they are on Windows / Linux / MacOSX / Android / iOS). A good person to contact would be Pawel Hajdan Jr Regards, René -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUbnK4XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMDFBNzE2QjE2MkIwMEU1NUJFREVBMDVB REJCRjg2MTBBMzc4OUI3AAoJEK27+GEKN4m3vY0P/jdG4W4vvVFquJ9SzKJwhCd3 rOrioQBmMolKiXMS9kdQbwwAf2pskK1VDi0+1fGimN4EIlVI8FO2+ORKQ/72u+0M ZDLz9Aml29TgjiLWzuvFTXQq9siKKVVx6yszetWCDjkdsmEIBKyz3sSFM+yNTyNu xmRydxomvl4FNcFMYtI4+nH5LxIIkntbCkJY/6niaDDVMl7jTJmvzcztOh4Q3eff kkhTdYGmd1s3ZbqKhawaHXfN2Gs2UrZR/kLEyYxM0AuURNOYEoORenWTUa0LloX7 Nk5CBSpX/oQj6Pk9BFOzgcgThd2iIY2qz2ALaibFDLUgsRqor2d6O3zLH93jvqNY zrasSrL4xIukvGv//e1sG51kOuyrR4ozmBiCSDd3jKM+OfSf/9kPIOaX7BQS4Ihm VwrMYaONES9B23IAixFoeosaOemcM17RFIb4w7lrDCSsWVB9zHct/Y/GHiGpgbBS xokTSB+Q1BMm86bBgux/v52Hr/14K5hFXfb8dWq2oZ8+JPxoS9ztMvEij+yfoJcs GulquJsMj9irZEHEasC0PgC7DdTBAfUO1gHhT/Meai4mJFuBLjaHcTlHxwqnOn44 flIPAnG98aqReCqArHxTsZ5poainP+oX0jnmEHnxsVOZL1Eb1APnWQ23nNN/Oawq 0SQjf164vBJOTWJ1QR59 =fZZc -----END PGP SIGNATURE----- From owner-freebsd-chromium@FreeBSD.ORG Thu Nov 20 23:14:05 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B442712; Thu, 20 Nov 2014 23:14:05 +0000 (UTC) Received: from mail-qa0-x231.google.com (mail-qa0-x231.google.com [IPv6:2607:f8b0:400d:c00::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1D2B1D2F; Thu, 20 Nov 2014 23:14:05 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id s7so2667123qap.36 for ; Thu, 20 Nov 2014 15:14:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=NEGeBxemkkjx8iJlqNcadJrRmOvo7X1uE7dLtynr50U=; b=XLELPLy/M/iMzrbfauj292h+RKdaX2z00jFSVLhUp4dUJ0o6ozRxvQk/u/aLSBKe57 MFOu9bEii4jtt1dXiNnAEBqKSr52lSAiocCnY7lW1h+9Asu5FKt7TI1/OgFVu283olYu SFd0Go6HyExRWvKR7SCKB+QwolLB1tKB/QNjyoPBaE4egcxmfNZ/FjfoNKFx+mBhl8JG xdlSqacroc3NiPMcjbImuPK4xLxusiRCL4nFNXVIvIMY0UOa2PdcIxTmY7+k0ai6PmP3 IBCqK7l2pMtv+VRapB8v+UTFkmrGM5AAzvmuXseSKYZntRBwFBIQgqew64Z83eMLOGBW zYCQ== X-Received: by 10.140.31.35 with SMTP id e32mr1574609qge.4.1416525244265; Thu, 20 Nov 2014 15:14:04 -0800 (PST) Received: from [10.3.4.126] ([64.214.53.64]) by mx.google.com with ESMTPSA id o9sm3186955qay.48.2014.11.20.15.14.03 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Nov 2014 15:14:03 -0800 (PST) Content-Type: multipart/signed; boundary="Apple-Mail=_7E422C50-6C7C-426A-8C1F-51E00C0DA013"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: backing down on Chromium ... From: Shawn Webb In-Reply-To: <546E72B9.60700@freebsd.org> Date: Thu, 20 Nov 2014 18:13:58 -0500 Message-Id: <8A50107E-55F9-4AD1-981A-5A52DDB5DC0A@gmail.com> References: <546E72B9.60700@freebsd.org> To: =?iso-8859-1?Q?Ren=E9_Ladan?= X-Mailer: Apple Mail (2.1878.6) Cc: chromium-list freebsd X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Nov 2014 23:14:05 -0000 --Apple-Mail=_7E422C50-6C7C-426A-8C1F-51E00C0DA013 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Nov 20, 2014, at 6:01 PM, Ren=E9 Ladan wrote: > Signed PGP part > Hello all, >=20 > after already four years I decided to back down somewhat on Chromium. > This is not an overnight decision, the feeling started creeping in > several months ago. >=20 > One reason is that maintaining Chromium all the way on FreeBSD would > seriously be a good candidate for a full-time job: > - keep the existing patches working, they need to be checked and > possibly rewritten on every major release > - polishing patches for upstream and tickling the upstream bots > - hunting down incompatibilities. This is mostly caused FreeBSD > masquerading as Linux and consequently Chromium assumes that e.g. > /proc is populated as on Linux. > - writing missing code for FreeBSD, including but not limited to: > - low-level network stuff > - fcvt(3) > - obtaining hard disk drive serial number for the Google Music (if > I understand correctly) > - obtaining detailed memory usage, proper GPU porting > - keeping the GitHub and ports version in sync > - writing VuXML entries once in a while > Also, other things seem more interesting (e.g. FreeBSD documentation = or > other ports), and sometimes I felt more like being a Chromium than a > FreeBSD developer. >=20 > This does mean that *you* will have to continue, but I (boldly) think > there is enough interest for it. This should hopefully get you = started: > - As you might know, we have an work-in-progress repository on GitHub: > https://github.com/gliaskos/freebsd-chromium/ > - Patches are available in the Ports Tree and on GitHub. There are = also > experimental patches against the top-of-tree (like FreeBSD-CURRENT) = at > https://people.freebsd.org/~rene/chromium/ > - The latter location also contains a script to generate the patches > (gen-diff.sh) and a script to try to build chromium in a chroot > (update.sh). It also contains a list of required packages = (pkg-list). > Note that libxml2 and yasm can go once the bundled versions work. > - Minor version updates are mostly a matter of running `make makesum` > and checking if the pkg-plist is still OK. See below for major > version updates. > - Notice that new upstream distribution files can take a day to = appear, > even in the case of a security update. >=20 > Porting a new major version (for GitHub or the Ports Tree) is a > different story though: > - Checkout the beta branch at GitHub > - Bump the PORTVERSION, run `make makesum` > - Run `make checkpatch` to see which patches still apply. Temporarily > move Broken / orphaned patches out of the way. Repeat till > `make checkpatch` is fine. > - Fix or delete the patches you just moved > - Try to build the port. Have coffee, brain, and willpower ready... > - If `make configure` fails, this is mostly because gyp is = complaining. > In case a directory got accidentally deleted by the > remove_bundled_libraries.py script, put it back in, add it to its > list, and try again. > - In case you need inspiration for a patch, try to look at the > corresponding Linux or MacOSX code. A lot of times adding BSD to = the > list suffices. > - Once Chromium links and staging passes, run `make check-plist` and > `make package` to see if the package list is still OK. > - Try to run it. > - Once that works, you can send the patches using a PR, a website, or > otherwise. > - Every six weeks or so the Beta version gets Stable, which means it = is > time to merge the beta branch back into the master branch. > - To get the patch for the Ports Tree, replace the old files/ = directory > with the new one, and update Makefile, pkg-*, and distinfo >=20 > In case you feel like working with upstream: > - See the WWW site for some hints on getting started > - Have a modern machine ready (many cores, RAM, ZFS, ccache) > - Check upstream on how to get the sources (chroot highly recommended > to not pollute your existing system). Notice that the initial > checkout can is between 10 GB and 15 GB large. > - Apply the patches from https://people.freebsd.org/~rene/chromium/ > - Run the script to try to build Chromium: > sh ./update.sh build nopull > Even more coffee, brain, and willpower recommended. > - To update from upstream, run: > sh ./update.sh > and check for merge conflicts in the git output. >=20 > Resources: > - https://googlechromereleases.blogspot.com/ > - chromium-dev@chromium.org > - chromium-packagers@chromium.org > - #chromium on FreeNode >=20 > For now I will continue to: > - Committing VuXML entries > - Committing new versions to the Ports Tree (e.g. as PR) and to = GitHub. > Feel free to fork the repository. > - Answer any questions you have. >=20 > Do mind that (at least in my experience), interest from upstream in = BSD > varies. There might eventually be BSD bots, but that doesn't > necessarily mean that build errors on BSD will be blocking (as they = are > on Windows / Linux / MacOSX / Android / iOS). >=20 > A good person to contact would be Pawel Hajdan Jr > >=20 > Regards, > Ren=E9 Hey Ren=E9, As someone who uses Chromium on a daily basis (and admittedly takes it = for granted), I would like to give you a sincere thank you for your hard = work. I=92m hoping that the person who fills in your big, worn shoes = will achieve the same level of awesomeness. Good luck in your future endeavors. Thanks, Shawn --Apple-Mail=_7E422C50-6C7C-426A-8C1F-51E00C0DA013 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- iQIcBAEBAgAGBQJUbnW5AAoJEGqEZY9SRW7u3psP/jveYy6n7Y1rwtZSBoR/+CnW HI6v7Gs2TEU/0NoxiqOPWz4khnhk0zxbuGFmad+SJY8tXic9JaYeJGDkhNFm+yEU YKbD6BGccM0uGxpUpl2Pb29sn/YI15qJHu1237WCq00FQRAuAfkY3S6CtSRtyvgX /i2DfFKdVOm62MBO8n+aeGnVYAaN1zVmlSwYjfY7Qn3V50iYYg+j/+zAo9erAqzT SYRqewIjS76P6vQPiytKUS10avrv9QjaXAWPPxCyLa8r292cMK963exAhC56Gjtc wIIFCL2esKpk3Z/aAZRVJFSL9meDZJQMI7dE1z4jz0WNgA9Wh0GCmWxlcKGe15EZ w1SfjNfxwZ6xxjuERZ04qzYdV+oB6IcgdiO7rnb+y55gCCn8nT0blZrnHi1rOtKA d4bsP5FQiTWu+/3ILa2rxuZ40HOFy7I7roh5R5Vqjt01Kg68uzzSH5K6JQM37L3r cssD03j19oNzBebR4Fny56Z++XTtYOVv1LxiEF+hc3HkWeRgIOi8+IXgPWJ28xb8 CU8ealyuVhw+6d8Xljj6Nnt6q7yNHuNfjQPS8yuPnjvEjOOevJDdgLtXhG12CH4+ X3z/a7kJ0kcnvlvoW5MioQ3kv0LybwbaPdrGgYjiW8PTLVV5VKTI94U9voVYKjNX SEZxu1cN94o4PgkVhM/d =1slt -----END PGP SIGNATURE----- --Apple-Mail=_7E422C50-6C7C-426A-8C1F-51E00C0DA013-- From owner-freebsd-chromium@FreeBSD.ORG Fri Nov 21 01:30:46 2014 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9F343654 for ; Fri, 21 Nov 2014 01:30:46 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6D88EC36 for ; Fri, 21 Nov 2014 01:30:46 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAL1Uk4l084616 for ; Fri, 21 Nov 2014 01:30:46 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 193610] www/chromium 37.0.2062.120_1 Bus error (core dumped) Date: Fri, 21 Nov 2014 01:30:44 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: beastie@tardisi.com X-Bugzilla-Status: Needs Triage X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2014 01:30:46 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193610 --- Comment #42 from Lawrence Chen --- Was going to report earlier that I finally have a working chromium again, on system where I had been without any chromium (seems once it starts upgrading your profile you can't go back.) vs system where I had been staying with 35.x Had stopped here to find out what it was to turn off to stop the address bar crash. Though the fix isn't 100%. If I type a single word into the address bar, it'll crash. So no doing searches of just a single word (though I did install a search extension, maybe I should get in habit of using it more...) Sad to find that NPAPI is more....as a result, I immediately missed 3 things....java, flash and PDF. The latter I resolved when I found an extension that does/uses Firefox's HTML5 PDF renderer. Which however isn't 100%. I can use it to view PDF statements and such from my credit cards sites. There's probably a security layer that prevents it from crossing into the extension where NPAPI didn't stop such things. The other annoyance is that it no longer understands that my desktop is two screens connected by Xinerma...not one big view....where it wants to do as much as possible on the right side. Include if I don't keep it maximized move most of the window offscreen to the right..... Had recalled seeing that it had a concept of "work area(s)" vs "display area", with files or sections for various types of systems, hopefully its just a missed defined() check that got missed in recent ports. Now getting more annoying that can't middle click text in (or out) of forms/addressbar in chromium. Not uncommon for me to deliberately have different things in the two 'clipboards'. Perhaps time to investigate using the more advanced features of my clipboard manager (providing it survives the upgrade to gnome3.) Currently not building it debug...though not stripping it. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-chromium@FreeBSD.ORG Fri Nov 21 05:55:31 2014 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E7DA778E for ; Fri, 21 Nov 2014 05:55:31 +0000 (UTC) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id BA8249C1 for ; Fri, 21 Nov 2014 05:55:31 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id sAL5tPBU029802 for ; Thu, 20 Nov 2014 21:55:25 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <546ED3CD.8090506@rawbw.com> Date: Thu, 20 Nov 2014 21:55:25 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: chromium@FreeBSD.org Subject: Chrome 39.0.2171.65 starts with black screen Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2014 05:55:32 -0000 Completely unusable. Previous version 38.0.2125.122 worked fine. System uses NVidia binary driver, if this matters. Yuri From owner-freebsd-chromium@FreeBSD.ORG Fri Nov 21 06:56:45 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7383C639 for ; Fri, 21 Nov 2014 06:56:45 +0000 (UTC) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0811DF8B for ; Fri, 21 Nov 2014 06:56:45 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id bs8so10974535wib.16 for ; Thu, 20 Nov 2014 22:56:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=yC6awqGxLOokg1dlPxECMVR9A/xuQa57DVDzkOj2Ad0=; b=mxugH6YAw//R1VJVZUdCtpm8m5swpuMBQf664coABaisGCloTYeheTOEI6N9L00oc6 E1zKz6beGYPq8E9DtEC6EDD0jojtYOecUd7NjVoPZ3NxQ5FssvwGgKX97LHJF38NFLyc nMU3cE/GS6K8zzeTV176RR1apPJIpkHxXOVrghMLIk43iMXGsnhv0pS98G78kvWafSif U7frcKze6S1lE23TLxxxlqc6tKqfDWrIQJjkIZ4vjQD7IUMyjLEZnlXJEr8pwlvAT83H Ler58IQJD2X7VmdlKsxOylQc6G2/X7gKFdjF3/30XyEkHjrU9qEU90RBKIb8c/kkOnes 539Q== X-Received: by 10.194.193.38 with SMTP id hl6mr4354276wjc.38.1416553003466; Thu, 20 Nov 2014 22:56:43 -0800 (PST) Received: from ?IPv6:2001:980:d7ed:1:b4ec:e001:49fe:edd1? ([2001:980:d7ed:1:b4ec:e001:49fe:edd1]) by mx.google.com with ESMTPSA id vy7sm6718921wjc.27.2014.11.20.22.56.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Nov 2014 22:56:42 -0800 (PST) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <546EE229.1080407@freebsd.org> Date: Fri, 21 Nov 2014 07:56:41 +0100 From: =?windows-1252?Q?Ren=E9_Ladan?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-chromium@freebsd.org Subject: Re: Chrome 39.0.2171.65 starts with black screen References: <546ED3CD.8090506@rawbw.com> In-Reply-To: <546ED3CD.8090506@rawbw.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2014 06:56:45 -0000 On 21-11-2014 06:55, Yuri wrote: > Completely unusable. > Previous version 38.0.2125.122 worked fine. > System uses NVidia binary driver, if this matters. > It runs fine here, also with the binary NVidia driver (version 340.24_1). What is your FreeBSD version/architecture? (here 10.0 amd64). One thing I can think of is the removal of the -fno-stack-protector flag in Makefile, but I would expect a crash if that is the cause. René From owner-freebsd-chromium@FreeBSD.ORG Fri Nov 21 07:10:13 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E72288EC for ; Fri, 21 Nov 2014 07:10:13 +0000 (UTC) Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6F630197 for ; Fri, 21 Nov 2014 07:10:13 +0000 (UTC) Received: by mail-wi0-f182.google.com with SMTP id h11so7743257wiw.15 for ; Thu, 20 Nov 2014 23:10:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=+0F3G1l1Ys419LGCzwB0Ph6DG9li0scFimjZaFZch6g=; b=zHfESnpu6XyUQhi/5dvx1x0RtS6Zf/etP5nnZc9r2+yQJxA2khBLlkuiNKbtvua+8B k34XwWsiVKT7Klzbp69baX25+ruLGT3QDmZHPiU1YORYgPmuv/FtGoOSuZwN0nZEr5cm t0npg7xeHNyK6Iv3B/4hx/RiWToRQSu2R3qM1T6ozL5xLTbNjrvhPaae/Z+O3XRMf2f/ miVl7ogt2fOeXrGGO5AedBz/StLVagl52iE0PETO15Kre01h44TlIgF+auNaKLmXCBKg LuOSZdIwXufLZ9D07fVjU71CgVIMD2jEcnRWJ7SbVohQuLoUjbjmtnhxNWGNohdatJb7 XhzQ== X-Received: by 10.194.241.194 with SMTP id wk2mr4233685wjc.132.1416553811809; Thu, 20 Nov 2014 23:10:11 -0800 (PST) Received: from ?IPv6:2001:980:d7ed:1:b4ec:e001:49fe:edd1? ([2001:980:d7ed:1:b4ec:e001:49fe:edd1]) by mx.google.com with ESMTPSA id vm8sm6794896wjc.6.2014.11.20.23.10.10 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 20 Nov 2014 23:10:11 -0800 (PST) Sender: =?UTF-8?Q?Ren=C3=A9_Ladan?= Message-ID: <546EE551.8030401@freebsd.org> Date: Fri, 21 Nov 2014 08:10:09 +0100 From: =?windows-1252?Q?Ren=E9_Ladan?= User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: Shawn Webb Subject: Re: backing down on Chromium ... References: <546E72B9.60700@freebsd.org> <8A50107E-55F9-4AD1-981A-5A52DDB5DC0A@gmail.com> In-Reply-To: <8A50107E-55F9-4AD1-981A-5A52DDB5DC0A@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 8bit Cc: chromium-list freebsd X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2014 07:10:14 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 21-11-2014 00:13, Shawn Webb wrote: > On Nov 20, 2014, at 6:01 PM, René Ladan wrote: > >> Signed PGP part >> Hello all, >> >> after already four years I decided to back down somewhat on Chromium. >> This is not an overnight decision, the feeling started creeping in >> several months ago. >> >> One reason is that maintaining Chromium all the way on FreeBSD would >> seriously be a good candidate for a full-time job: >> - keep the existing patches working, they need to be checked and >> possibly rewritten on every major release >> - polishing patches for upstream and tickling the upstream bots >> - hunting down incompatibilities. This is mostly caused FreeBSD >> masquerading as Linux and consequently Chromium assumes that e.g. >> /proc is populated as on Linux. >> - writing missing code for FreeBSD, including but not limited to: >> - low-level network stuff >> - fcvt(3) >> - obtaining hard disk drive serial number for the Google Music (if >> I understand correctly) >> - obtaining detailed memory usage, proper GPU porting >> - keeping the GitHub and ports version in sync >> - writing VuXML entries once in a while >> Also, other things seem more interesting (e.g. FreeBSD documentation or >> other ports), and sometimes I felt more like being a Chromium than a >> FreeBSD developer. >> >> This does mean that *you* will have to continue, but I (boldly) think >> there is enough interest for it. This should hopefully get you started: >> - As you might know, we have an work-in-progress repository on GitHub: >> https://github.com/gliaskos/freebsd-chromium/ >> - Patches are available in the Ports Tree and on GitHub. There are also >> experimental patches against the top-of-tree (like FreeBSD-CURRENT) at >> https://people.freebsd.org/~rene/chromium/ >> - The latter location also contains a script to generate the patches >> (gen-diff.sh) and a script to try to build chromium in a chroot >> (update.sh). It also contains a list of required packages (pkg-list). >> Note that libxml2 and yasm can go once the bundled versions work. >> - Minor version updates are mostly a matter of running `make makesum` >> and checking if the pkg-plist is still OK. See below for major >> version updates. >> - Notice that new upstream distribution files can take a day to appear, >> even in the case of a security update. >> >> Porting a new major version (for GitHub or the Ports Tree) is a >> different story though: >> - Checkout the beta branch at GitHub >> - Bump the PORTVERSION, run `make makesum` >> - Run `make checkpatch` to see which patches still apply. Temporarily >> move Broken / orphaned patches out of the way. Repeat till >> `make checkpatch` is fine. >> - Fix or delete the patches you just moved >> - Try to build the port. Have coffee, brain, and willpower ready... >> - If `make configure` fails, this is mostly because gyp is complaining. >> In case a directory got accidentally deleted by the >> remove_bundled_libraries.py script, put it back in, add it to its >> list, and try again. >> - In case you need inspiration for a patch, try to look at the >> corresponding Linux or MacOSX code. A lot of times adding BSD to the >> list suffices. >> - Once Chromium links and staging passes, run `make check-plist` and >> `make package` to see if the package list is still OK. >> - Try to run it. >> - Once that works, you can send the patches using a PR, a website, or >> otherwise. >> - Every six weeks or so the Beta version gets Stable, which means it is >> time to merge the beta branch back into the master branch. >> - To get the patch for the Ports Tree, replace the old files/ directory >> with the new one, and update Makefile, pkg-*, and distinfo >> >> In case you feel like working with upstream: >> - See the WWW site for some hints on getting started >> - Have a modern machine ready (many cores, RAM, ZFS, ccache) >> - Check upstream on how to get the sources (chroot highly recommended >> to not pollute your existing system). Notice that the initial >> checkout can is between 10 GB and 15 GB large. >> - Apply the patches from https://people.freebsd.org/~rene/chromium/ >> - Run the script to try to build Chromium: >> sh ./update.sh build nopull >> Even more coffee, brain, and willpower recommended. >> - To update from upstream, run: >> sh ./update.sh >> and check for merge conflicts in the git output. >> >> Resources: >> - https://googlechromereleases.blogspot.com/ >> - chromium-dev@chromium.org >> - chromium-packagers@chromium.org >> - #chromium on FreeNode >> >> For now I will continue to: >> - Committing VuXML entries >> - Committing new versions to the Ports Tree (e.g. as PR) and to GitHub. >> Feel free to fork the repository. >> - Answer any questions you have. >> >> Do mind that (at least in my experience), interest from upstream in BSD >> varies. There might eventually be BSD bots, but that doesn't >> necessarily mean that build errors on BSD will be blocking (as they are >> on Windows / Linux / MacOSX / Android / iOS). >> >> A good person to contact would be Pawel Hajdan Jr >> >> >> Regards, >> René > > Hey René, > > As someone who uses Chromium on a daily basis (and admittedly takes it for granted), I would like to give you a sincere thank you for your hard work. I’m hoping that the person who fills in your big, worn shoes will achieve the same level of awesomeness. Thank you for your warm words :) I should also thank George Liaskos, who helped out with patching Chromium from the early days up to version 30. Without him we might not even have a Chromium port today. Regards, René > > Good luck in your future endeavors. > > Thanks, > > Shawn -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUbuVRXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQxMDFBNzE2QjE2MkIwMEU1NUJFREVBMDVB REJCRjg2MTBBMzc4OUI3AAoJEK27+GEKN4m3PYkP/0kLLCCOeJTsKsUI4ViAOgju MkrFSfgPdYbxLBAhe1ZOiBwV9BZZ8CGD7Dvnk5jGNI3hUTsib52PbeXCr1DRrNMD +E4CuIB6Gbwsn2s9K675b3WfHwq8Ze1nZUsBvBouQmqFXUHpqbx2ycIpD5C8zbwX eqT6x629Ky9dHyzd5Vfu9XJNQW0FjqL3+BmEBbeY2Q0K4lMpd8De181r6tez7RlT cHWazomQOSKOt1vTXPUSiNuRd7/Q7m0EY+AZNH46PKYIi8Xj7hehc8QrF6ovKJHv 9WlZiJTD9tZdmKlXAH7GfgEcOJep57aBy1GUfvR/dgtMpx7z56ECiPABMi+P/qpr 9IjKM5o8QXLFSffbS1i7YiK1pIlMSmjF6vm4lbI24P1qfRFtXbfs6xw2bATJ8TOS xy6R0UMp/B3iq4UUmuZpMXiQyFcamltz0+1nLWXVSQNDjLCb5fSceK5Msuj95geV AkKP1Q8eOudQPQXe7sQMq9/F2XCZE6OQ3tnBg6afrXNpyu/7wiGA2/4t6jo4TOwd tJ4f+DjnECk/BhS8xuv1iG1OhTY4YJjBl/Eh/jig3QbnAG9rE+Dk8ufm1z/NO9uD IzvKDcx7s40uKPfgeGnzP1Bi+ZJ42y+Hp+q/ERdgv3asHbqtxhsYJzVju7qvDkY1 y5WDYw//lKhox5/FLsjq =+YFz -----END PGP SIGNATURE----- From owner-freebsd-chromium@FreeBSD.ORG Fri Nov 21 07:37:11 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A86BACB3; Fri, 21 Nov 2014 07:37:11 +0000 (UTC) Received: from shell0.rawbw.com (shell0.rawbw.com [198.144.192.45]) by mx1.freebsd.org (Postfix) with ESMTP id 7BDA7671; Fri, 21 Nov 2014 07:37:10 +0000 (UTC) Received: from eagle.yuri.org (stunnel@localhost [127.0.0.1]) (authenticated bits=0) by shell0.rawbw.com (8.14.4/8.14.4) with ESMTP id sAL7b9PS048099; Thu, 20 Nov 2014 23:37:10 -0800 (PST) (envelope-from yuri@rawbw.com) Message-ID: <546EEBA5.6090307@rawbw.com> Date: Thu, 20 Nov 2014 23:37:09 -0800 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: =?windows-1252?Q?Ren=E9_Ladan?= , freebsd-chromium@freebsd.org Subject: Re: Chrome 39.0.2171.65 starts with black screen References: <546ED3CD.8090506@rawbw.com> <546EE229.1080407@freebsd.org> In-Reply-To: <546EE229.1080407@freebsd.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2014 07:37:11 -0000 On 11/20/2014 22:56, René Ladan wrote: > It runs fine here, also with the binary NVidia driver (version 340.24_1). > > What is your FreeBSD version/architecture? (here 10.0 amd64). One thing > I can think of is the removal of the -fno-stack-protector flag in > Makefile, but I would expect a crash if that is the cause. I just downgraded to 38.0.2125.122 and it is still black, even though it worked today before system update. I think some dependency causes this. 10.1 amd64 Yuri From owner-freebsd-chromium@FreeBSD.ORG Fri Nov 21 17:19:17 2014 Return-Path: Delivered-To: freebsd-chromium@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 42DB85B4 for ; Fri, 21 Nov 2014 17:19:17 +0000 (UTC) Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com [IPv6:2607:f8b0:4001:c05::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 03EF0DCD for ; Fri, 21 Nov 2014 17:19:16 +0000 (UTC) Received: by mail-ig0-f177.google.com with SMTP id uq10so5037062igb.4 for ; Fri, 21 Nov 2014 09:19:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=goodking.ca; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=sGwEAcQQhdbV5LC2jnvSMt5JFw2Pv53xoRF972hM3CQ=; b=Mw9/NAtOP2T/ZTom/YbezcvIDp8SFlo5JTY192lhqAu4CpOmTcYYh/jbX7hMTRBB/G SQYpaWygAa7d+Ar6vGE3SzW2WBsM3tyAS/jW7WyRcMd2odAQeyQZPgXsAJAt5UhORT03 he8Ow3tFm3N6uu5mXVIaoihqmwuJ/g2IgyJxQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=sGwEAcQQhdbV5LC2jnvSMt5JFw2Pv53xoRF972hM3CQ=; b=csG8EUTcHUlcV8z69dbz7sySFW+uUjZoTvLvKNfqPguXdk50UzF+/VY7sbyW275WBy h+fFZeB9RdSWxs/5kY2WsGIygTQPOmFQIbqDAfgRAPGp+CCCIgFA+7rZI3CijUjWFmOA Z/XhQfMNG8IBJ6IKrRkrKReWkpSxEk1TNtql365wPh5bJtC8u2XSmtvW6nWC6faD2hLJ nCMs8kd9riIW02Umq0dnWVSNfIjAXPUOTPIIVRmrA4gdDaVwcdQp0rjCYy6EnjuAB/Pp 4n6hVUaHDhGkL/WCLwV5Y0LJJQLXdBBrh0O90AOS8Emt0fT60kSbrrYqjyQkvDuXc87S 7Hpg== X-Gm-Message-State: ALoCoQn6qsIbyjQpGvnPsJeJQEqnvjeRylQ2fcEGtFPJMhCr+wapGYffdcv2CBf95jUQFV7Qd6Xl X-Received: by 10.107.37.73 with SMTP id l70mr4063191iol.63.1416590356299; Fri, 21 Nov 2014 09:19:16 -0800 (PST) Received: from goodking.ca (tabthorpe-1-pt.tunnel.tserv21.tor1.ipv6.he.net. [2001:470:1c:cbb::2]) by mx.google.com with ESMTPSA id m2sm3217493ioi.10.2014.11.21.09.19.14 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 21 Nov 2014 09:19:15 -0800 (PST) Date: Fri, 21 Nov 2014 12:19:11 -0500 From: Thomas Abthorpe To: =?iso-8859-1?Q?Ren=E9?= Ladan Subject: Re: backing down on Chromium ... Message-ID: <20141121171911.GA30654@goodking.ca> References: <546E72B9.60700@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <546E72B9.60700@freebsd.org> X-URL: http://www.goodking.ca/ X-PGP-Key: http://www.goodking.ca/~tabthorpe/tabthorpe.asc X-PGP-Key-ID: 0xD9371097A473C990 X-PGP-Key-Fingerprint: D883 2D7C EB78 944A 69FC 36A6 D937 1097 A473 C990 User-Agent: Mutt/1.5.23 (2014-03-12) Cc: chromium-list freebsd X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Nov 2014 17:19:17 -0000 --YZ5djTAD1cGYuMQK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 21, 2014 at 12:01:13AM +0100, Ren Ladan wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 >=20 > Hello all, >=20 > after already four years I decided to back down somewhat on Chromium. > This is not an overnight decision, the feeling started creeping in > several months ago. >=20 I for one want to thank Rene from the bottom of my heart. I dragged him into this way back when, and being the good chap he is, graciously accepted. Thank you Rene and Giorgios, you have done a great job on keeping it current. With hat: chromium on freebsd user --=20 Thomas Abthorpe thomas@goodking.ca --YZ5djTAD1cGYuMQK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUb3QOAAoJENk3EJekc8mQhrEIAKMZYWGDUN0n9a/DEpUd3l0F 194e8nIjEIMWyWgYXxOO1z9uNAz5DuK2vJeslA3/E126R1SW7BNgqdBvxX4icGJD JB2X0lE54j2b9ephrFJkrpIKdhwKkQfhBsP/Nuk2SOYOVIc/AXM5zu0XHlqG7+1z JPCFCPa/Z9hYr1fhuVXLjbuAaVV2OxZnqB19cHPy4sYC+NsP8ka7ZGNyCf12vuJT JxzAiMag7PjehOWYqtdgk0QNkYZ/f1sROJerdBiG964385QTRLq8nlcDCZybs3GL btQ4dWYwpDwQcl441myCesWN/+qNxNLhm+0w1ss6Dw/BCYKGoef1gyKr0Q5ftqc= =Ad80 -----END PGP SIGNATURE----- --YZ5djTAD1cGYuMQK-- From owner-freebsd-chromium@FreeBSD.ORG Sat Nov 22 18:29:25 2014 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5C6C3B48 for ; Sat, 22 Nov 2014 18:29:25 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 498201CD for ; Sat, 22 Nov 2014 18:29:25 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAMITPbb030447 for ; Sat, 22 Nov 2014 18:29:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: maintainer-feedback requested: [Bug 195288] www/chromium gcc fails Date: Sat, 22 Nov 2014 18:29:25 +0000 X-Bugzilla-Type: request Message-ID: In-Reply-To: References: X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2014 18:29:25 -0000 mikhail.rokhin@gmail.com has asked chromium@FreeBSD.org for maintainer-feedback: Bug 195288: www/chromium gcc fails https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195288 --- Description --- ===> Building for chromium-39.0.2171.65 ninja: Entering directory `out/Release' [7/15540] CC obj/third_party/libvpx/source/libv...er/libvpx_asm_offsets_vp8.vp8_asm_enc_offs ets.o FAILED: gcc5 -MMD -MF obj/third_party/libvpx/source/libvpx/vp8/encoder/libvpx_asm_offsets_vp8.vp8_asm _enc_offsets.o.d -DV8_DEPRECATION_WARNINGS -D_FILE_OFFSET_BITS=64 -DNO_TCMALLOC -DDISABLE_NACL -DCHROMIUM_BUILD -DCR_CLANG_REVISION=217949 -DTOOLKIT_VIEWS=1 -DUSE_AURA=1 -DUSE_ASH=1 -DUSE_PANGO=1 -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1 -DUSE_CLIPBOARD_AURAX11=1 -DENABLE_ONE_CLICK_SIGNIN -DUSE_XI2_MT=2 -DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -DUSE_PROPRIETARY_CODECS -DENABLE_CONFIGURATION_POLICY -DENABLE_NOTIFICATIONS -DENABLE_EGLIMAGE=1 -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1 -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_BACKGROUND=1 -DENABLE_GOOGLE_NOW=1 -DCLD_VERSION=2 -DCLD2_DATA_SOURCE=static -DENABLE_FULL_PRINTING=1 -DENABLE_PRINTING=1 -DENABLE_SPELLCHECK=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 -DENABLE_MANAGED_USERS=1 '-DDATA_REDUCTION_FALLBACK_HOST="http://compress.googlezip.net:80/"' '-DDATA_REDUCTION_DEV_HOST="https://proxy-dev.googlezip.net:443/"' '-DDATA_REDUCTION_DEV_FALLBACK_HOST="http://proxy-dev.googlezip.net:80/"' '-DSPDY_PROXY_AUTH_ORIGIN="https://proxy.googlezip.net:443/"' '-DDATA_REDUCTION_PROXY_PROBE_URL="http://check.googlezip.net/connect"' '-DDATA_REDUCTION_PROXY_WARMUP_URL="http://www.gstatic.com/generate_204"' -DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 -DENABLE_LOAD_COMPLETION_HACKS=1 -DUSE_NSS=1 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -Igen -I../../third_party/libvpx/source/config/linux/x64 -I../../third_party/libvpx/source/config -I../../third_party/libvpx/source/libvpx -fstack-protector --param=ssp-buffer-size=4 -pthread -fno-strict-aliasing -Wno-unused-parameter -Wno-missing-field-initializers -fvisibility=hidden -pipe -fPIC -Wno-reserved-user-defined-literal -fcolor-diagnostics -Wheader-hygiene -Wno-char-subscripts -Wno-unneeded-internal-declaration -Wno-covered-switch-default -Wstring-conversion -Wno-c++11-narrowing -Wno-deprecated-register -Wno-unused-local-typedef -Wno-format -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -funwind-tables -O2 -pipe -march=native -isystem/usr/local/include -Wno-unknown-warning-option -fstack-protector -Wl,-rpath=/usr/local/lib/gcc5 -fno-strict-aliasing -c ../../third_party/libvpx/source/libvpx/vp8/encoder/vp8_asm_enc_offsets.c -o obj/third_party/libvpx/source/libvpx/vp8/encoder/libvpx_asm_offsets_vp8.vp8_asm _enc_offsets.o gcc5: error: unrecognized command line option '-fcolor-diagnostics' gcc5: error: unrecognized command line option '-Wheader-hygiene' gcc5: error: unrecognized command line option '-Wstring-conversion' [7/15540] ACTION Generating resources from blink_resources.grd ninja: build stopped: subcommand failed. ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/www/chromium *** Error code 1 and gcc-4.x either. --- Comment #1 from Bugzilla Automation --- Auto-assigned to maintainer chromium@FreeBSD.org From owner-freebsd-chromium@FreeBSD.ORG Sat Nov 22 18:29:25 2014 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A4889B4A for ; Sat, 22 Nov 2014 18:29:25 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8CA4B1D0 for ; Sat, 22 Nov 2014 18:29:25 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAMITP5N030455 for ; Sat, 22 Nov 2014 18:29:25 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 195288] New: www/chromium gcc fails Date: Sat, 22 Nov 2014 18:29:25 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: mikhail.rokhin@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2014 18:29:25 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195288 Bug ID: 195288 Summary: www/chromium gcc fails Product: Ports Tree Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: chromium@FreeBSD.org Reporter: mikhail.rokhin@gmail.com Assignee: chromium@FreeBSD.org Flags: maintainer-feedback?(chromium@FreeBSD.org) ===> Building for chromium-39.0.2171.65 ninja: Entering directory `out/Release' [7/15540] CC obj/third_party/libvpx/source/libv...er/libvpx_asm_offsets_vp8.vp8_asm_enc_offsets.o FAILED: gcc5 -MMD -MF obj/third_party/libvpx/source/libvpx/vp8/encoder/libvpx_asm_offsets_vp8.vp8_asm_enc_offsets.o.d -DV8_DEPRECATION_WARNINGS -D_FILE_OFFSET_BITS=64 -DNO_TCMALLOC -DDISABLE_NACL -DCHROMIUM_BUILD -DCR_CLANG_REVISION=217949 -DTOOLKIT_VIEWS=1 -DUSE_AURA=1 -DUSE_ASH=1 -DUSE_PANGO=1 -DUSE_CAIRO=1 -DUSE_GLIB=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DUSE_X11=1 -DUSE_CLIPBOARD_AURAX11=1 -DENABLE_ONE_CLICK_SIGNIN -DUSE_XI2_MT=2 -DENABLE_REMOTING=1 -DENABLE_WEBRTC=1 -DUSE_PROPRIETARY_CODECS -DENABLE_CONFIGURATION_POLICY -DENABLE_NOTIFICATIONS -DENABLE_EGLIMAGE=1 -DENABLE_TASK_MANAGER=1 -DENABLE_EXTENSIONS=1 -DENABLE_PLUGINS=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_THEMES=1 -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_BACKGROUND=1 -DENABLE_GOOGLE_NOW=1 -DCLD_VERSION=2 -DCLD2_DATA_SOURCE=static -DENABLE_FULL_PRINTING=1 -DENABLE_PRINTING=1 -DENABLE_SPELLCHECK=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 -DENABLE_MANAGED_USERS=1 '-DDATA_REDUCTION_FALLBACK_HOST="http://compress.googlezip.net:80/"' '-DDATA_REDUCTION_DEV_HOST="https://proxy-dev.googlezip.net:443/"' '-DDATA_REDUCTION_DEV_FALLBACK_HOST="http://proxy-dev.googlezip.net:80/"' '-DSPDY_PROXY_AUTH_ORIGIN="https://proxy.googlezip.net:443/"' '-DDATA_REDUCTION_PROXY_PROBE_URL="http://check.googlezip.net/connect"' '-DDATA_REDUCTION_PROXY_WARMUP_URL="http://www.gstatic.com/generate_204"' -DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 -DENABLE_LOAD_COMPLETION_HACKS=1 -DUSE_NSS=1 -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -Igen -I../../third_party/libvpx/source/config/linux/x64 -I../../third_party/libvpx/source/config -I../../third_party/libvpx/source/libvpx -fstack-protector --param=ssp-buffer-size=4 -pthread -fno-strict-aliasing -Wno-unused-parameter -Wno-missing-field-initializers -fvisibility=hidden -pipe -fPIC -Wno-reserved-user-defined-literal -fcolor-diagnostics -Wheader-hygiene -Wno-char-subscripts -Wno-unneeded-internal-declaration -Wno-covered-switch-default -Wstring-conversion -Wno-c++11-narrowing -Wno-deprecated-register -Wno-unused-local-typedef -Wno-format -m64 -march=x86-64 -O2 -fno-ident -fdata-sections -ffunction-sections -funwind-tables -O2 -pipe -march=native -isystem/usr/local/include -Wno-unknown-warning-option -fstack-protector -Wl,-rpath=/usr/local/lib/gcc5 -fno-strict-aliasing -c ../../third_party/libvpx/source/libvpx/vp8/encoder/vp8_asm_enc_offsets.c -o obj/third_party/libvpx/source/libvpx/vp8/encoder/libvpx_asm_offsets_vp8.vp8_asm_enc_offsets.o gcc5: error: unrecognized command line option '-fcolor-diagnostics' gcc5: error: unrecognized command line option '-Wheader-hygiene' gcc5: error: unrecognized command line option '-Wstring-conversion' [7/15540] ACTION Generating resources from blink_resources.grd ninja: build stopped: subcommand failed. ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /usr/ports/www/chromium *** Error code 1 and gcc-4.x either. --- Comment #1 from Bugzilla Automation --- Auto-assigned to maintainer chromium@FreeBSD.org -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-chromium@FreeBSD.ORG Sat Nov 22 18:29:40 2014 Return-Path: Delivered-To: chromium@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72EBDB98 for ; Sat, 22 Nov 2014 18:29:40 +0000 (UTC) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 5B2B21D5 for ; Sat, 22 Nov 2014 18:29:40 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAMITeMS030527 for ; Sat, 22 Nov 2014 18:29:40 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 195288] www/chromium gcc fails Date: Sat, 22 Nov 2014 18:29:40 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports Tree X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: mikhail.rokhin@gmail.com X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: chromium@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: maintainer-feedback+ X-Bugzilla-Changed-Fields: cc flagtypes.name Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 22 Nov 2014 18:29:40 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195288 mikhail.rokhin@gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mikhail.rokhin@gmail.com Flags|maintainer-feedback?(chromi |maintainer-feedback+ |um@FreeBSD.org) | -- You are receiving this mail because: You are the assignee for the bug.