From: Thien-Thi Nguyen <ttn@giblet.glug.org>
Cc: bug-guile@gnu.org
Subject: Re: MacOS X
Date: Sat, 29 Jun 2002 19:08:41 -0700 [thread overview]
Message-ID: <E17OU8n-0003dz-00@giblet> (raw)
In-Reply-To: <901274C5-8271-11D6-B00F-003065F9192A@member.ams.org> (message from0richmit on Mon, 17 Jun 2002 23:12:11 -0500)
From: richmit <richmit@member.ams.org>
Date: Mon, 17 Jun 2002 23:12:11 -0500
After struggling for a few hours I have finally managed to get guile
to build on MacOS X. In order to do this, I had to remove readline
from my development system -- I don't know how to get guile to build
without readline support. We are using readline 4.2.
perhaps "--disable-readline" would be a useful configure option to add.
I also had to use the following command line for configure to get a
valid build environment:
CPPFLAGS=-traditional-cpp CC=/usr/bin/gcc3 ./configure
--prefix=/usr/local/ --disable-threads
normally `--prefx=/usr/local' is the default and can be omitted. is
this not the case on MacOS X? (or is the difference the extra "/" ?)
During the compile, a few warnings came out: [bad decls]
these should be cleaned up for sure. thanks for the tip.
Will MacOS X be officially supported in the future?
personally, i don't see the value of "official support" at this time in
theory or in practice (guile maintainership is pretty losing, IMHO). by
the same token (also personally), i'd like to see if i can munge guile
to be as near hassle-free as possible on as many platforms as possible,
to gain confidence in my own configury skills. bottom line: this will
likely result in guile on MacOS X being supported by its users in some
form or another (as it should be ;-). no worries, just keep the bug
reports flowing...
thi
_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile
next prev parent reply other threads:[~2002-06-30 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-18 4:12 MacOS X richmit
2002-06-30 2:08 ` Thien-Thi Nguyen [this message]
2002-06-30 10:07 ` Marius Vollmer
2002-06-30 20:53 ` richmit
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=E17OU8n-0003dz-00@giblet \
--to=ttn@giblet.glug.org \
--cc=bug-guile@gnu.org \
--cc=ttn@glug.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).