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

Vim, win64, mingw, compiling HEAD, xpm trouble ?

Expand Messages
  • Marc Weber
    I m trying to reproduce a Vim Python related encoding bug in my UltiSnips fork which was reported. Therefore I need to compile Vim x64 on Windows.
    Message 1 of 8 , Jul 24, 2013
    • 0 Attachment
      I'm trying to reproduce a Vim Python related encoding bug in my
      UltiSnips fork which was reported.

      Therefore I need to compile Vim x64 on Windows.

      jx86-64/xpm_w32.o gobjx86-64/gui.o gobjx86-64/gui_w32.o gobjx86-64/gui_beval.o g
      objx86-64/os_w32exe.o -lkernel32 -luser32 -lgdi32 -ladvapi32 -lcomdlg32 -lcomctl 32 -lversion -L xpm/x64/lib -lXpm -lole32 -luuid mingw32-make[1]: Leaving directory
      `C:/MinGW/msys/1.0/home/m/vim2/src/GvimExt'
      gobjx86-64/xpm_w32.o:xpm_w32.c:(.text+0x59): undefined reference to `XpmReadFileToImage'
      gobjx86-64/xpm_w32.o:xpm_w32.c:(.text+0xb8): undefined reference to `XDestroyImage'
      collect2: ld gab 1 als Ende-Status zur?ck
      mingw32-make: *** [gvim.exe] Error 1

      command I used for compiling

      $ mingw32-make.exe -f Make_ming.mak ARCH=x86-64 FEATURES=BIG GUI=yes
      OLE=no NETBEANS=no PYTHON="c:/Python27" DYNAMIC_PYTHON=yes PYTHON_VER=27
      PYTHON3="c:/Python33" DYNAMIC_PYTHON3=yes PYTHON3_VER=33 -j2

      With XPM=no then I get "xpm.h" not found. Version: fresh hg clone

      Is this the supposed way to compile Vim on Windows ?

      Marc Weber

      --
      --
      You received this message from the "vim_use" 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_use" group.
      To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@....
      For more options, visit https://groups.google.com/groups/opt_out.
    • Sergey Khorev
      Hi Marc, objx86-64/os_w32exe.o -lkernel32 -luser32 -lgdi32 -ladvapi32 -lcomdlg32 ... Can you try without MSYS? This worked fine for me in cmd.exe:
      Message 2 of 8 , Jul 24, 2013
      • 0 Attachment
        Hi Marc,

            objx86-64/os_w32exe.o -lkernel32 -luser32 -lgdi32 -ladvapi32 -lcomdlg32 -lcomctl 32 -lversion -L xpm/x64/lib -lXpm -lole32 -luuid mingw32-make[1]: Leaving directory
            `C:/MinGW/msys/1.0/home/m/vim2/src/GvimExt'
            gobjx86-64/xpm_w32.o:xpm_w32.c:(.text+0x59): undefined reference to `XpmReadFileToImage'
            gobjx86-64/xpm_w32.o:xpm_w32.c:(.text+0xb8): undefined reference to `XDestroyImage'
            collect2: ld gab 1 als Ende-Status zur?ck
            mingw32-make: *** [gvim.exe] Error 1

        command I used for compiling

        $ mingw32-make.exe -f Make_ming.mak ARCH=x86-64 FEATURES=BIG GUI=yes
        OLE=no NETBEANS=no PYTHON="c:/Python27" DYNAMIC_PYTHON=yes PYTHON_VER=27
        PYTHON3="c:/Python33" DYNAMIC_PYTHON3=yes PYTHON3_VER=33 -j2



        Can you try without MSYS?
        This worked fine for me in cmd.exe:
        mingw32-make.exe -f Make_ming.mak ARCH=x86-64 FEATURES=BIG GUI=yes OLE=no NETBEANS=no PYTHON=d:/Develop/Python27 DYNAMIC_PYTHON=yes PYTHON_VER=27 PYTHON3=d:/Develop/Python32 DYNAMIC_PYTHON3=yes PYTHON3_VER=32


        E:\vim\src>gcc --version
        gcc.EXE (rubenvb-4.6.3) 4.6.3

        E:\vim\src>mingw32-make --version
        GNU Make 3.82
        Built for i386-pc-mingw32

        --
        --
        You received this message from the "vim_use" 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_use" group.
        To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@....
        For more options, visit https://groups.google.com/groups/opt_out.
         
         
      • Nikolay Pavlov
        ... gobjx86-64/gui_beval.o g ... -lcomdlg32 -lcomctl 32 -lversion -L xpm/x64/lib -lXpm -lole32 -luuid mingw32-make[1]: Leaving directory ...
        Message 3 of 8 , Jul 24, 2013
        • 0 Attachment


          On Jul 24, 2013 2:28 PM, "Marc Weber" <marco-oweber@...> wrote:
          >
          > I'm trying to reproduce a Vim Python related encoding bug in my
          > UltiSnips fork which was reported.
          >
          > Therefore I need to compile Vim x64 on Windows.
          >
          >     jx86-64/xpm_w32.o gobjx86-64/gui.o gobjx86-64/gui_w32.o gobjx86-64/gui_beval.o g
          >     objx86-64/os_w32exe.o -lkernel32 -luser32 -lgdi32 -ladvapi32 -lcomdlg32 -lcomctl 32 -lversion -L xpm/x64/lib -lXpm -lole32 -luuid mingw32-make[1]: Leaving directory
          >     `C:/MinGW/msys/1.0/home/m/vim2/src/GvimExt'
          >     gobjx86-64/xpm_w32.o:xpm_w32.c:(.text+0x59): undefined reference to `XpmReadFileToImage'
          >     gobjx86-64/xpm_w32.o:xpm_w32.c:(.text+0xb8): undefined reference to `XDestroyImage'
          >     collect2: ld gab 1 als Ende-Status zur?ck
          >     mingw32-make: *** [gvim.exe] Error 1
          >
          > command I used for compiling
          >
          > $ mingw32-make.exe -f Make_ming.mak ARCH=x86-64 FEATURES=BIG GUI=yes
          > OLE=no NETBEANS=no PYTHON="c:/Python27" DYNAMIC_PYTHON=yes PYTHON_VER=27
          > PYTHON3="c:/Python33" DYNAMIC_PYTHON3=yes PYTHON3_VER=33 -j2
          >
          > With XPM=no then I get "xpm.h" not found. Version: fresh hg clone
          >
          > Is this the supposed way to compile Vim on Windows ?

          I use similar (some VAR=val pairs are not present, some more are there, but make -f uses the same file) for cross-compiling vim for windows on my Gentoo system: https://sourceforge.net/p/vimpluginloader/dev-tools/ci/default/tree/build.zsh.

          > Marc Weber
          >
          > --
          > --
          > You received this message from the "vim_use" 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_use" group.
          > To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@....
          > For more options, visit https://groups.google.com/groups/opt_out.
          >
          >

          --
          --
          You received this message from the "vim_use" 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_use" group.
          To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@....
          For more options, visit https://groups.google.com/groups/opt_out.
           
           
        • Marc Weber
          ... Without MSYS there is neither mingw32-make nor gcc !? Do I have to change PATH then? Anyway, the user sent me his exe and python.dll files, but vim crashed
          Message 4 of 8 , Jul 24, 2013
          • 0 Attachment
            > Can you try without MSYS?
            Without MSYS there is neither mingw32-make nor gcc !?

            Do I have to change PATH then?

            Anyway, the user sent me his exe and python.dll files, but vim
            crashed as soon as I tried any :py command. Is this because he compiled
            with python at f: instead of c: ?

            Marc Weber

            --
            --
            You received this message from the "vim_use" 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_use" group.
            To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@....
            For more options, visit https://groups.google.com/groups/opt_out.
          • Sergey Khorev
            ... Yes, you will need to add paths to make and gcc ... I don t think so. Probably it has something to do with incompatible builds of Python dlls. -- -- You
            Message 5 of 8 , Jul 24, 2013
            • 0 Attachment
              > Can you try without MSYS?
              Without MSYS there is neither mingw32-make nor gcc !?

              Do I have to change PATH then?

              Yes, you will need to add paths to make and gcc
               
              Anyway, the user sent me his exe and python.dll files, but vim
              crashed as soon as I tried any :py command. Is this because he compiled
              with python at f: instead of c: ?


              I don't think so. Probably it has something to do with incompatible builds of Python dlls.

              --
              --
              You received this message from the "vim_use" 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_use" group.
              To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@....
              For more options, visit https://groups.google.com/groups/opt_out.
               
               
            • Marc Weber
              Having set PATH to C: mingw bin only caused the same error Marc Weber -- -- You received this message from the vim_use maillist. Do not top-post! Type your
              Message 6 of 8 , Jul 24, 2013
              • 0 Attachment
                Having set PATH to C:\mingw\bin only caused the same error

                Marc Weber

                --
                --
                You received this message from the "vim_use" 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_use" group.
                To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@....
                For more options, visit https://groups.google.com/groups/opt_out.
              • Sergey Khorev
                ... Btw on Windows 7 x64 I can easily crash Vim compiled with Python 2.7.5 and 3.2.5 with :py3 print(1+2). At the same time :py is working correctly. -- -- You
                Message 7 of 8 , Jul 24, 2013
                • 0 Attachment



                  On Wed, Jul 24, 2013 at 3:51 PM, Nikolay Pavlov <zyx.vim@...> wrote:

                  I use similar (some VAR=val pairs are not present, some more are there, but make -f uses the same file) for cross-compiling vim for windows on my Gentoo system: https://sourceforge.net/p/vimpluginloader/dev-tools/ci/default/tree/build.zsh.


                  Btw on Windows 7 x64 I can easily crash Vim compiled with Python 2.7.5 and 3.2.5 with :py3 print(1+2). At the same time :py is working correctly.

                  --
                  --
                  You received this message from the "vim_use" 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_use" group.
                  To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@....
                  For more options, visit https://groups.google.com/groups/opt_out.
                   
                   
                • Nikolay Pavlov
                  ... but make -f uses the same file) for cross-compiling vim for windows on my Gentoo system:
                  Message 8 of 8 , Jul 24, 2013
                  • 0 Attachment


                    On Jul 24, 2013 7:45 PM, "Sergey Khorev" <sergey.khorev@...> wrote:
                    >
                    >
                    >
                    >
                    > On Wed, Jul 24, 2013 at 3:51 PM, Nikolay Pavlov <zyx.vim@...> wrote:
                    >>
                    >> I use similar (some VAR=val pairs are not present, some more are there, but make -f uses the same file) for cross-compiling vim for windows on my Gentoo system: https://sourceforge.net/p/vimpluginloader/dev-tools/ci/default/tree/build.zsh.
                    >
                    >
                    > Btw on Windows 7 x64 I can easily crash Vim compiled with Python 2.7.5 and 3.2.5 with :py3 print(1+2). At the same time :py is working correctly.

                    Same issue here, but with wine and i686-pc-mingw32. Python is always compiled with dynamic linking, but for this reason python 3 is disabled in winesetup.pl script lying near (this also disables compilation option).

                    --
                    --
                    You received this message from the "vim_use" 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_use" group.
                    To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+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.