MacOS X

MacOS X

[richmit]

Greetings;

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.  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

During the compile, a few warnings came out:

stime.c:365: warning: implicit declaration of function `strcpy'
ramap.c:2012: warning: implicit declaration of function `strlen'
unif.c:1563: warning: implicit declaration of function `memcpy'
socket.c: In function `scm_getsockopt':
socket.c:240: warning: passing arg 5 of `getsockopt' from incompatible 
pointer type
socket.c: In function `scm_accept':
socket.c:625: warning: passing arg 3 of `accept' from incompatible 
pointer type
socket.c: In function `scm_getsockname':
socket.c:650: warning: passing arg 3 of `getsockname' from incompatible 
pointer type
socket.c: In function `scm_getpeername':
socket.c:675: warning: passing arg 3 of `getpeername' from incompatible 
pointer type
socket.c: In function `scm_recvfrom':
socket.c:810: warning: passing arg 6 of `recvfrom' from incompatible 
pointer type

Will MacOS X be officially supported in the future?  We are using guile 
for several
internal development projects, and the PowerPC platform with MacOS X has 
proven
itself to be a valuable platform for us.

Thanx in advance for your time.

							-mitch richling

PS: Guile is a great tool.  You have something to be proud of.



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile

Re: MacOS X

[Thien-Thi Nguyen]

   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

Re: MacOS X

[Marius Vollmer]

Thien-Thi Nguyen <ttn@giblet.glug.org> writes:

>    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.

Richmit, lest you get the impression that the 'official' developers of
Guile are not interested in patches and bug reports about MacOS: they
are.  We can't promise to fix all bugs since few if any have access to
a MacOS box, but patches are always welcome.  (Heck, we even have (the
beginnings?) of Win32 support in Guile.)

Soo, please don't be put off by a lack of response to bug reports.  It
only means that nobody knows the fix, not that we don't want to hear
about it.  Patches are easier to handle and will get more attention.
And, there is nothing keeping _you_ from becoming the 'official' MacOS
dude of Guile... ;-)

_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile

Re: MacOS X

[richmit]

On Saturday, June 29, 2002, at 09:08  PM, Thien-Thi Nguyen wrote:

>    From: richmit <richmit@member.ams.org>
>    Date: Mon, 17 Jun 2002 23:12:11 -0500

>    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 "/" ?)

yea, --prefix is irrelevant here.  What is of note is that gcc3 did
a better job than gcc2.  It is also important to note that many of
the config tests get incorrect results without the CPPFLAGS variable
set.

For example, the tests for usleep couldn't find the declaration in
the header files.



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://mail.gnu.org/mailman/listinfo/bug-guile