[Prev][Next][Index][Thread]

Re: Status of Dylan on MacOS X

In article <200110191717.NAA11384@life.ai.mit.edu>, Raffael Cavallaro 
<raffael@mediaone.net> wrote:

> On Friday, October 19, 2001, at 11:11 AM, Rob Myers wrote:
> 
> > You do need to install some of the GNU tools to replace the Apple ones
> > (automake, autoconf and libtool), especially for compiling the compiler.
> >
> > It hasn't been tested on 10.1 yet to the best of my knowledge, but it 
> > should
> > work OK. I'm hoping 10.1 will fix the need to install the GNU tools (the
> > very latest GNU tools don't compile on 10.0.4). I'll test all this when 
> > my
> > copy of 10.1 arrives, hopefully next week.
> 
> Last time I tried to install the current release, I tripped over this. I 
> remember being reluctant to replace the Apple versions of these tools 
> for fear that either:
> 
> 1. it would break the Apple tool chain in some unforeseen way, making 
> the Apple Developer Tools unusable for compiling and installing other 
> open source software released for MacOS X.

I'm afraid of that as well.


> 2. Apple would release an update to their developer tools that would 
> overwrite these Gnu Tools, thus rendering the Dylan tool chain unusable.

Won't happen, as Apple stuff is in /usr/bin while stuff compiled by the 
user goes into /usr/local/bin.

 
> So, I guess what I'm asking is: Is there, or will there soon be a 
> version of Gwydion Dlylan that works on a stock MacOS X 10.1, with the 
> Developer Tools as shipped by Apple, since this is what every other open 
> source software project will be targeting. Failing that, is there,  or 
> will there soon be a binary distribution that works under a stock MacOS 
> X?

You need automake, as OS X doesn't come with it at all.

I had to make one more change from what is in the cvs at the moment.  My 
quick-hack change is:

diff -c -r1.30 Defaults.in
*** src/Defaults.in     2001/09/25 03:38:48     1.30
--- src/Defaults.in     2001/10/20 00:07:42
***************
*** 41,54 ****
  $shared = "@shared@" eq "yes";
  $static = "@static@" eq "yes";
  $INSTALL = "@INSTALL@";
! $LIBTOOL = '@LIBTOOL@';
  
  # INSTALL_DATA and INSTALL_PROGRAM don't do what I would expect.  In
  # particular, INSTALL_PROGRAM doesn't force executability.
  $install_data = "@INSTALL@";
  if ($shared) {
!     $install_program = "@LIBTOOL@ @INSTALL@ -m oug+rx";
!     $install_library = "@LIBTOOL@ @INSTALL@";
  } else {
      $install_program = "@INSTALL@ -m oug+rx";
      $install_library = "@INSTALL@";
--- 41,54 ----
  $shared = "@shared@" eq "yes";
  $static = "@static@" eq "yes";
  $INSTALL = "@INSTALL@";
! $LIBTOOL = "glibtool";
  
  # INSTALL_DATA and INSTALL_PROGRAM don't do what I would expect.  In
  # particular, INSTALL_PROGRAM doesn't force executability.
  $install_data = "@INSTALL@";
  if ($shared) {
!     $install_program = "glibtool @INSTALL@ -m oug+rx";
!     $install_library = "glibtool @INSTALL@";
  } else {
      $install_program = "@INSTALL@ -m oug+rx";
      $install_library = "@INSTALL@";


I see from the cvs log of this file that Rob had *twice* before made a 
similar (but less hacky) change, and it has been twice backed out by 
other members of the d2c team.

Rob's previous change (writing "\@LIBTOOL@" in each place) doesn't work 
in OS X 10.1 if you've only installed automake.  I suspect that Apple's 
autoconf also needs enhancement because doing ./configure prints up the 
following error messages:

You should update you 'aclocal.m4' by running aclocal
autoconf: Undefined macros:
configure.in:203:AC_PROG_LIBTOOL


I don't know anywhere near enough about autoconf to know how to fix 
this.  Certainly just running "aclocal" does help.


However, with the above patch, and the missing automake installed (I 
used 1.4-P5 from ftp.gnu.org) the current Gwydion source in cvs builds 
and runs fine on 10.1.

-- Bruce
Follow-Ups: