[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Guile-commits] 01/02: Delete trailing whitespace in; nfc.

From: Thien-Thi Nguyen
Subject: [Guile-commits] 01/02: Delete trailing whitespace in; nfc.
Date: Sun, 28 Feb 2021 15:52:45 -0500 (EST)

ttn pushed a commit to branch branch_release-1-8
in repository guile.

commit 618620c4c8a52705d27439bb1f2bc505629c640a
Author: Thien-Thi Nguyen <>
AuthorDate: Sun Feb 28 15:42:58 2021 -0500

    Delete trailing whitespace in; nfc.
--- | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/ b/
index 24300ba..660bee0 100644
--- a/
+++ b/
@@ -187,19 +187,19 @@ dnl  investigation of problems with "64" system and 
library calls on
 dnl  Darwin (MacOS X).  The libguile code (_scm.h) assumes that if a
 dnl  system has stat64, it will have all the other 64 APIs too; but on
 dnl  Darwin, stat64 is there but other APIs are missing.
 dnl  It also appears, from the Darwin docs, that most system call APIs
 dnl  there (i.e. the traditional ones _without_ "64" in their names) have
 dnl  been 64-bit-capable for a long time now, so it isn't necessary to
 dnl  use "64" versions anyway.  For example, Darwin's off_t is 64-bit.
 dnl  A similar problem has been reported for HP-UX:
 dnl  Therefore, and also because a Guile without LARGEFILE64 support is
 dnl  better than no Guile at all, we provide this option to suppress
 dnl  trying to use "64" calls.
 dnl  It may be that for some 64-bit function on Darwin/HP-UX we do need
 dnl  to use a "64" call, and hence that by using --without-64-calls we're
 dnl  missing out on that.  If so, someone can work on that in the future.
@@ -895,7 +895,7 @@ volatile complex double z = - _Complex_I;
 main (void)
-  z = csqrt (z);       
+  z = csqrt (z);
   if (creal (z) > 0.0)
     return 0;  /* good */
@@ -1463,7 +1463,7 @@ CFLAGS="$old_CFLAGS"
 fi # with_threads=pthreads
-## Cross building      
+## Cross building
 if test "$cross_compiling" = "yes"; then
   AC_MSG_CHECKING([cc for build])
   ## /usr/bin/cc still uses wrong assembler
@@ -1471,8 +1471,8 @@ if test "$cross_compiling" = "yes"; then
   CC_FOR_BUILD="${CC_FOR_BUILD-PATH=/usr/bin:$PATH cc}"
 ## AC_MSG_CHECKING("if we are cross compiling")
 ## AC_MSG_RESULT($cross_compiling)
 if test "$cross_compiling" = "yes"; then
@@ -1496,7 +1496,7 @@ if test "$cross_compiling" = "yes"; then
 ## AC_MSG_CHECKING("if we are cross compiling")
 ## AC_MSG_RESULT($cross_compiling)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]