DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4BS0FJhc1142559 Authentication-Results: delorie.com; dmarc=none (p=none dis=none) header.from=delorie.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=delorie.com X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 4BS0FJ5x1142539 Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=gmail.com Authentication-Results: delorie.com; spf=pass smtp.mailfrom=gmail.com DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 4BS0FJ5x1142539 Authentication-Results: delorie.com; dkim=pass (2048-bit key, unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20230601 header.b=IWgUyRln X-Recipient: djgpp AT delorie DOT com X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1735344917; x=1735949717; darn=delorie.com; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id:from :to:cc:subject:date:message-id:reply-to; bh=wUT9BEUp7F2AsFmIa9xWQURU+9fHeGc3wuAQ46+by9I=; b=IWgUyRln9PEFiJ3ZhXr16rM9Fl0gtYDyPnjLYMrtp0xK3JEbVRHDcIiYD0zLmwGAo9 oiYVpK3Jzg+k4fK0E95kzewkqZOxvfmlZyMsZwqWmGOqEDNHUDeQ5PI4jKa2BZFmUf6U kb84VmAg8q4HJHZ/cEq8MnYPY5wy11KueOfzoXIgYEj4ePzbG3qkv7O+NvpzoVOM37Qj WtFsz+s+S+f+EIU+xN+F1qeWC4Kks9FMw7B6mLb4zV92TAFT1WybYoWjKL932Strk0zW wRnQdIUgKDco4ARXZxmxJXpj8vTlH3zO8+q6xOPdHVefFCsQfKNT6Ym1oAZJQeOV5EwB 8Csw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1735344917; x=1735949717; h=content-transfer-encoding:in-reply-to:from:content-language :references:to:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=wUT9BEUp7F2AsFmIa9xWQURU+9fHeGc3wuAQ46+by9I=; b=DT6H567kuy6x2aw1Is/6EojD9ozoruNR9P2MbP1mWLO1OQFGF670o8x/07CBU0jZS4 PnwqrD+pJ1Lk4iSJRlKy2qaq2rv1O4K1ONUUP+5giyZVynTTxOL9BwRJ6huagKQPOHaR pft5ZKfpf05elds7O9eFHQyigJ4S0HRgEyLcX7l9XeFmNo9G0F3tsSjKDYLweO16XYo+ +onVEeoXDu/GbXFFgPofZnrvBtZMfWufhii707wkRFBeQc4RWV68tSvAk+IPk+E7CL7p MdXEnCyYkKT2ZkJN4sGrRF/2w2ncBpgtFHj9pH6ZxDX+PASV2Wh/ONHfLD8X96yGdCvx 7BiA== X-Gm-Message-State: AOJu0YzeQDbp6ZllUurtxcCr+HBJtEEGIaE3nlSWaimUuEyllmI1QM10 XH6nhh52RyB1nPZXi30ISKGhhPV13oPJuWb2bYxz38rcf9fqhXEr1M8JcA== X-Gm-Gg: ASbGncuE44xRAQPEC4jl2TjrqsARrpj+NN2xE0WBS4CU0VVIeWdlwJRzPTZ2rLVyrax CEouyovcU8ftxHFltvXo/YC2gUs+vD9aKwZ2Svv7pXBo0II6GTerF7NU75DCPAhFgPAvqikQBUV 8CdZfgYStyg5EvXYakMOoFvTmFoxmEWcH3AWU5ANsfdyuuJb4+a4pnyUIHUJtVyQeoIJELE3I3h yP4YGFPMfz/lqueZ4AUMLm5UXYDkIDhNz/kIyGFnLEidBqjU6CiQcSyD4NhTKoPBuLhHcaURFgC 78N9mtxyT1BSTEUnrjl9aZRs5DJL4p4SbSUCxxt4as27TGYiFlI= X-Google-Smtp-Source: AGHT+IFjMuwHKL9ZTlJ7wUUIjIoKFKcaCZAgDldSC4mOEDLLbhOeSiTE4gNoadVWyPkxqIQwPbcIlA== X-Received: by 2002:a05:6214:29cc:b0:6d4:238e:35b0 with SMTP id 6a1803df08f44-6dd2334b27amr470289826d6.17.1735344917482; Fri, 27 Dec 2024 16:15:17 -0800 (PST) Message-ID: Date: Fri, 27 Dec 2024 19:15:16 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Fwd: [Texinfo] Remove DJGPP support files? To: djgpp AT delorie DOT com References: Content-Language: en-US From: "Frank Sapone (emoaddict15 AT gmail DOT com) [via djgpp AT delorie DOT com]" In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Reply-To: djgpp AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk Hi Gavin, I personally am not using it.  However, a fair number of GNU-related utilities that have DJGPP build options are mostly done on cross compilers or Win9x dos boxes because, as you mentioned, it's practically impossible to build a lot of this stuff now without long file name support. It's the holidays so we may not hear from anyone else for a couple of weeks, but I do know there is one person on here who does keep up with compiling many of the tools.  I believe it's Andre but I am not sure offhand. Thanks, Frank On 12/23/2024 3:58 PM, Gavin Smith (gavinsmith0123 AT gmail DOT com) [via djgpp AT delorie DOT com] wrote: > Hello DJGPP users, I was advised to ask you about whether anybody > uses recent Texinfo releases on DJGPP. We are considering removing > what attempts at supporting DJGPP currently exist. See my mail below > to the Texinfo development list. > > It is likely we will remove attempts at supporting DJGPP unless there is > evidence that somebody is actually using it successfully. > > Best regards > Gavin > > ----- Forwarded message from Gavin Smith ----- > > Date: Mon, 23 Dec 2024 17:40:17 +0000 > From: Gavin Smith > To: bug-texinfo AT gnu DOT org > Subject: Remove DJGPP support files? > > There is still a top-level directory in the Texinfo distribution > called "djgpp". I don't remember any reports from anybody building > or running Texinfo on DJGPP. All the mailing list posts I could find > on it are from over 10 years ago. I don't know if Texinfo would still > build on this platform. > > We still have a comment in configure.ac: > > AC_CONFIG_HEADERS([config.h:config.in])dnl Keep filename to 8.3 for MS-DOS. > > I doubt this is relevant any more as many of the filenames are much longer, > especially in texi2any. I very much doubt that the package could be built > on a system with 8.3 length filenames (although I am not sure to what > extent DJGPP programs could use longer filenames). > > Unless there are reports that a recent release of Texinfo acually builds > and runs on DJGPP (most relevant would be releases with the Perl texi2any, > after version 5.0) and that this is useful to somebody, then I would > propose removing the code that purports to support it. This would be > the "djgpp" subdirectory and a small amount of platform-conditional > code elsewhere. > > ----- End forwarded message -----