From owner-freebsd-chromium@FreeBSD.ORG Wed May 6 07:11:22 2015 Return-Path: Delivered-To: freebsd-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 42A555A1 for ; Wed, 6 May 2015 07:11:22 +0000 (UTC) Received: from oxim13.net (oxim13.net [37.59.37.16]) (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 E90A91BDD for ; Wed, 6 May 2015 07:11:21 +0000 (UTC) Received: from NYILWMO44 (localhost.localdomain [127.0.0.1]) by oxim13.net (Postfix) with SMTP id 172151081ACB for ; Wed, 6 May 2015 09:02:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=oxim13.net; s=oxidkim; t=1430895737; bh=VCQ0NzoT9Znh6dktoagO9LoqiSzGz0VF0Oe9hDl2AG4=; h=List-Unsubscribe:From:To:Subject:Date; b=PsMniAAq2oV3N5I57LYaC8avC9ZmN6i1LDP1qVzZLljAvtWty4Dir9S7ScqKtOrcJ 0CBQbl1wOqjLslZAgRjTb4BimZPyzMgCTU5XOD5RTo4JPbVuqSLZqOmsZnptZ/5+4s rhIACuZEVtMYSjf81Zzb+0ilGcTALly4sTOJCP6yo3jDYgyPaNqaq0J62/3o5PNNZR VBDB4MJOYe54lc7uGYQkKZ92Rj0bCo6gmFep0XeNHOfE9qwlpDc0H26ZeN2NcXEqPf jGpbatvYgm9ZxV0J8BftxeWhJaTIO7CDc51BDmpNK+WDviHPsTUSPttzBuUlX3T3vY 73byIaW/alirQ== X-MessageId: 788973768777795252||70826969668368456772827977738577647082696966836846798271||100614733||7||788973768777795252 Message-ID: <35bd1560b3a770476da570b812ee9e6e@love4aviation.com> From: To: Subject: FoxtrotSix by Love4aviation. Date: Wed, 6 May 2015 09:01:00 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 07:11:22 -0000 If this message doesn't display correctly, read it online=2E =20 A bug in the coding of our newsletter broke the hyperlinks. So here are = the links to watch our latest video on your favorite website. Sorry for = the inconvenience=2E FoxtrotSix by Love4aviation FoxtrotSix, our new video. Another Community video from the gigabits of = recordings provided by pilots from all over the world. We hope you enjoy = it and become contributors by sending us your raw video files.=20 Watch it now on: =20 Aviation Safety Warning: Another evidence of a Duc Helices propeller = breakage. Keep in mind that according to ICAO regulation, pilots and = engineers have a duty to report any occurence involving aviation safety. = Read more=2E Stay with us: Share : Please remove me from your mailing list in english. From owner-freebsd-chromium@FreeBSD.ORG Wed May 6 10:36:09 2015 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 8B6B5199 for ; Wed, 6 May 2015 10:36:09 +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 760CE127B for ; Wed, 6 May 2015 10:36:09 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t46Aa9MJ034713 for ; Wed, 6 May 2015 10:36:09 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: [Bug 195816] [www/chromium] fix of handling of spaces in shell script Date: Wed, 06 May 2015 10:36:09 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: patch X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: yuri@rawbw.com X-Bugzilla-Status: New 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.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 10:36:09 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195816 --- Comment #1 from yuri@rawbw.com --- Maintainer timeout. -- You are receiving this mail because: You are the assignee for the bug. From owner-freebsd-chromium@FreeBSD.ORG Wed May 6 12:17:42 2015 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 543EBD6E for ; Wed, 6 May 2015 12:17:42 +0000 (UTC) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2011" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id C6A571D8E for ; Wed, 6 May 2015 12:17:41 +0000 (UTC) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.14.9/8.14.9) with ESMTP id t46CHdII055358 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Wed, 6 May 2015 12:17:39 GMT (envelope-from saper@saper.info) Received: from localhost (saper@localhost) by m.saper.info (8.14.9/8.14.9/Submit) with ESMTP id t46CHdRP055355 for ; Wed, 6 May 2015 12:17:39 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Wed, 6 May 2015 12:17:39 +0000 From: Marcin Cieslak To: chromium@freebsd.org Subject: gyp with BSD make? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 12:17:42 -0000 Hello, Has anybody tried or was there interest to modify gyp to generate BSDmakefiles that would automatically get our CC, CXX and other flags? ~Marcin From owner-freebsd-chromium@FreeBSD.ORG Wed May 6 13:11:11 2015 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 01DBE9B3 for ; Wed, 6 May 2015 13:11:11 +0000 (UTC) Received: from mail-ob0-x233.google.com (mail-ob0-x233.google.com [IPv6:2607:f8b0:4003:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BC54B13A3 for ; Wed, 6 May 2015 13:11:10 +0000 (UTC) Received: by obfe9 with SMTP id e9so6388851obf.1 for ; Wed, 06 May 2015 06:11:10 -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:message-id:subject :from:to:cc:content-type:content-transfer-encoding; bh=FvgxPHofUo2bc0N54lku9mUCYd04G//N2W8eo3t/A2Q=; b=l6ddh+K+qaz+GTUwy/DycfLoqQ8H/9QmUceOcg3XUoA9xyXUTJoTT6sviSoCUNzJcC yzvV28IK0wdZC/FokcZs3h6LsTSIAbcjLHogXRGPa6o8MNtPe4ljy4MvlyKKe4rOp045 8Rl0wAEE0iJu8TygMxXxIUlHOkbIeyqG46JnMi+7dtI6vNylFWG/M/i4AkGnOCYeKIAp i4WHhNZte93pB5hrja7xpWFdHL7LjtJSyvxRytaJVYTukZabnxPNA3nkAwKSaxEJnjtI Izv4wdQlSikqQNsWJJVp708vL7+f6CdBUctAmjJscSFojBhszB7HN2wbhFPHLeNQeOks Ft8g== MIME-Version: 1.0 X-Received: by 10.182.5.4 with SMTP id o4mr23655216obo.67.1430917870116; Wed, 06 May 2015 06:11:10 -0700 (PDT) Sender: r.c.ladan@gmail.com Received: by 10.60.155.212 with HTTP; Wed, 6 May 2015 06:11:10 -0700 (PDT) In-Reply-To: References: Date: Wed, 6 May 2015 15:11:10 +0200 X-Google-Sender-Auth: 3PBInX35g_zXk-ItkM_s8RQUOiM Message-ID: Subject: Re: gyp with BSD make? From: =?UTF-8?Q?Ren=C3=A9_Ladan?= To: Marcin Cieslak Cc: chromium@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 13:11:11 -0000 2015-05-06 14:17 GMT+02:00 Marcin Cieslak : > Hello, > > Has anybody tried or was there interest > to modify gyp to generate BSDmakefiles > that would automatically get our CC, CXX > and other flags? > That would be quite an endavour I think and make our Chromium less compatible with upstream. The configure step would indeed be a bit faster but I don't see any benefits for the main build step which takes the bulk of the time? Upstream Chromium was in the process of replacing GYP with GN but that stalled (to the point where it shall not be mentioned). Regards, Ren=C3=A9 From owner-freebsd-chromium@FreeBSD.ORG Wed May 6 23:40:18 2015 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 2C84B89E; Wed, 6 May 2015 23:40:18 +0000 (UTC) Received: from m.saper.info (m.saper.info [IPv6:2a01:4f8:a0:7383::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "m.saper.info", Issuer "Marcin Cieslak 2011" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id B984B1014; Wed, 6 May 2015 23:40:17 +0000 (UTC) Received: from m.saper.info (saper@m.saper.info [IPv6:2a01:4f8:a0:7383::]) by m.saper.info (8.14.9/8.14.9) with ESMTP id t46NeDX9080141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 6 May 2015 23:40:13 GMT (envelope-from saper@saper.info) Received: from localhost (saper@localhost) by m.saper.info (8.14.9/8.14.9/Submit) with ESMTP id t46NeCC8080138; Wed, 6 May 2015 23:40:13 GMT (envelope-from saper@saper.info) X-Authentication-Warning: m.saper.info: saper owned process doing -bs Date: Wed, 6 May 2015 23:40:12 +0000 From: Marcin Cieslak To: =?ISO-8859-15?Q?Ren=E9_Ladan?= cc: chromium@freebsd.org Subject: Re: gyp with BSD make? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: 8BIT X-BeenThere: freebsd-chromium@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Chromium issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 23:40:18 -0000 On Wed, 6 May 2015, René Ladan wrote: > 2015-05-06 14:17 GMT+02:00 Marcin Cieslak : > > Hello, > > > > Has anybody tried or was there interest > > to modify gyp to generate BSDmakefiles > > that would automatically get our CC, CXX > > and other flags? > > > That would be quite an endavour I think and make our Chromium less > compatible with upstream. > The configure step would indeed be a bit faster but I don't see any > benefits for the main build step which takes the bulk of the time? Thanks. I didn't think about Chromium, but there is a node-gyp tool used to build quite a number of node(.js) addons written in C/C++. I am now involved in making sure http://github.com/sass/node-sass runs fine on FreeBSD and building binaries; but I think we should have node-gyp in our ports tree, respecting CC/CXX and so on. On one hand I can patch it, on the other - since node addons are relatively simple to build with well-defined dependencies (v8, libuv, node) we could get or something we could refer to. > Upstream Chromium was in the process of replacing GYP with GN but that > stalled (to the point where it shall not be mentioned). iojs community was also discussing moving away from GYP (https://github.com/iojs/io.js/issues/133) but it seems that the tool is here to stay for now. So my goal are hundreds of small node projects that use node-gyp - most of them fail as-is because "g++" is assumed to be the compiler or other rather silly reasons. ~Marcin