[commits] r11148 - in /libdfp/trunk: ChangeLog README.developer configure configure.ac

[ryanarn@xxxxxxxxxx]

Author: ryanarn
Date: Wed Aug  4 10:31:35 2010
New Revision: 11148

Log:
2010-08-04  Ryan S. Arnold  <rsa@xxxxxxxxxx>

	* configure: Regenerated.
	* configure.ac: Apparently AC_CANONICAL_SYSTEM is only for compilers.
	I removed it, and support for --target.  Now you must use --build
	only.
	* README.developer: Removed directions for using --target.


Modified:
    libdfp/trunk/ChangeLog
    libdfp/trunk/README.developer
    libdfp/trunk/configure
    libdfp/trunk/configure.ac

Modified: libdfp/trunk/ChangeLog
==============================================================================
--- libdfp/trunk/ChangeLog (original)
+++ libdfp/trunk/ChangeLog Wed Aug  4 10:31:35 2010
@@ -1,4 +1,13 @@
+2010-08-04  Ryan S. Arnold  <rsa@xxxxxxxxxx>
+
+	* configure: Regenerated.
+	* configure.ac: Apparently AC_CANONICAL_SYSTEM is only for compilers.
+	I removed it, and support for --target.  Now you must use --build
+	only.
+	* README.developer: Removed directions for using --target.
+
 2010-07-30  Ryan S. Arnold  <rsa@xxxxxxxxxx>
+
 	* sysdeps/powerpc/dfpu/fe_decround.c (stdio.h): Removed unnecessary
 	include.
 

Modified: libdfp/trunk/README.developer
==============================================================================
--- libdfp/trunk/README.developer (original)
+++ libdfp/trunk/README.developer Wed Aug  4 10:31:35 2010
@@ -289,7 +289,7 @@
 	Some System Z machines require the -mzarch flag, e.g.
 	CFLAGS="-m31 -mzarch -O2 -g"
 
-	These should accompany sympathetic --build or --target switches
+	These should accompany sympathetic --build switch
 	described below, e.g.
 
 		powerpc-linux-gnu for -m32
@@ -303,17 +303,13 @@
 Libdfp's default configure  will be based on whatever bitness the user
 environment is.
 
-In order to build 32-bit libdfp you can pass the following switches:
+In order to build 32-bit libdfp you can pass the following switch:
 
 	--build=powerpc-linux-gnu
-	  or
-	--target=powerpc-linux-gnu
-
-In order to build 64-bit libdfp you can pass the following switches:
+
+In order to build 64-bit libdfp you can pass the following switch:
 
 	--build=powerpc64-linux-gnu
-	  or
-	--target=powerpc64-linux-gnu
 
 The following switches define the DFP backend.
 

Modified: libdfp/trunk/configure
==============================================================================
--- libdfp/trunk/configure (original)
+++ libdfp/trunk/configure Wed Aug  4 10:31:35 2010
@@ -276,7 +276,7 @@
 ac_unique_file="printf_dfp.c"
 ac_subdirs_all="$ac_subdirs_all libdecnumber"
 ac_subdirs_all="$ac_subdirs_all libbid"
-ac_subst_vars='SHELL PATH_SEPARATOR PACKAGE_NAME PACKAGE_TARNAME PACKAGE_VERSION PACKAGE_STRING PACKAGE_BUGREPORT exec_prefix prefix program_transform_name bindir sbindir libexecdir datadir sysconfdir sharedstatedir localstatedir libdir includedir oldincludedir infodir mandir build_alias host_alias target_alias DEFS ECHO_C ECHO_N ECHO_T LIBS build build_cpu build_vendor build_os host host_cpu host_vendor host_os target target_cpu target_vendor target_os enable_decimal_float dfp_backend with_dfp with_fp base_machine machine CC CFLAGS LDFLAGS CPPFLAGS ac_ct_CC EXEEXT OBJEXT OBJDUMP AS ASFLAGS libdfp_cv_cc_with_decimal_float glibc_headers glibc_build enable_static enable_shared submachine submachine_opt sysdep_dirs RANLIB ac_ct_RANLIB AWK subdirs LIBOBJS LTLIBOBJS'
+ac_subst_vars='SHELL PATH_SEPARATOR PACKAGE_NAME PACKAGE_TARNAME PACKAGE_VERSION PACKAGE_STRING PACKAGE_BUGREPORT exec_prefix prefix program_transform_name bindir sbindir libexecdir datadir sysconfdir sharedstatedir localstatedir libdir includedir oldincludedir infodir mandir build_alias host_alias target_alias DEFS ECHO_C ECHO_N ECHO_T LIBS build build_cpu build_vendor build_os host host_cpu host_vendor host_os enable_decimal_float dfp_backend with_dfp with_fp base_machine machine CC CFLAGS LDFLAGS CPPFLAGS ac_ct_CC EXEEXT OBJEXT OBJDUMP AS ASFLAGS libdfp_cv_cc_with_decimal_float glibc_headers glibc_build enable_static enable_shared submachine submachine_opt sysdep_dirs RANLIB ac_ct_RANLIB AWK subdirs LIBOBJS LTLIBOBJS'
 ac_subst_files=''
 
 # Initialize some variables set by options.
