From: "Dale P. Smith" <dsmith@altustech.com>
Subject: Guile 1.5.6 build failure on OpenBSD 3.0
Date: Wed, 10 Apr 2002 11:11:39 -0400 [thread overview]
Message-ID: <20020410111139.4ac7edd7.dsmith@altustech.com> (raw)
Guile fails to build on OpenBSD 3.0.
It appears that the preprocessor #define i386 isn't defined, while
__i386__ is. Using __i386__ seems to fix things. Here is a diff:
--- gc_os_dep.c.old Wed Apr 10 11:09:36 2002
+++ gc_os_dep.c Wed Apr 10 11:10:07 2002
@@ -254,7 +254,7 @@
# define NEXT
# define mach_type_known
# endif
-# if defined(__OpenBSD__) && defined(i386)
+# if defined(__OpenBSD__) && defined(__i386__)
# define I386
# define OPENBSD
# define mach_type_known
-Dale
--
Dale P. Smith
Treasurer, Cleveland Linux Users Group http://cleveland.lug.net
Senior Systems Consultant, Altus Technologies Corporation
dsmith@altustech.com
440-746-9000 x339
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next reply other threads:[~2002-04-10 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 15:11 Dale P. Smith [this message]
2002-04-22 17:34 ` Guile 1.5.6 build failure on OpenBSD 3.0 Thien-Thi Nguyen
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=20020410111139.4ac7edd7.dsmith@altustech.com \
--to=dsmith@altustech.com \
/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).