Cygwin build failure

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Cygwin build failure

Paul Thomas-10
David,

Knowing that you do regular Cygwin builds of gcc, I wonder can you advise
me, please?  For the better part of a month, I have not succeeded in
building gcc from the CVS tree under Cygwin_NT-5.1 for one reason or
another.

I now get:

_________________________________________________________________
.............
/cygdrive/d/gcc-cvs/build/./gcc/xgcc -B/cygdrive/d/gcc-cvs/build/./gcc/ -B/cygdr
ive/d/irun-cvs/i686-pc-cygwin/bin/ -B/cygdrive/d/irun-cvs/i686-pc-cygwin/lib/
 -i
system /cygdrive/d/irun-cvs/i686-pc-cygwin/include -isystem
/cygdrive/d/irun-cvs
/i686-pc-cygwin/sys-include -DHAVE_CONFIG_H -I. -I../../../gcc/libgfortran -I.
 -
iquote../../../gcc/libgfortran/io -std=gnu99 -Wall -Wstrict-prototypes -Wmissing
-prototypes -Wold-style-definition -Wextra -Wwrite-strings -O2 -g -O2 -c
../../.
./gcc/libgfortran/runtime/environ.c -o environ.o
In file included from /usr/include/cygwin/types.h:21,
                 from /usr/include/sys/types.h:365,
                 from ../../../gcc/libgfortran/libgfortran.h:74,
                 from ../../../gcc/libgfortran/runtime/environ.c:35:
/usr/include/stdint.h:18: error: conflicting types for 'int8_t'
../../../gcc/libgfortran/libgfortran.h:63: error: previous declaration of
'int8_
t' was here
/usr/include/stdint.h:20: error: conflicting types for 'int32_t'
../../../gcc/libgfortran/libgfortran.h:65: error: previous declaration of
'int32
_t' was here
/usr/include/stdint.h:28: error: conflicting types for 'uint32_t'
../../../gcc/libgfortran/libgfortran.h:69: error: previous declaration of
'uint3
2_t' was here
make[2]: *** [environ.lo] Error 1
make[2]: Leaving directory
`/cygdrive/d/gcc-cvs/build/i686-pc-cygwin/libgfortran
'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/cygdrive/d/gcc-cvs/build/i686-pc-cygwin/libgfortran
'
make: *** [all-target-libgfortran] Error 2
_________________________________________________________________
If I comment out the definitions of the integer types in gfortran.h, I get
instead, a even more uninformative (for me that is):

../../../gcc/libgfortran/runtime/environ.c: In function 'init_integer':
../../../gcc/libgfortran/runtime/environ.c:104: error: invariant not
recomputed
when ADDR_EXPR changed
&_ctype_D.1954[1];

../../../gcc/libgfortran/runtime/environ.c:104: internal compiler error:
verify_
stmts failed.
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
make[2]: *** [environ.lo] Error 1
make[2]: Leaving directory
`/cygdrive/d/gcc-cvs/build/i686-pc-cygwin/libgfortran
'
make[1]: *** [all] Error 2
make[1]: Leaving directory
`/cygdrive/d/gcc-cvs/build/i686-pc-cygwin/libgfortran
'
make: *** [all-target-libgfortran] Error 2

Since I am also failing to build from the cvs tree on Red Hat as well, it is
not proving to be a very productive day.  BTW, the 20050515 snapshot builds
fine on both.

Where am I going wrong?

Paul T


Reply | Threaded
Open this post in threaded view
|

Re: Cygwin build failure

FX Coudert
> Knowing that you do regular Cygwin builds of gcc, I wonder can you advise
> me, please?  For the better part of a month, I have not succeeded in
> building gcc from the CVS tree under Cygwin_NT-5.1 for one reason or
> another.

That's PR 21766 (appropriately named "Bootstrap failure on
i686-pc-cygwin"). Opened almost a month ago. GCC mainline doesn't
build on cygwin or mingw since that time.

Seeing that almost no comment had been made by the maintainers on it,
and no correct patch proposed, it looks like we're gonna have to live
with it for a long time... :(

Short-time answer: patches provided in bugzilla don't fix the problem,
but they should enable you to build successfully (and then, the
problem shouldn't really appear in gfortran).

Long-time answer: well, I cc this mail to [hidden email] and
maintainers so that we can have a hint whether this is going to be
fixed soon or not.

FX

PS: Detailled info on your problems:

> /usr/include/stdint.h:18: error: conflicting types for 'int8_t'
> ../../../gcc/libgfortran/libgfortran.h:63: error: previous declaration of
> 'int8_t' was here

This one is because you're reconfiguring in a non-empty tree. There is
a PR number for it, but I don't remember it...

> ../../../gcc/libgfortran/runtime/environ.c:104: error: invariant not
> recomputed when ADDR_EXPR changed
> &_ctype_D.1954[1];

This one is due to the bootstrap failure (PR 21766).
Reply | Threaded
Open this post in threaded view
|

Re: Cygwin build failure

Andrew Pinski
In reply to this post by Paul Thomas-10

On Jun 20, 2005, at 12:25 PM, Paul Thomas wrote:

> David,
>
> Knowing that you do regular Cygwin builds of gcc, I wonder can you
> advise me, please?  For the better part of a month, I have not
> succeeded in building gcc from the CVS tree under Cygwin_NT-5.1 for
> one reason or another.
> ../../../gcc/libgfortran/runtime/environ.c: In function 'init_integer':
> ../../../gcc/libgfortran/runtime/environ.c:104: error: invariant not
> recomputed
> when ADDR_EXPR changed
> &_ctype_D.1954[1];

This is PR 21766.

-- Pinski

Reply | Threaded
Open this post in threaded view
|

Re: Cygwin build failure

Paul Thomas-10
In reply to this post by FX Coudert
Thanks Francois-Xavier and Andrew for replying,

> That's PR 21766 (appropriately named "Bootstrap failure on
> i686-pc-cygwin"). Opened almost a month ago. GCC mainline doesn't
> build on cygwin or mingw since that time.

> Seeing that almost no comment had been made by the maintainers on it,
> and no correct patch proposed, it looks like we're gonna have to live
> with it for a long time... :(

Ah..., I naively thought that it would have been fixed whilst I was away!
What a bloody nuisance.

PS: Detailled info on your problems:

> This one is because you're reconfiguring in a non-empty tree. There is
> a PR number for it, but I don't remember it...

I thought that it was empty; I'l try again.

Thanks

Paul T


Reply | Threaded
Open this post in threaded view
|

RE: Cygwin build failure

Billinghurst, David (CALCRTS)
In reply to this post by Paul Thomas-10
> From: Paul Thomas
>
> David,
>
> Knowing that you do regular Cygwin builds of gcc, I wonder
> can you advise
> me, please?  For the better part of a month, I have not succeeded in
> building gcc from the CVS tree under Cygwin_NT-5.1 for one reason or
> another.
>

...
 
> Where am I going wrong?
>
> Paul T
>

I have a patch of Danny Smith's in my local tree
http://gcc.gnu.org/ml/gcc-patches/2005-05/msg00009.html
(This is noted in my test results).
There is a later patch that I haven't had time to investigate.
This is PR 21766

        David


NOTICE
This e-mail and any attachments are private and confidential and may contain privileged information. If you are not an authorised recipient, the copying or distribution of this e-mail and any attachments is prohibited and you must not read, print or act in reliance on this e-mail or attachments.
This notice should not be removed.