On Friday 06 May 2005 09:01 am, Joseph S. Myers wrote:
> On Fri, 6 May 2005, Bruce Korb wrote:
>
> > That is, indeed, very bizarre. I opened that file and the lines that
> > are supposed to be continued with backslashes ended with: \\\n\
> > which is correct. After you extract it, you have: \\
On Fri, 6 May 2005, Bruce Korb wrote:
> That is, indeed, very bizarre. I opened that file and the lines that
> are supposed to be continued with backslashes ended with: \\\n\
> which is correct. After you extract it, you have: \n\
> which is not correct. I am at a loss as to what to sugge
On Thursday 05 May 2005 10:26 pm, Frank Heckenbach wrote:
> > I do not know where you got your code, but what you have is not what
> > was released and not what is under CVS. Your patch to fixincl.x
> > will correct the deviation from the released source. I just downloaded
> > the distro from ftp.
Bruce Korb wrote:
> Frank wrote:
> > gcc-3.4.3 contains an incorrect header fix for "the __FD_ZERO macro
> > present in glibc 1.x". The file installed in
> > /lib/gcc/i686-pc-linux-gnulibc1/3.4.3/include/gnu/types.h
> > contains the following, with spurious double-backslashes:
> [[...]]
> > This p
Frank wrote:
> gcc-3.4.3 contains an incorrect header fix for "the __FD_ZERO macro
> present in glibc 1.x". The file installed in
> /lib/gcc/i686-pc-linux-gnulibc1/3.4.3/include/gnu/types.h
> contains the following, with spurious double-backslashes:
[[...]]
> This patch fixes the issue for me:
>
>
