From owner-freebsd-current@FreeBSD.ORG Fri Mar 7 23:25:22 2014 Return-Path: Delivered-To: freebsd-current@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 CDFDE4C5 for ; Fri, 7 Mar 2014 23:25:22 +0000 (UTC) Received: from mail-pd0-f171.google.com (mail-pd0-f171.google.com [209.85.192.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9BAB1C3D for ; Fri, 7 Mar 2014 23:25:22 +0000 (UTC) Received: by mail-pd0-f171.google.com with SMTP id r10so4616893pdi.16 for ; Fri, 07 Mar 2014 15:25:16 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=bYJzRCC38m3KyNRTpEwDtuSCvbvaCUyACTTExAG/uUM=; b=AsiYLF/GpM0fZ8XlpwvsiEYnhJ53ROESF3Nl2WZ+3zZ4sjw04HmGIrg7CNNyVNigcw lwKzgGZAtf1Ndra8fspR/wxYdr9jh8yrt/vYrh7F+Q17KpLPO4XtovrvioEn17/5Q62k vixRB+Mxh8R3WjoXg3hLr6pq43YPOCov3wynQ4s9EMTtV4tO5B1iGFG7Flst3rorkLPe 5qXBDq+Cwglki5tN0bi0cIBAw5vwR3MyRxx7QUjtCHFq70gQZAfcTuE7V4WoVFOO+18a p7/j/AEQcAno2+5BxI5gC/zFnvBeAolq0vdtUHl+gePpAIKbzXPC/OZzRKgHZ3tVUqVh sdHA== X-Gm-Message-State: ALoCoQnNjYyuwME7DnPyRK9pmcQEeIDT3mcbVdVBEYzoHdE9BDsCsw8JWK2CT4DGc9KOu8zPsVea X-Received: by 10.66.155.102 with SMTP id vv6mr25133796pab.89.1394234716187; Fri, 07 Mar 2014 15:25:16 -0800 (PST) Received: from lgmac-cvenus.corp.netflix.com (dc1-prod.netflix.com. [69.53.236.251]) by mx.google.com with ESMTPSA id gj9sm40681051pbc.7.2014.03.07.15.25.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Mar 2014 15:25:15 -0800 (PST) Sender: Warner Losh Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: warning: filename ends with '.', which is not allowed on Windows: 'tools/test/sort/bigtest/q-1.024.003.' From: Warner Losh In-Reply-To: Date: Fri, 7 Mar 2014 16:25:12 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <22DB6968-3DCC-4B35-9210-891DB28D7CE7@gmail.com> References: <5319757E.1060301@freebsd.org> <821C2C51-604E-43E0-9796-300996B81B41@FreeBSD.org> <40D5835F-679A-4ED9-AFC4-8E80773E5D82@FreeBSD.org> <3D879607-7AB5-475E-86DC-BBD97FC7269D@felyko.com> To: Eitan Adler X-Mailer: Apple Mail (2.1874) Cc: David Chisnall , FreeBSD Current , Rui Paulo , Rui Paulo , David Xu X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2014 23:25:23 -0000 On Mar 7, 2014, at 4:12 PM, Eitan Adler wrote: > On 7 March 2014 13:50, Rui Paulo wrote: >> On 7 Mar 2014, at 10:38, David Chisnall wrote: >>=20 >>> On 7 Mar 2014, at 16:41, Rui Paulo wrote: >>>=20 >>>> On 6 Mar 2014, at 23:30, David Xu wrote: >>>>> it seems filename ended with a dot is illegal on Windows, if = someone >>>>> wants to check out freebsd source code on Windows, it will be a = problem. >>>>=20 >>>> Is this something we want to support? >>>=20 >>> Yes, definitely. Building FreeBSD on other platforms is one of the = requests we get very often from embedded systems vendors. Cheap = virtualisation has made it less urgent (they can just stick a FreeBSD = VirtualBox VM on their workstations), but it's definitely something we'd = like eventually. To my knowledge, no one is working on it, but we = should aim to make life easy for whoever does... >>=20 >> I guess I should clarify: I wasn=92t talking about cross building in = general, but specifically on Windows. It=92s far easier to setup a = case-sensitive file system on OS X and cross build FreeBSD from there = than it is on Windows. >=20 > Over 50% of the people that come to FreeBSD.org run windows. If it is > possible to support building on windows, we should try. The big issue isn=92t case sensitivity or file names ending in dot. The = real issue is that our build just isn=92t setup for this at the moment = and it would be a big lift to make it work at all. Sure, go ahead and = fix this minor flea-bite of an issue, but there are several large = elephant-sized issues before we could have even a tiny chance of doing = this... Warner