* gfortran build error i386.c
[not found] <DF7B7224D273BA4CB5A786DF6B1B48DDDD7C8F71@EMP-EXMR104.corp.leidos.com>
@ 2017-12-28 1:34 ` Darrell Reich via fortran
2017-12-28 4:18 ` Tim Prince via fortran
0 siblings, 1 reply; 2+ messages in thread
From: Darrell Reich via fortran @ 2017-12-28 1:34 UTC (permalink / raw)
To: fortran
What am I doing wrong? I have been able to build gfortran 8 previously.
What safeguards are in place to prevent breaking the build?
Is there a nightly build & test continuous integration setup?
I like the separate build folders from svn so the important files that are checked in are not mixed up with the temporary build artifacts. All projects should be setup that way.
I’ve pasted the error messages and recent history of the file below. Please confirm I am or am not crazy, thanks!
svn update
make
../../svn/gcc/config/i386/i386.c:44778:1: error: too many initializers for ‘const attribute_spec’
};
^
../../svn/gcc/config/i386/i386.c:44778:1: error: cannot convert ‘bool’ to ‘const attribute_spec::exclusions*’ in initialization
svn log i386.c | head
r255997 | jakub | 2017-12-25 03:59:17 -0800 (Mon, 25 Dec 2017) | 115 lines
r255975 | kyukhin | 2017-12-22 04:37:16 -0800 (Fri, 22 Dec 2017) | 78 lines
r255974 | itsimbal | 2017-12-22 03:41:02 -0800 (Fri, 22 Dec 2017) | 23 lines
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: gfortran build error i386.c
2017-12-28 1:34 ` gfortran build error i386.c Darrell Reich via fortran
@ 2017-12-28 4:18 ` Tim Prince via fortran
0 siblings, 0 replies; 2+ messages in thread
From: Tim Prince via fortran @ 2017-12-28 4:18 UTC (permalink / raw)
To: fortran
On 12/27/2017 8:34 PM, Darrell Reich via fortran wrote:
> What am I doing wrong? I have been able to build gfortran 8 previously.
>
> What safeguards are in place to prevent breaking the build?
> Is there a nightly build & test continuous integration setup?
>
> I like the separate build folders from svn so the important files that are checked in are not mixed up with the temporary build artifacts. All projects should be setup that way.
>
> I’ve pasted the error messages and recent history of the file below. Please confirm I am or am not crazy, thanks!
>
> svn update
> make
>
> ../../svn/gcc/config/i386/i386.c:44778:1: error: too many initializers for ‘const attribute_spec’
> };
> ^
> ../../svn/gcc/config/i386/i386.c:44778:1: error: cannot convert ‘bool’ to ‘const attribute_spec::exclusions*’ in initialization
>
> svn log i386.c | head
> r255997 | jakub | 2017-12-25 03:59:17 -0800 (Mon, 25 Dec 2017) | 115 lines
>
> r255975 | kyukhin | 2017-12-22 04:37:16 -0800 (Fri, 22 Dec 2017) | 78 lines
>
> r255974 | itsimbal | 2017-12-22 03:41:02 -0800 (Fri, 22 Dec 2017) | 23 lines
>
I've seen this problem for at least a week. I didn't try the build since
it was successful about 3 weeks ago. I assume it's specific to Windows
or cygwin. I can't find it on gcc bugzilla, so maybe it would be good
to file a bug report. I'm fairly certain no one does nightly tests for
whichever targets expose this.
--
Tim Prince
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-12-28 4:18 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <DF7B7224D273BA4CB5A786DF6B1B48DDDD7C8F71@EMP-EXMR104.corp.leidos.com>
2017-12-28 1:34 ` gfortran build error i386.c Darrell Reich via fortran
2017-12-28 4:18 ` Tim Prince via fortran
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).