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

[PATCH] Remove -no-cpp-precomp flag on Mac OS X

Expand Messages
  • Misty De Meo
    Vim currently unconditionally adds the -no-cpp-precomp flag on Mac OS X, with a comment that it s needed for OS X 10.2 . The flag currently does nothing in
    Message 1 of 3 , Oct 19 10:22 PM
      Vim currently unconditionally adds the -no-cpp-precomp flag on Mac OS
      X, with a comment that it's "needed for OS X 10.2". The flag currently
      does nothing in modern versions of OS X (the last version of Apple GCC
      that actually did anything with it was released in December, 2002),
      and prevents vim from being built with non-Apple compilers. For
      example, FSF GCC 4.8 will fail due to the unrecognized flag. (There's
      some more information on this in my blog post about it:
      http://www.mistydemeo.com/?p=78)

      The attached patch simply unconditionally removes the sections of code
      that add -no-cpp-precomp, with the assumption that users trying to
      compile vim on OS X 10.2 or lower can simply use a newer compiler. I
      can try to detect Apple GCC 2.95 to enable it if necessary, but
      unfortunately I don't have a Mac running an OS older than 10.4 so I
      can't test for that case.

      Best,
      Misty De Meo

      --
      --
      You received this message from the "vim_dev" maillist.
      Do not top-post! Type your reply below the text you are replying to.
      For more information, visit http://www.vim.org/maillist.php

      ---
      You received this message because you are subscribed to the Google Groups "vim_dev" group.
      To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
    • Bram Moolenaar
      ... Thanks. It should be possible to have a check for OX X 10.2 or earlier. I believe that the compilation fails in bad ways otherwise, if I remember
      Message 2 of 3 , Oct 20 1:15 PM
        Misty De Meo wrote:

        > Vim currently unconditionally adds the -no-cpp-precomp flag on Mac OS
        > X, with a comment that it's "needed for OS X 10.2". The flag currently
        > does nothing in modern versions of OS X (the last version of Apple GCC
        > that actually did anything with it was released in December, 2002),
        > and prevents vim from being built with non-Apple compilers. For
        > example, FSF GCC 4.8 will fail due to the unrecognized flag. (There's
        > some more information on this in my blog post about it:
        > http://www.mistydemeo.com/?p=78)
        >
        > The attached patch simply unconditionally removes the sections of code
        > that add -no-cpp-precomp, with the assumption that users trying to
        > compile vim on OS X 10.2 or lower can simply use a newer compiler. I
        > can try to detect Apple GCC 2.95 to enable it if necessary, but
        > unfortunately I don't have a Mac running an OS older than 10.4 so I
        > can't test for that case.

        Thanks. It should be possible to have a check for OX X 10.2 or earlier.
        I believe that the compilation fails in bad ways otherwise, if I
        remember correctly (used this on my old Powerbook, haven't used it in a
        long time).

        --
        Life is a gift, living is an art. (Bram Moolenaar)

        /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
        /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
        \\\ an exciting new programming language -- http://www.Zimbu.org ///
        \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

        --
        --
        You received this message from the "vim_dev" maillist.
        Do not top-post! Type your reply below the text you are replying to.
        For more information, visit http://www.vim.org/maillist.php

        ---
        You received this message because you are subscribed to the Google Groups "vim_dev" group.
        To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe@....
        For more options, visit https://groups.google.com/groups/opt_out.
      • Misty De Meo
        Sounds good, though I d rather not scope the patch to 10.2 unconditionally - that just reintroduces the same issue for Jaguar users who want to use FSF GCC to
        Message 3 of 3 , Oct 20 11:27 PM
          Sounds good, though I'd rather not scope the patch to 10.2
          unconditionally - that just reintroduces the same issue for Jaguar
          users who want to use FSF GCC to bring themselves up to date.
          Unfortunately, I don't have a Mac with gcc-2.95 so I can't confirm
          what the version string looks like to write a patch for it. The source
          is online though, so it probably resembles this string:
          http://opensource.apple.com/source/gcc/gcc-937.2/gcc/version.c It
          looks like this specific build of gcc-2.95 is the only one that Apple
          shipped with cpp-precomp so that's probably the only one that needs to
          be checked for. Too bad they don't include "Apple" in the string like
          usual though.

          Best,
          Misty

          On Sun, Oct 20, 2013 at 1:15 PM, Bram Moolenaar <Bram@...> wrote:
          >
          > Misty De Meo wrote:
          >
          >> Vim currently unconditionally adds the -no-cpp-precomp flag on Mac OS
          >> X, with a comment that it's "needed for OS X 10.2". The flag currently
          >> does nothing in modern versions of OS X (the last version of Apple GCC
          >> that actually did anything with it was released in December, 2002),
          >> and prevents vim from being built with non-Apple compilers. For
          >> example, FSF GCC 4.8 will fail due to the unrecognized flag. (There's
          >> some more information on this in my blog post about it:
          >> http://www.mistydemeo.com/?p=78)
          >>
          >> The attached patch simply unconditionally removes the sections of code
          >> that add -no-cpp-precomp, with the assumption that users trying to
          >> compile vim on OS X 10.2 or lower can simply use a newer compiler. I
          >> can try to detect Apple GCC 2.95 to enable it if necessary, but
          >> unfortunately I don't have a Mac running an OS older than 10.4 so I
          >> can't test for that case.
          >
          > Thanks. It should be possible to have a check for OX X 10.2 or earlier.
          > I believe that the compilation fails in bad ways otherwise, if I
          > remember correctly (used this on my old Powerbook, haven't used it in a
          > long time).
          >
          > --
          > Life is a gift, living is an art. (Bram Moolenaar)
          >
          > /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net \\\
          > /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
          > \\\ an exciting new programming language -- http://www.Zimbu.org ///
          > \\\ help me help AIDS victims -- http://ICCF-Holland.org ///

          --
          --
          You received this message from the "vim_dev" maillist.
          Do not top-post! Type your reply below the text you are replying to.
          For more information, visit http://www.vim.org/maillist.php

          ---
          You received this message because you are subscribed to the Google Groups "vim_dev" group.
          To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscribe@....
          For more options, visit https://groups.google.com/groups/opt_out.
        Your message has been successfully submitted and would be delivered to recipients shortly.