From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: native Win32 guile 1.7.0
Date: Sat, 31 May 2003 10:20:56 +1000 [thread overview]
Message-ID: <87of1kuftj.fsf@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0305301113300.607-100000@bono.reversers.net> (stefan@lkcc.org's message of "Fri, 30 May 2003 11:27:37 +0200 (CEST)")
stefan <stefan@lkcc.org> writes:
>
> With the last changes in 'numbers.h' all of the errors in the error.log I
> posted earlier disappear, i.e. using _copysign, _isnan and _finite solved
> the problems in the 'numbers.test'.
I'd suggest doing those in a system-neutral style too. _copysign is a
function I take it. In which case add autoconf tests and use
(untested),
/* mingw offers _copysign rather than copysign */
#if ! HAVE_COPYSIGN && HAVE__COPYSIGN
#define copysign _copysign
#define HAVE_COPYSIGN 1
#endif
Again, good for adapting automatically to the future. (Autoconf is
about testing for features, not system types.)
> * I do use a special 'guile.cache' file as cache file for the configure
> script. The file defines some tests to be done and chached. I think
> this is normal for a cross-build.
In principle hopefully not :-). I needed to force
ac_cv_sys_restartable_syscalls=no when I tried a cross compile a while
ago though.
And an EXEEXT_FOR_BUILD is needed for gen-scmconfig. I've been
meaning to propose some code I'd used for gmp in that area.
> * The 'fileblocks.o' must be removed in configure before configure'ing.
> This is due to the macro AC_STRUCT_ST_BLOCKS.
It's always annoying when autoconf does more than wanted. Maybe
AC_CHECK_MEMBER should be used instead.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-31 0:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 14:31 native Win32 guile 1.7.0 stefan
2003-05-29 23:13 ` Kevin Ryde
2003-05-29 23:23 ` Kevin Ryde
2003-05-30 3:23 ` stefan
2003-05-30 23:58 ` Kevin Ryde
2003-06-11 23:42 ` Kevin Ryde
2003-05-30 9:27 ` stefan
2003-05-31 0:20 ` Kevin Ryde [this message]
2003-06-08 22:03 ` Kevin Ryde
2003-06-11 23:15 ` Kevin Ryde
2003-06-12 5:01 ` stefan
2003-06-15 0:15 ` putenv tests (was: native Win32 guile 1.7.0) Kevin Ryde
2003-06-11 23:54 ` native Win32 guile 1.7.0 Kevin Ryde
2003-06-14 5:36 ` stefan
2003-06-14 12:24 ` Marius Vollmer
2003-06-14 13:46 ` stefan
2003-06-14 16:18 ` Marius Vollmer
2003-06-16 17:25 ` stefan
2003-06-18 23:42 ` Marius Vollmer
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=87of1kuftj.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).