This is the mail archive of the 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: PATCH: re-apply Kelley's test for old Darwin cctools

Mike Stump wrote:

But it doesn't address the Zack concern. Could you test for $build == $target additionally, and not do the test if they are different. I think that would be a very minor change, and trivial enough to do, and make everyone happier.

I can't easily *test* such a change, as I checked the patch before and after installng the new cctools - and I don't know how I would uninstall the new cctools.

How about the attached patch?  The test is performed and the message is
printed regardless, but it only exits if $build = $target.
(I'm assuming gcc_HAS_CHECK_FEATURE will actually work in a
	--Per Bothner
RCS file: /cvs/gcc/gcc/gcc/,v
retrieving revision 2.83
diff -u -r2.83
---	5 Nov 2004 04:49:18 -0000	2.83
+++	21 Nov 2004 23:02:59 -0000
@@ -2700,7 +2700,16 @@
     case $target in
       *-*-aix*) conftest_s='	.csect .text[[PR]]
 	mfcr 3,128';;
-      *-*-darwin*) conftest_s='	.text
+      *-*-darwin*)
+	gcc_GAS_CHECK_FEATURE([.machine directive support],
+	  gcc_cv_as_machine_directive,,,
+	  [	.machine ppc7400])
+	if test x$gcc_cv_as_machine_directive != xyes; then
+	  echo "*** This target requires an assembler supporting \".machine\"" >&2
+	  echo you can get it from: >&2
+	  test x$build = x$target && exit 1
+	fi
+	conftest_s='	.text
 	mfcr r3,128';;
       *) conftest_s='	.machine power4

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