From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Jason@zx2c4.com Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 3e2932c2 for ; Sat, 25 Aug 2018 05:07:12 +0000 (UTC) Received: from frisell.zx2c4.com (frisell.zx2c4.com [192.95.5.64]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 6c1b42a8 for ; Sat, 25 Aug 2018 05:07:12 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 52eaf19a for ; Sat, 25 Aug 2018 05:05:58 +0000 (UTC) Received: by frisell.zx2c4.com (ZX2C4 Mail Server) with ESMTPSA id f8c06e89 (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128:NO) for ; Sat, 25 Aug 2018 05:05:57 +0000 (UTC) Received: by mail-oi0-f42.google.com with SMTP id c190-v6so18848706oig.6 for ; Fri, 24 Aug 2018 22:20:25 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "Jason A. Donenfeld" Date: Fri, 24 Aug 2018 23:20:12 -0600 Message-ID: Subject: Re: wireguard-android build error To: dcow@eero.com Content-Type: text/plain; charset="UTF-8" Cc: WireGuard mailing list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Yes, right now I make use of insane flags of GNU coreutil's ls(1). I can probably replace these with something BSD compatible instead, like I did for the iOS bridge code, which does something similar.