This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: re-apply Kelley's test for old Darwin cctools
- From: Per Bothner <per at bothner dot com>
- To: Mike Stump <mrs at apple dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Sun, 21 Nov 2004 15:04:50 -0800
- Subject: Re: PATCH: re-apply Kelley's test for old Darwin cctools
- References: <F7D75CE6-3C0D-11D9-856A-003065BDF310@apple.com>
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
cross-environment.)
--
--Per Bothner
per@bothner.com http://per.bothner.com/
Index: configure.ac
===================================================================
RCS file: /cvs/gcc/gcc/gcc/configure.ac,v
retrieving revision 2.83
diff -u -r2.83 configure.ac
--- configure.ac 5 Nov 2004 04:49:18 -0000 2.83
+++ configure.ac 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: ftp://gcc.gnu.org/pub/gcc/infrastructure/cctools-528.5.dmg >&2
+ test x$build = x$target && exit 1
+ fi
+ conftest_s=' .text
mfcr r3,128';;
*) conftest_s=' .machine power4
.text