unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: [patch] 1.6.4: configure syntax error with autoconf 2.59
Date: Fri, 30 Jul 2004 14:07:28 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.58L.0407301357270.23489@blysk.ds.pg.gda.pl> (raw)

Hello,

 As of autoconf 2.59 due to the way AC_LIBOBJ gets expanded, the resulting 
configure script contains "; fi" alone in a line, which is not accepted at 
least by bash 2.05b.  Here is an obvious fix.

2004-07-30  Maciej W. Rozycki  <macro@linux-mips.org>

	* configure.in: Reformat a conditional statement to place
	AC_LIBOBJ alone in a line.
	* configure: Regenerate.

 Please apply.

  Maciej

guile-1.6.4-ac.patch
diff -up --recursive --new-file guile-1.6.4.macro/configure.in guile-1.6.4/configure.in
--- guile-1.6.4.macro/configure.in	2002-12-08 01:48:52.000000000 +0000
+++ guile-1.6.4/configure.in	2004-07-26 22:40:49.000000000 +0000
@@ -462,7 +462,9 @@ AC_REPLACE_FUNCS(inet_aton putenv strerr
 # explicitly to LIBOBJS to make sure that it is translated to
 # `alloca.lo' for libtool later on.  This can and should be done more cleanly.
 AC_FUNC_ALLOCA
-if test "$ALLOCA" = "alloca.o"; then AC_LIBOBJ([alloca]); fi
+if test "$ALLOCA" = "alloca.o"; then
+	AC_LIBOBJ([alloca])
+fi
 
 AC_CHECK_MEMBERS([struct stat.st_rdev])
 AC_CHECK_MEMBERS([struct stat.st_blksize])


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile


             reply	other threads:[~2004-07-30 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-30 12:07 Maciej W. Rozycki [this message]
2004-07-31  1:52 ` [patch] 1.6.4: configure syntax error with autoconf 2.59 Kevin Ryde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.58L.0407301357270.23489@blysk.ds.pg.gda.pl \
    --to=macro@linux-mips.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).