This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/53832] [4.8 Regression] error: macro "ggc_alloc_cleared_lang_decl" passed 1 arguments, but takes just 0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53832

Gary Funck <gary at intrepid dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gary at intrepid dot com,
                   |                            |nenad at intrepid dot com

--- Comment #5 from Gary Funck <gary at intrepid dot com> 2012-07-15 17:13:51 UTC ---
(In reply to comment #4)
> This seems to have been caused by using a sparse checkout from svn (using
> --set-depth empty) to avoid having thousands of files from libjava and other
> dirs I don't use.
> 
> After restoring most of the absent files I get a proper gtype-desc.h
> 
> The bit that matters seems to be gcc/ada, without that dir being present I get
> a bad gtype-desc.h even though I'm using --enable-languages=c,c++

For GUPC, we build snapshots (and releases) that only have "C"+"C++"+"UPC". 
Recently, we have run into the failure documented in this bug report for
full bootstrap builds (which invoke the C++ compiler) and our truncated
source tree.  We merge almost weekly with the trunk, fyi.

I recall some time back some exchanges on the GCC list regarding the
difficulties
of releasing sub-parts of the GCC source tree, but don't recall the technical
details or the stated policy.

Our users run builds on some rather constrained machines, and for them the
extra 400MB of source may make a difference.

We can confirm that there is something in the 'ada' tree that fixes this build
failure.

Has a decision been made that sub-setting the GCC tree is unsupported?

Or ... perhaps this bug was marked as "RESOLVED INVALID" for a different
reason?

In any event, we would like to be able to continue to release sub-sets of the
GCC source tree if possible, and still run full bootstrap, etc. (note that
with --disable-bootstrap we don't see this failure).

Please advise.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]