This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/27963] [4.2 Regression] libjava fails to build if it isn't built by default
- From: "ro at techfak dot uni-bielefeld dot de" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 8 Jun 2006 20:23:58 -0000
- Subject: [Bug bootstrap/27963] [4.2 Regression] libjava fails to build if it isn't built by default
- References: <bug-27963-81@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from ro at techfak dot uni-bielefeld dot de 2006-06-08 20:23 -------
Subject: Re: [4.2 Regression] libjava fails to build if it isn't built by
default
ayers at gcc dot gnu dot org writes:
> I followed the advice given here:
>
> http://gcc.gnu.org/ml/gcc-patches/2006-05/msg00886.html
As this PR demonstrates, this advice was wrong wrt. to adding boehm-gc to
noconfigdirs, as this will break any configuration where libjava just isn't
built by default.
> I believe "noconfigdir" is supposed to mean "not supported" so in this case the
> correct "patch" would be to remove tartget-boehm-gc if in fact it is supported
> by the platform, as we will later remove it again if it wasn't requested by
> libobjc and not needed by java.
>
> If I get a get a list of targets for which I should re-enable target-boehm-gc
> (and possibly pre approval) I can certainly come up with a patch (it's just a
> matter of removing target-boehm-gc from the appropriate noconfigdir entry).
I fear this is the wrong way round: it shouldn't be necessary to unbreak
the affected targets one by one, but boehm-gc should only be included in
noconfigdirs if it is known not to work (which is what noconfigdirs is
for).
Rainer
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27963