From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: native Win32 guile 1.7.0
Date: Fri, 30 May 2003 09:13:07 +1000 [thread overview]
Message-ID: <87of1lny7w.fsf@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0305291627020.353-200000@bono.reversers.net> (stefan@lkcc.org's message of "Thu, 29 May 2003 16:31:06 +0200 (CEST)")
stefan <stefan@lkcc.org> writes:
>
> * posix.c (s_scm_putenv): Disable use of unsetenv() for the
> mingw32 build.
>
> #ifndef __MINGW32__
It'd be good autoconf style to test unsetenv with AC_CHECK_FUNCS if
it's not always available. In particular that way it gets used if
added to mingw in the future.
Perhaps environ could be munged directly if unsetenv doesn't exist.
Might end up being a memory leak. Probably not ideal to silently do
nothing.
> * mkstemp.c: Provide prototype to avoid compiler warning.
It's usually best to just omit prototypes if they're not in a standard
header, and the return value is only an int. It's all too easy to end
up with a conflict on some obscure system. AC_CHECK_DECLS is the way
to go if you really want a declaration.
> * configure.in: Removed -lm check
>
> if test $MINGW32 = no; then
> AC_CHECK_LIB(m, main)
> fi
Doesn't it simply find -lm doesn't exist and continue? If there has
to be a hard system dependency, autoconf deprecates $MINGW32 in favour
of "case $host in *-*-mingw*)" etc.
Libtool has an AC_CHECK_LIBM which knows about a few systems. We use
it in gmp, not actually documented though.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-29 23:13 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 [this message]
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
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=87of1lny7w.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).