I have been noticing the following error in trunk and in branch.
It looks look in libstdcv3 signbit,
Has it been reported yet?
/home/sherlock/gcc/o/gcc/xgcc -B/home/sherlock/gcc/o/gcc/
-B/usr/local/i686-pc-c
ygwin/bin/ -isystem
/usr/local/i686-pc-cygwin/i
nclude -isystem / -DHAVE_CNFIG_H
-I. -I/.
-I -g -c
////gcc-4
-o signbit.o
In file included from
32:
error:
conflicti
ng types for 'ieee_double_shape_type'
error:
previous
declaration of 'ieee_double_shape_type' was here
error:
conflicti
ng types for 'ieee_long_double_shape_type'
error:
previous
declaration of 'ieee_long_double_shape_type' was here
error:
conflicti
ng types for 'ieee_quad_double_shape_type'
error:
previous
declaration of 'ieee_quad_double_shape_type' was here
make[3]: [signbit.lo] Error 1
make[3]: Leaving directory
`/
math'
make[2]: [all-recursive] Error 1
make[2]: Leaving directory
`/'
make[1]: [all] Error 2
make[1]: Leaving directory
`/'
make: [all-target-libstdcv3] Error 2
sherlock@mars ~/gcc/o
$

Bobby McNulty wrote:

I have been noticing the following error in trunk and in branch.

I get no such error when compiling the trunk.

/home/sherlock/gcc/o/gcc/xgcc -B/home/sherlock/gcc/o/gcc/
-B/usr/local/i686-pc-c
ygwin/bin/ -isystem
/usr/local/i686-pc-cygwin/i
nclude -isystem / -DHAVE_CNFIG_H
-I. -I/.
-I -g -c
////gcc-4
-o signbit.o
In file included from

32:
error:
conflicti
ng types for 'ieee_double_shape_type'

It looks like what is happening is BYTERDER isn't getting defined
correctly. This is supposed to be taken care of by the sys/param.h
header of the target, which Cygwin does provide correctly. It looks
like for some reason gcc isn't picking this up in your case. Are you
doing a native or a cross? What configure options are you using?

Brian

Brian Dessent wrote:

>Bobby McNulty wrote:
>

>
>>I have been noticing the following error in trunk and in branch.
>
>>
>
>I get no such error when compiling the trunk.
>

>
>>/home/sherlock/gcc/o/gcc/xgcc -B/home/sherlock/gcc/o/gcc/
B/usr/local/i686-pc-c
>>ygwin/bin/ -isystem
>>/usr/local/i686-pc-cygwin/i
>>nclude -isystem / -DHAVE_CNFIG_H
I. -I/.
>-I -g -c
>>////gcc-4
>-o signbit.o
>>In file included from
>>
>>32:
>error:
>>conflicti
>>ng types for 'ieee_double_shape_type'
>
>>
>
>It looks like what is happening is BYTERDER isn't getting defined
>correctly. This is supposed to be taken care of by the sys/param.h
>header of the target, which Cygwin does provide correctly. It looks
>like for some reason gcc isn't picking this up in your case. Are you
>doing a native or a cross? What configure options are you using?
>
>Brian
>
>

native.
Might be the snapshots.
anyway, /gcc-4_0-branch/configure
straight like that.
No other options.
trunk is the sameway.
Bobby

Brian Dessent wrote:

/home/sherlock/gcc/o/gcc/xgcc -B/home/sherlock/gcc/o/gcc/
-B/usr/local/i686-pc-c
ygwin/bin/ -isystem
/usr/local/i686-pc-cygwin/i
nclude -isystem / -DHAVE_CNFIG_H
-I. -I/.
-I -g -c
////gcc-4
-o signbit.o
In file included from

32:
error:
conflicti
ng types for 'ieee_double_shape_type'

It looks like what is happening is BYTERDER isn't getting defined
correctly. This is supposed to be taken care of by the sys/param.h
header of the target, which Cygwin does provide correctly. It looks
like for some reason gcc isn't picking this up in your case. Are you
doing a native or a cross? What configure options are you using?

This is caused by this change:
<>.
This modified include/endian.h to only conditionally define BYTERDER
etc. if __USE_BSD is defined, whereas before in newlib's
machine/endian.h
<>
they were defined unconditionally.

Thus if you build gcc with the 1.5.18 version of cygwin and its headers
you don't run into this, but if you try to use a snapshot that contains
this change you get the above error.

Brian

Bobby McNulty wrote:
Since this is just staying on the cutting edge of programming, I am only
going to use release cygwin1.dll.
Waiting for cygwin 1.5.19
FYI,