From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7065 invoked by alias); 12 Apr 2016 20:17:29 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 6912 invoked by uid 89); 12 Apr 2016 20:17:28 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=direnth, UD:dirent.h, dirent.h, castro X-HELO: mail-wm0-f53.google.com Received: from mail-wm0-f53.google.com (HELO mail-wm0-f53.google.com) (74.125.82.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-GCM-SHA256 encrypted) ESMTPS; Tue, 12 Apr 2016 20:17:27 +0000 Received: by mail-wm0-f53.google.com with SMTP id l6so202604087wml.1 for ; Tue, 12 Apr 2016 13:17:26 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=AyZMKxrK+gKwwB3iTKoZvlnv7dR847cRClHRMKHC0FI=; b=cf8mUNbMoA/iMvPd02cW9E/MsszcEsbd3IUwFuOB1yloVm59xesltT+/TrjdbtqclC Qw7UgUvU00yc7z41ZW5l6SaPTwova6GqhSkjWKv4pB1nGwuMfJAf0yfEj0hOb/UdpyHU ABEiImn9U6PthvsHWFNl3TU70adJN8dwC1OetrTiZVI/qd6VQCVVO+D9ezYN4Ipq01zD my/vf0+Sej0h8l83129tK55/OtlccXatvapSIqVfc8dK+2G+nPTgrPmD8rq1ueI20nYr LC8G7cAjVA4yLZ7kFjTdCX2fOKwWgeHUs4JuzBq+fNPczVmlLhtv0f0HrbyLRT3a/Ejf 0F0Q== X-Gm-Message-State: AD7BkJIlI+eg2Q/VVKqJaRODDQlf/zXxjVP/GiVigBFQ4AaOFbiKFAcATly20g2tQTaGyA== X-Received: by 10.28.98.137 with SMTP id w131mr27046124wmb.30.1460492244046; Tue, 12 Apr 2016 13:17:24 -0700 (PDT) Received: from [192.168.2.109] (p5B1745A9.dip0.t-ipconnect.de. [91.23.69.169]) by smtp.googlemail.com with ESMTPSA id i206sm24470695wmf.1.2016.04.12.13.17.22 for (version=TLSv1/SSLv3 cipher=OTHER); Tue, 12 Apr 2016 13:17:22 -0700 (PDT) Subject: Re: 2.3.1(0.291/5/3): MAXNAMLEN too small To: cygwin@cygwin.com References: From: Marco Atzeri Message-ID: <570D57D1.4000809@gmail.com> Date: Tue, 12 Apr 2016 20:17:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-04/txt/msg00271.txt.bz2 On 12/04/2016 18:26, Arturo Castro wrote: > Hey all, > > I was compiling mg (the OpenBSD microemacs editor), and it was using MAXNAMLEN for filename completion. It had a bug because its value in Cygwin is 256 (too low!). We changed it to NAME_MAX which is 1024 and it works, but I think they should have the same value, so MAXNAMLEN should be updated to 1024, shouldn't it? > > CYGWIN_NT-6.1-WOW 2.3.1(0.291/5/3) i686, on Win7-64bit. > > Thanks! > on 2.5.1 cd /usr/include $ grep -rH MAXNAMLEN * ... dirent.h:#define MAXNAMLEN 1024 .... tcl8.5/unix/tclUnixPort.h:# define MAXNAMLEN 255 from where your build is taking MAXNAMLEN ? -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple