This is the mail archive of the gcc-patches@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]

Re: PR bootstrap/27963 - PR target/19970 [toplevel]


DJ Delorie schrieb:
> Well, I can't think of a better way to approach this problem.  I still
> worry that some platforms won't be able to build boehm-gc, especially
> this close to the 4.2 branch, but it's easy enough to tweak the
> platforms that fail.  I'm OK with it if Mark OK's it for stage3.
> Mark?
> 

Just to address your worry, let me repeat.  boehm-gc will /only/ be
build if it was requested via --enable-objc-gc or java was enabled (and
libgcj not disabled).  At least that's what this code was for:

+# Make sure we only build Boehm's garbage collector if required.
+case ,${enable_languages},:${enable_libgcj}:${enable_objc_gc} in
+  *,objc,*:*:yes)
+    # Keep target-boehm-gc if requested for Objective-C.
+    ;;
+  *,java,*:no:*)
+    # Remove target-boehm-gc if libgcj has been disabled explicitly.
+    noconfigdirs="$noconfigdirs target-boehm-gc"
+    ;;
+  *,java,*:*:*)
+    # Keep target-boehm-gc by default for Java.
+    ;;
+  *)
+    # Otherwise remove target-boehm-gc.
+    noconfigdirs="$noconfigdirs target-boehm-gc"
+    ;;
+esac

So I don't think that removing target-boehm-gc from the target
noconfigdirs is significantly worse than before the patch for PR 13946
was committed.

Cheers,
David


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