delorie.com/archives/browse.cgi | search |
X-Authentication-Warning: | delorie.com: mail set sender to djgpp-workers-bounces using -f |
X-Recipient: | djgpp-workers AT delorie DOT com |
DKIM-Signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; |
d=gmail.com; s=20120113; | |
h=mime-version:x-received:in-reply-to:references:date:message-id | |
:subject:from:to:content-type; | |
bh=73GRU6Po72YgJrb4OG41gqx+Y1DwvUzV3AkRZ60ZwuY=; | |
b=QEsGFavW3H5Yqe7RD/GVY68A9QDq8wsjuOHX/RtqQHukKEl50yQ/E2bz4Hx+JwRhp5 | |
61uy2siV4HzfbA8pObunEjdLz88G2e/cQinUFpyHUoVf8QVIUlPLl3xxFSsoTV1fGUnc | |
C5plJN66cAn6x4etFcp9DY4ueYxUdN1u6uIO2eK8dKM3aXl/YTw8CKSzGOnTdMESPCvC | |
uUNgIbMN95lyh9aVNPv/DB9N0bEKffJBR+YF2EKEmDjfemcUw1jMwJBlJrNl18Nky3wa | |
kahcaNqvWsH3W67J/h1gBMKtmg1KdLT0jstJ/88Qoom82NecJU1aDAEUqDc+WzdY6I0W | |
MvFw== | |
MIME-Version: | 1.0 |
X-Received: | by 10.60.31.170 with SMTP id b10mr5402066oei.34.1363819656100; |
Wed, 20 Mar 2013 15:47:36 -0700 (PDT) | |
In-Reply-To: | <CAA2C=vB08rhgRyL-WX+vgXQKxkh4-bXxYZRG+8NyL1HzaUKafA@mail.gmail.com> |
References: | <5140A042 DOT 9050805 AT iki DOT fi> |
<CAA2C=vB08rhgRyL-WX+vgXQKxkh4-bXxYZRG+8NyL1HzaUKafA AT mail DOT gmail DOT com> | |
Date: | Wed, 20 Mar 2013 17:47:35 -0500 |
Message-ID: | <CAA-ihx-wzMncQTikJZ2yFuSCzz4ebBUneNcm5iO4DygvL519aw@mail.gmail.com> |
Subject: | Re: About new DJGPP v2.04 beta |
From: | Rugxulo <rugxulo AT gmail DOT com> |
To: | djgpp-workers AT delorie DOT com |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
Hi, On Mon, Mar 18, 2013 at 3:54 AM, Ozkan Sezer <sezeroz AT gmail DOT com> wrote: > On Wed, Mar 13, 2013 at 5:50 PM, Andris Pavenis <andris DOT pavenis AT iki DOT fi> wrote: > >> I guess we should make a new DJGPP v2.04 beta soon >> and most likely do a release also sometimes >> in not too far future I still say just refreshing DJDEV204.ZIP to latest CVS would be easiest (and just rename old one to *.OLD but keep it online just in case). >> Some examples where it could be needed: >> - use of upcoming gcc-4.8.0 (changes for >> 1 header file needed, already in CVS) Which header exactly? If it's only such a minor change, a manual patch would be easier (unless DJDEV* is updated on mirrors). >> - GMP-5.1.X does not compile without trunc() >> which was recently added to CVS. Really only >> 'make check' fails, but one cannot relay >> that library will work OK without that Could always just add a local patch inside the .ZIP. But most DJGPP projects aren't using GMP, are they? >> There will most likely be no ports of these >> for DJGPP v2.03. Eek. Well, are there are huge reasons to not use 2.04 besides just a bit less testing in all environments?? (I know some people still use 2.03p2, but are there any diehards who refuse, or can't, switch to 2.04? Eli???) >> for gcc-4.8.0: something seems to be broken >> with bash-2.0.4 which prevents building GCC >> for DJGPP v2.03. Unfortunately bash-2.0.5b from >> beta also cannot be used in this case. What exactly happens and where and when? I admit our ports of Bash are "quirky", but they seem to "mostly" work. > It would have been very nice if the src were made somehow configurable > to leave out undesired features, e.g. symlinks getting in the way upon > every fopen() & co, FILE_DESC_DIRECTORY, and the likes. Why? Is there a bug resulting from this? Is it too slow? Or are you just unhappy that the libc is slightly larger?
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |