From: Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de>
Cc: guile-devel@gnu.org
Subject: Re: Please put these fixes from CVS HEAD into branch_release-1-6
Date: Mon, 12 Jan 2004 18:42:00 +0100 [thread overview]
Message-ID: <uw5n08tqd1z.fsf@merkur.math.uni-magdeburg.de> (raw)
In-Reply-To: <87znfb75k2.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Tue, 04 Nov 2003 23:22:37 -0600")
Rob Browning <rlb@defaultvalue.org> wrote on Nov 5, 2003:
> Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de> writes:
>
>> Earlier this year, I reported a build problem of Guile on Solaris
>> when using the Sun/Forte compiler. The fix was put only put into
>> CVS HEAD:
>
> If no one gets to this beforehand, I'll do it next week.
I have just noticed that the changes still do not show up in CVS.
Could someone please put my fixes into the stable branch? Thanks.
For reference, I am attaching my message again below.
-------------------->8--------------------
Earlier this year, I reported a build problem of Guile on Solaris
when using the Sun/Forte compiler. The fix was put only put into CVS
HEAD:
2003-07-27 Marius Vollmer <mvo@zagadka.de>
* configure.in (__libc_stack_end): Actually use the value in
__libc_stack_end for something so that the access doesn't get
optimized away. Thanks to Matthias Koeppe!
Today I tried to build a Guile from branch_release-1-6 and ran into
the same old problem. Can you please put this fix into the stable
branch? Thank you.
--- configure.in.~1.157.2.26.~ Tue Nov 4 14:23:03 2003
+++ configure.in Tue Nov 4 18:44:37 2003
@@ -325,8 +325,9 @@
inet_pton inet_ntop)
AC_MSG_CHECKING(for __libc_stack_end)
-AC_TRY_LINK([extern char *__libc_stack_end;],
- [char *p = __libc_stack_end;],
+AC_TRY_LINK([#include <stdio.h>
+extern char *__libc_stack_end;],
+ [printf("%p", (char*) __libc_stack_end);],
have_libc_stack_end=yes,
have_libc_stack_end=no)
AC_MSG_RESULT($have_libc_stack_end)
The same, though less critical, applies to this fix:
2003-02-27 Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de>
* format.scm (format:out-substr): Update the column counter
correctly. This fixes the behavior of ~T (tabbing) after ~F, for
instance.
Index: ice-9/format.scm
===================================================================
RCS file: /cvs/guile/guile-core/ice-9/format.scm,v
retrieving revision 1.11.2.1
diff -u -r1.11.2.1 format.scm
--- ice-9/format.scm 27 Nov 2001 22:30:04 -0000 1.11.2.1
+++ ice-9/format.scm 4 Nov 2003 17:50:42 -0000
@@ -94,7 +94,7 @@
(do ((k i (+ k 1)))
((= k n))
(write-char (string-ref str k) format:port))
- (set! format:output-col (+ format:output-col n)))
+ (set! format:output-col (+ format:output-col (- n i))))
;(define (format:out-fill n ch) ; this allocates a new string
; (format:out-str (make-string n ch)))
--
Matthias Koeppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-12 17:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 19:21 Please put these fixes from CVS HEAD into branch_release-1-6 Matthias Koeppe
2003-11-05 5:22 ` Rob Browning
2004-01-12 17:42 ` Matthias Koeppe [this message]
2004-01-13 16:45 ` Rob Browning
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=uw5n08tqd1z.fsf@merkur.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.de \
--cc=guile-devel@gnu.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).