I'm not sure what Anton means and I haven't tried to make any of the dists
yet, but considering the chicken and egg problem, I can see why he's
hesitant to post anything at the moment.
I hadn't examined your scripts before, and I don't understand why you are
setting:
env ac_cv_sizeof_long_long=0
Is there a problem I haven't discovered yet that this solves?
Otherwise, I've ignored the -no-cpp-precomp problem because it cures itself
once cc realizes that the precomp is not working. Your passing of
the -Dunix switch is maybe a better solution than the source change I did to
prim, but I had also fixed cygwin to handle the newer config files.
I had done my investigations quite a while before you posted your stuff, but
I've been buried in work since then and haven't had time to resolve all the
differences. It wasn't until I had to rebuild my local CVS repository that
I discovered the signal.c problems, and it was that and 10.2's release that
pushed me to finally speak up.
Hopefully, all this will get some movement from Anton on Jorge, and
hopefully, I'm going to be able to get back into getting our OSX FCode
tokenizer finished. My intent is that the two go hand in hand, but these
kind of logistical problems are frustrating those plans. ;(
DaR
> -----Original Message-----
> From: David N. Williams [mailto:[EMAIL PROTECTED]]
> Sent: Monday, August 26, 2002 5:42 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [gforth] Re: [GForth] Binary distributions for Mac OS X
>
>
> Dennis Ruffer wrote:
> >
> > I agree, but until Jorge gets the Fink one done, yours is
> all people have
> > and due to the 1998 config.guess problem with darwin, it is
> hard to know how
> > to build it. What does Anton want removed from yours?
>
> It wasn't that he wanted anything removed. Maybe he won't mind
> a private
> quote from email:
>
> No. The binonlydist was meant to be combined with the source
> dist to
> produce a bindist (for those who could get the source dist
> more easily
> (from a GNU mirror) than a bindist (from our site), and then
> run make.
> That's why it does not contain gforth.fi.
>
> However, it seems that many people did not understand this, so
> I have
> concluded that binonlydists are a bad idea and I have not
> created them
> for recent releases.
>
> Are you aware of my howto on building 0.5.0 for OS X?
>
>
http://www-personal.umich.edu/~williams/archive/forth/gforth/dir.html
As far as I know, it works fine. It does not mention that the
build takes advantage of dynamic libs (AFAICT) when dlcompat is
installed, but it works without it anyway.
-- David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
