Loading ...
Sorry, an error occurred while loading the content.

1266Re: vim +perl etc. on OS X

Expand Messages
  • Bram Moolenaar
    Jan 16, 2004
      Ken Scott wrote:

      > > Benji Fisher wrote:
      > >
      > >> On Wed, Jan 14, 2004 at 10:07:32AM -0700, Ken Scott wrote:
      > >>>
      > >>> On Jan 14, 2004, at 8:39 AM, Bob Ippolito wrote:
      > >>>
      > >>>> [snip]
      > >>>
      > >>>> That's bizarre, because Python is threaded on OS X 10.3 ... I wonder
      > >>>> what the deal is with that? Is a threaded Python ok because it has
      > >>>> the GIL, or should a non-threaded version be in Vim as well? Or
      > >>>> maybe.. Vim's configure script should take a threaded Perl?
      > >>>
      > >>> If someone can talk me through modifying the configure script, I'll
      > >>> try building it to accept the threaded perl, and see if it can do
      > >>> basic things or not.
      > >>
      > >> Tweaking the configure script is not easy. I prefer to leave
      > >> that for people who understand autoconf. As for perl, I assume
      > >> there is a reason not to link against a threaded version. Bram?
      > >
      > > I do not know why Perl without threads is refused. There is an
      > > explicit configure check for it, thus there must be a good reason.
      > > But perhaps it was only for an old version of Perl? It's also
      > > possible that if_perl.xs is not prepared for threading.
      > >
      > > You could edit src/auto/configure, search for "usethreads" and insert
      > > this below the "eval" command:
      > >
      > > usethreads=undef
      > >
      > > Look out or compile errors and warnings in if_perl.c.
      > I did this; the only warning I saw was a warning for an unused
      > variable. At the end, near the ld steps, I was getting a message that
      > /usr/local/lib does not exist, but I do not think that harmed anything.
      > I ran the Vim.app that was created. It shows +perl, and I am able to
      > run :perl VIM::Msg("This is from Perl in Vim") and get the message
      > displayed. I think this means that the perl interface is working on
      > some very basic level. I do not have the expertise to test this more
      > fully.
      > I am now playing in the auto/configure script to see if the Tcl support
      > can be turned on. It was not finding the includes; I am trying to get
      > the include from /System/Library/Frameworks/Tcl.framework/Headers to be
      > recognized.
      > Onward and upwards...

      The patch that added the configure check for threads is 6.1.438, made by
      Aron Griffis. I'll include him in the copy list.

      Aron, can you tell us how to test that a threaded Perl will break?
      Could this depend on the Perl version somehow? Perhaps the Perl on Mac
      OSX 10.3 does work.

      Not too long ago, cut and paste was done with scissors and glue...

      /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
      /// Sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
      \\\ Project leader for A-A-P -- http://www.A-A-P.org ///
      \\\ Help AIDS victims, buy here: http://ICCF-Holland.org/click1.html ///
    • Show all 17 messages in this topic