delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2003/12/21/10:08:28

X-Authentication-Warning: delorie.com: mail set sender to djgpp-workers-bounces using -f
From: Kbwms AT aol DOT com
Message-ID: <1ee.15fab781.2d171158@aol.com>
Date: Sun, 21 Dec 2003 10:08:08 EST
Subject: Re: isnanf et al
To: djgpp-workers AT delorie DOT com
MIME-Version: 1.0
X-Mailer: 8.0 for Windows sub 6021
Reply-To: djgpp-workers AT delorie DOT com

--part1_1ee.15fab781.2d171158_boundary
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

In a message dated 12/21/2003 9:23:18 AM Eastern Standard Time, 
rich AT phekda DOT gotadsl DOT co DOT uk writes:

> >
> >The fixes would entail modifying the 24 files in libm v204 that were 
> >mentioned in the email.  My suggestion is to revert to the sources for 
> >those files in libm v203.
> 
> That would break the build with gcc 3.3.x (and 3.2.x?). Those changes 
> were made, so that DJGPP 2.04 could be built with gcc 3.3.x (and 3.2.x?).
> 
> I think you posted a patch that #undef various things. Maybe applying 
> that patch and revert the gcc fixes in libm would work.
> 

Do you have a simple way to "revert the gcc fixes" or must the job be done 
manually?

Which files should be used as the base (or from set)?


--part1_1ee.15fab781.2d171158_boundary
Content-Type: text/html; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<HTML><FONT FACE=3Darial,helvetica><HTML><FONT  SIZE=3D3 PTSIZE=3D12 FAMILY=
=3D"SERIF" FACE=3D"Georgia" LANG=3D"0">In a message dated 12/21/2003 9:23:18=
 AM Eastern Standard Time, rich AT phekda DOT gotadsl DOT co DOT uk writes:<BR>
<BR>
<BLOCKQUOTE TYPE=3DCITE style=3D"BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT=
: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"></FONT><FONT  COLOR=3D"#000000"=
 BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR: #ffffff" SIZE=3D2 PTSIZE=3D10 F=
AMILY=3D"SANSSERIF" FACE=3D"Arial" LANG=3D"0">&gt;<BR>
&gt;The fixes would entail modifying the 24 files in libm v204 that were <BR=
>
&gt;mentioned in the email.&nbsp; My suggestion is to revert to the sources=20=
for <BR>
&gt;those files in libm v203.<BR>
<BR>
That would break the build with gcc 3.3.x (and 3.2.x?). Those changes <BR>
were made, so that DJGPP 2.04 could be built with gcc 3.3.x (and 3.2.x?).<BR=
>
<BR>
I think you posted a patch that #undef various things. Maybe applying <BR>
that patch and revert the gcc fixes in libm would work.<BR>
</BLOCKQUOTE><BR>
</FONT><FONT  COLOR=3D"#000000" BACK=3D"#ffffff" style=3D"BACKGROUND-COLOR:=20=
#ffffff" SIZE=3D3 PTSIZE=3D12 FAMILY=3D"SERIF" FACE=3D"Georgia" LANG=3D"0"><=
BR>
Do you have a simple way to "revert the gcc fixes" or must the job be done m=
anually?<BR>
<BR>
Which files should be used as the base (or from set)?<BR>
<BR>
</FONT></HTML>
--part1_1ee.15fab781.2d171158_boundary--

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019