From owner-freebsd-chromium@FreeBSD.ORG  Tue Mar  4 19:23:55 2014
Return-Path: <owner-freebsd-chromium@FreeBSD.ORG>
Delivered-To: freebsd-chromium@FreebSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 2CF119A6
 for <freebsd-chromium@FreebSD.org>; Tue,  4 Mar 2014 19:23:55 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id DD116D24
 for <freebsd-chromium@FreebSD.org>; Tue,  4 Mar 2014 19:23:54 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <gofc-freebsd-chromium@m.gmane.org>)
 id 1WKuwM-0004Mk-5I
 for freebsd-chromium@FreebSD.org; Tue, 04 Mar 2014 20:23:46 +0100
Received: from a91-154-115-217.elisa-laajakaista.fi ([91.154.115.217])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <freebsd-chromium@FreebSD.org>; Tue, 04 Mar 2014 20:23:46 +0100
Received: from rakuco by a91-154-115-217.elisa-laajakaista.fi with local
 (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00
 for <freebsd-chromium@FreebSD.org>; Tue, 04 Mar 2014 20:23:46 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: freebsd-chromium@FreebSD.org
From: Raphael Kubo da Costa <rakuco@FreeBSD.org>
Subject: Re: Native build of chromium/webrtc source requires full path in
 /usr/local
Date: Tue, 04 Mar 2014 21:23:32 +0200
Lines: 16
Message-ID: <867g89n4y3.fsf@orwell.Elisa>
References: <CA+WntOu7i5C+gKO_uNNFoEKs4oYVSipf8sN2CFiQb9oXtxNHLA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: a91-154-115-217.elisa-laajakaista.fi
User-Agent: Gnus/5.13001 (Ma Gnus v0.10) Emacs/24.3 (berkeley-unix)
Cancel-Lock: sha1:PErv5ZTwQGoCUDOdCt7pnOMPNUU=
X-BeenThere: freebsd-chromium@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: FreeBSD-specific Chromium issues <freebsd-chromium.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-chromium/>
List-Post: <mailto:freebsd-chromium@freebsd.org>
List-Help: <mailto:freebsd-chromium-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-chromium>, 
 <mailto:freebsd-chromium-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Mar 2014 19:23:55 -0000

Joe Nosay <superbisquit@gmail.com> writes:

> I've had to rewrite the paths on h, c, and cc files for the build to
> continue. The assumption, and hopefully not a faulty one, is that the port
> Makefile can be edited so that any build from the Google Chrome Framework
> can be ported to FreeBSD. Fewer files than thought of need to be changed;
> and, even on the ChromeOS build, I have noticed that vfs.h references can
> be replaced with NFS references- it's basically the same thing, which may
> be good if someone is interested in having a ChromeOS Linux compatibility
> layer.
>
> Will the assumption work; and, if so, then what parts will I need to work
> on?

I couldn't really understand your question. Can you post an example of a
change you had to make?