@@ -797,7 +797,6 @@
 System types:
   --build=BUILD     configure for building on BUILD [guessed]
   --host=HOST       cross-compile to build programs to run on HOST [BUILD]
-  --target=TARGET   configure for building compilers for TARGET [HOST]
 _ACEOF
 fi
 
@@ -1396,48 +1395,9 @@
 host_os=`echo $ac_cv_host | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\3/'`
 
 
-
-# Do we support `cross' libdfp support?  Probably.  But this may not be
-# necessary.  The implication of building a cross libdfp is that we can't
-# actually guess the Decimal Float Type backend based upon the $build_*
-# variables.  This will be manifest as a --target that differs from --build.
-echo "$as_me:$LINENO: checking target system type" >&5
-echo $ECHO_N "checking target system type... $ECHO_C" >&6
-if test "${ac_cv_target+set}" = set; then
-  echo $ECHO_N "(cached) $ECHO_C" >&6
-else
-  ac_cv_target_alias=$target_alias
-test "x$ac_cv_target_alias" = "x" &&
-  ac_cv_target_alias=$ac_cv_host_alias
-ac_cv_target=`$ac_config_sub $ac_cv_target_alias` ||
-  { { echo "$as_me:$LINENO: error: $ac_config_sub $ac_cv_target_alias failed" >&5
-echo "$as_me: error: $ac_config_sub $ac_cv_target_alias failed" >&2;}
-   { (exit 1); exit 1; }; }
-
-fi
-echo "$as_me:$LINENO: result: $ac_cv_target" >&5
-echo "${ECHO_T}$ac_cv_target" >&6
-target=$ac_cv_target
-target_cpu=`echo $ac_cv_target | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\1/'`
-target_vendor=`echo $ac_cv_target | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\2/'`
-target_os=`echo $ac_cv_target | sed 's/^\([^-]*\)-\([^-]*\)-\(.*\)$/\3/'`
-
-
-# The aliases save the names the user supplied, while $host etc.
-# will get canonicalized.
-test -n "$target_alias" &&
-  test "$program_prefix$program_suffix$program_transform_name" = \
-    NONENONEs,x,x, &&
-  program_prefix=${target_alias}-
-
 config_os=$host_os
-machine=$host_cpu
-target_machine=$target_cpu
-
-# If the user uses --target instead of --host we can detect it.
-if test "$target_machine" != "$machine"; then
-  machine=$target_machine
-fi
+#machine=$host_cpu
+machine=$build_cpu
 
 # Only allow a Linux host OS.  We don't support building libdfp on non-Linux
 # systems.
@@ -3719,10 +3679,6 @@
 s,@host_cpu@,$host_cpu,;t t
 s,@host_vendor@,$host_vendor,;t t
 s,@host_os@,$host_os,;t t
-s,@target@,$target,;t t
-s,@target_cpu@,$target_cpu,;t t
-s,@target_vendor@,$target_vendor,;t t
-s,@target_os@,$target_os,;t t
 s,@enable_decimal_float@,$enable_decimal_float,;t t
 s,@dfp_backend@,$dfp_backend,;t t
 s,@with_dfp@,$with_dfp,;t t

Modified: libdfp/trunk/configure.ac
==============================================================================
--- libdfp/trunk/configure.ac (original)
+++ libdfp/trunk/configure.ac Wed Aug  4 10:31:35 2010
@@ -24,21 +24,9 @@
 # Defines host_cpu, host_vendor, and host_os variables.  This is where the
 # code will run.
 AC_CANONICAL_HOST
-
-# Do we support `cross' libdfp support?  Probably.  But this may not be
-# necessary.  The implication of building a cross libdfp is that we can't
-# actually guess the Decimal Float Type backend based upon the $build_*
-# variables.  This will be manifest as a --target that differs from --build.
-AC_CANONICAL_SYSTEM
-
 config_os=$host_os
-machine=$host_cpu
-target_machine=$target_cpu
-
-# If the user uses --target instead of --host we can detect it.
-if test "$target_machine" != "$machine"; then
-  machine=$target_machine
-fi
+#machine=$host_cpu
+machine=$build_cpu
 
 # Only allow a Linux host OS.  We don't support building libdfp on non-Linux
 # systems.