From owner-freebsd-current@FreeBSD.ORG Sat Mar 8 01:30:03 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B72C18E4; Sat, 8 Mar 2014 01:30:03 +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)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4092483D; Sat, 8 Mar 2014 01:30:03 +0000 (UTC) Received: by mail-qa0-f49.google.com with SMTP id cm18so4297232qab.22 for ; Fri, 07 Mar 2014 17:30:02 -0800 (PST) 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=IkkAbCe2wMbsRfTpoteKhpSGIAU3/kz2luTXzDR48tA=; b=tzPrR1nkSCqgoPQr1xXdfgtmAonshN7A4nyKHzK5BM1bB8ZyQwY8Rp3375gC5NmDJI 1u9qR0F8+L9j2kS2UrregwlZM4pOCdHk9T5lZzV2oR39h0sSnr4xfbGKvIa5f4L7ktdY tV/B2B3FfYGxWUDPn6PxFhXOK/Le/vGPKlgjdCKpYIqHb5Mi2j4xtiNH8xYaC9aNrrIY eUvkywrGTEtycbuFu6En1qlUesCT8LmADkqDUm3JIwV+aoO332bLkOjkPLUjQmztkpzv m19X6VCHMDtCExYqIXqUn6tTeMCRIRO2F50/p3642ANQMT59UzeIW5q/wovKKw79Kopv RO/A== MIME-Version: 1.0 X-Received: by 10.224.12.14 with SMTP id v14mr25332889qav.73.1394242202442; Fri, 07 Mar 2014 17:30:02 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.8.137 with HTTP; Fri, 7 Mar 2014 17:30:02 -0800 (PST) In-Reply-To: <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> <22DB6968-3DCC-4B35-9210-891DB28D7CE7@gmail.com> Date: Fri, 7 Mar 2014 17:30:02 -0800 X-Google-Sender-Auth: KlOsVi0_d4sTW_cMdafIvNw8Q2s Message-ID: Subject: Re: warning: filename ends with '.', which is not allowed on Windows: 'tools/test/sort/bigtest/q-1.024.003.' From: Adrian Chadd To: Warner Losh Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Rui Paulo , David Chisnall , Eitan Adler , FreeBSD Current , 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: Sat, 08 Mar 2014 01:30:03 -0000 On 7 March 2014 15:25, Warner Losh wrote: > > 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: >>> >>>> On 7 Mar 2014, at 16:41, Rui Paulo wrote: >>>> >>>>> 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 prob= lem. >>>>> >>>>> Is this something we want to support? >>>> >>>> Yes, definitely. Building FreeBSD on other platforms is one of the re= quests we get very often from embedded systems vendors. Cheap virtualisati= on 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. T= o my knowledge, no one is working on it, but we should aim to make life eas= y for whoever does... >>> >>> I guess I should clarify: I wasn't talking about cross building in gene= ral, but specifically on Windows. It's far easier to setup a case-sensitiv= e file system on OS X and cross build FreeBSD from there than it is on Wind= ows. >> >> 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't case sensitivity or file names ending in dot. The rea= l issue is that our build just isn't setup for this at the moment and it wo= uld 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 b= efore we could have even a tiny chance of doing this... > are those issues documented anywhere? :) -a