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

Re: patched vim on pc?

Expand Messages
  • Bruce Mellows
    The Make_bc5.mak defaults to yes for MBYTE, ICONV and DYNAMIC_IME, so I have them compiled in I believe (I don t currently have any modifications to my
    Message 1 of 22 , Jun 30, 2002
      The Make_bc5.mak defaults to "yes" for MBYTE, ICONV and DYNAMIC_IME, so
      I have them compiled in I believe (I don't currently have any
      modifications to my checkout), not that I use multi-byte etc, but they
      appear to be enabled.

      I updated and compiled this morning (my timezone is +1000).

      :version

      VIM - Vi IMproved 6.1 (2002 Mar 24, compiled Jul 1 2002 09:00:36)
      MS-Windows 32 bit GUI version
      Included patches: 1-118
      Big version with GUI. Features included (+) or not (-):
      +autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent
      +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
      +comments
      +cryptv -cscope +dialog_gui +diff +digraphs -ebcdic +emacs_tags +eval
      +ex_extra +extra_search +farsi +file_in_path +find_in_path +folding -footer
      +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist +keymap
      +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu
      +mksession
      +modify_fname +mouse +mouseshape +multi_byte_ime/dyn +multi_lang -ole
      -osfiletype +path_extra -perl -postscript +printer -python +quickfix
      +rightleft -ruby +scrollbind +signs +smartindent -sniff +statusline
      -sun_workshop +syntax +tag_binary +tag_old_static -tag_any_white -tcl
      -tgetent -termresponse +textobjects +title +toolbar +user_commands
      +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace
      +wildignore +wildmenu +windows
      +writebackup -xfontset -xim -xterm_save
      system vimrc file: "$VIM\vimrc"
      user vimrc file: "$HOME\_vimrc"
      2nd user vimrc file: "$VIM\_vimrc"
      user exrc file: "$HOME\_exrc"
      2nd user exrc file: "$VIM\_exrc"
      system gvimrc file: "$VIM\gvimrc"
      user gvimrc file: "$HOME\_gvimrc"
      2nd user gvimrc file: "$VIM\_gvimrc"
      system menu file: "$VIMRUNTIME\menu.vim"

      P. Alejandro Lopez-Valencia wrote:

      >----- Original Message -----
      >From: "Bruce Mellows" <bruce@...>
      >To: "vim-dev" <vim-dev@...>
      >Sent: Sunday, June 30, 2002 6:01 PM
      >Subject: Re: patched vim on pc?
      >
      >
      >
      >
      >>Compiling using BC5.5 is an off-the-shelf operation - follow the
      >>
      >>
      >readme
      >
      >I'll ignore this, but watch your fingers next time :)
      >
      >
      One last thing (Columbo style), what do you mean by "watch you fingers"

      >
      >
      >>alternately, in a shell that is set up to use the borland compiler
      >>set BOR=%boland_compiler_base_dir%
      >>set CPU=6
      >>:: take your pick
      >>set GUI=yes
      >>set GUI=no
      >>cd src
      >>make -f Make_bc5.mak
      >>
      >>
      >>
      >
      >No, it doesn't work for me, *at all*. All binaries I've produced fail
      >with threading problems (and I am talking about trying at least 30 times
      >in the last four months) or dll entry point failures, if I examine it
      >with Dependency Walker. With GNU objdump, I see lots of entry point
      >relocations, I suspect that the incremental linker is messing things up,
      >it may be related with the fact that I do need MBYE, ICONV and
      >DYNAMIC_IME (having to write sometimes in non-western languages and
      >dealing with text in different vector encodings...).
      >
      >
      >
      >
      >
      >
    • P. Alejandro Lopez-Valencia
      ... From: Bruce Mellows To: vim-dev Sent: Sunday, June 30, 2002 7:34 PM Subject: Re: patched vim on pc? ... so ...
      Message 2 of 22 , Jul 1 4:26 AM
        ----- Original Message -----
        From: "Bruce Mellows" <bruce@...>
        To: "vim-dev" <vim-dev@...>
        Sent: Sunday, June 30, 2002 7:34 PM
        Subject: Re: patched vim on pc?


        > The Make_bc5.mak defaults to "yes" for MBYTE, ICONV and DYNAMIC_IME,
        so
        > I have them compiled in I believe (I don't currently have any
        > modifications to my checkout), not that I use multi-byte etc, but they
        > appear to be enabled.
        >
        > I updated and compiled this morning (my timezone is +1000).
        >
        > :version
        >
        > VIM - Vi IMproved 6.1 (2002 Mar 24, compiled Jul 1 2002 09:00:36)
        > MS-Windows 32 bit GUI version
        > Included patches: 1-118
        > Big version with GUI. Features included (+) or not (-):
        > +autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent
        > +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info
        > +comments
        > +cryptv -cscope +dialog_gui +diff +digraphs -ebcdic +emacs_tags +eval
        > +ex_extra +extra_search +farsi +file_in_path +find_in_path
        +folding -footer
        > +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist +keymap
        > +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu
        > +mksession

        That's very interesting! What OS version? I am trying to do this under
        WinME. Anyway, I am downloading a new CVS cache as I write this, in case
        it is something related to file corruption.
      • P. Alejandro Lopez-Valencia
        ... From: Bruce Mellows To: vim-dev Sent: Sunday, June 30, 2002 7:34 PM Subject: Re: patched vim on pc? ... so ...
        Message 3 of 22 , Jul 1 5:47 AM
          ----- Original Message -----
          From: "Bruce Mellows" <bruce@...>
          To: "vim-dev" <vim-dev@...>
          Sent: Sunday, June 30, 2002 7:34 PM
          Subject: Re: patched vim on pc?


          > The Make_bc5.mak defaults to "yes" for MBYTE, ICONV and DYNAMIC_IME,
          so
          > I have them compiled in I believe (I don't currently have any
          > modifications to my checkout), not that I use multi-byte etc, but they
          > appear to be enabled.
          >
          > I updated and compiled this morning (my timezone is +1000).
          >
          > :version
          >
          > VIM - Vi IMproved 6.1 (2002 Mar 24, compiled Jul 1 2002 09:00:36)
          > MS-Windows 32 bit GUI version
          > Included patches: 1-118

          Hmm... I just tried it again, with a fresh CVS dump and making sure to
          convert all text files to DOS EOLs first. It *fails*. I include the
          profiler run below. Notice that I am using the getext and libiconv
          libraries from http://gnuwin32.sf.net/. The system dlls have been
          updated to the IE 5.5SP2+patches level. Not sure if I did the stub
          conversion right (what options did you use with coff2omf?).

          ------------------------------------------------------------------------
          --------
          Starting profile on 01/07/2002 at 07:39:16 a.m.

          Operating System: Microsoft Windows Me (32-bit), version 4.90.3000
          (Gold)
          Program Executable: c:\vim\vim61\GVIM_61.EXE
          Program Arguments:
          Starting Directory: C:\Vim\vim61\
          Search Path:
          c:\bcc55\bin;C:\WINDOWS;C:\WINDOWS\COMMAND;C:\archiv~1\java\j2re1.4.0_01
          \bin

          Options Selected:
          Simulate ShellExecute by inserting any App Paths directories into
          the PATH environment variable.
          Log DllMain calls for process attach and process detach messages.
          Log DllMain calls for all other messages, including thread attach
          and thread detach.
          Hook the process to gather more detailed dependency information.
          Log LoadLibrary function calls.
          Log GetProcAddress function calls.
          Log thread information.
          Use simple thread numbers instead of actual thread IDs.
          Log first chance exceptions.
          Log debug output messages.
          Use full paths when logging file names.
          Log a time stamp with each line of log.
          Automatically open and profile child processes.
          ------------------------------------------------------------------------
          --------

          00:00:00.000: Started "c:\vim\vim61\GVIM_61.EXE" (process 0xFFE72E15) at
          address 0x00400000 by thread 1. Successfully hooked module.
          00:00:00.036: Loaded "c:\windows\system\OLE32.DLL" at address 0x7FF20000
          by thread 1. Successfully hooked module.
          00:00:00.044: Loaded "c:\windows\system\MSVCRT.DLL" at address
          0x78000000 by thread 1. Successfully hooked module.
          00:00:00.120: Loaded "c:\windows\system\SHELL32.DLL" at address
          0x7FBC0000 by thread 1. Successfully hooked module.
          00:00:00.146: Loaded "c:\windows\system\SHLWAPI.DLL" at address
          0x70BD0000 by thread 1. Successfully hooked module.
          00:00:00.162: Loaded "c:\windows\system\COMDLG32.DLL" at address
          0x7FE00000 by thread 1. Successfully hooked module.
          00:00:00.170: Loaded "c:\windows\system\USER32.DLL" at address
          0xBFF40000 by thread 1. Shared module not hooked.
          00:00:00.174: Loaded "c:\windows\system\GDI32.DLL" at address 0xBFF10000
          by thread 1. Shared module not hooked.
          00:00:00.180: Loaded "c:\windows\system\COMCTL32.DLL" at address
          0xBFB70000 by thread 1. Shared module not hooked.
          00:00:00.569: Loaded "c:\windows\system\KERNEL32.DLL" at address
          0xBFF60000 by thread 1. Shared module not hooked.
          00:00:00.573: Loaded "c:\windows\system\ADVAPI32.DLL" at address
          0xBFE60000 by thread 1. Shared module not hooked.
          00:00:00.575: Entrypoint reached. All implicit modules have been loaded.
          00:00:00.583: Injected "c:\archivos de programa\reparacion de
          windows\depends21_x86\DEPENDS.DLL" at address 0x08370000 by thread 1.
          00:00:00.585: DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in
          "c:\archivos de programa\reparacion de
          windows\depends21_x86\DEPENDS.DLL" called by thread 1.
          00:00:00.614: DllMain(0x08370000, DLL_PROCESS_ATTACH, 0x00000000) in
          "c:\archivos de programa\reparacion de
          windows\depends21_x86\DEPENDS.DLL" returned 1 (0x1) by thread 1.
          00:00:01.459: DllMain(0x70BD0000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\SHLWAPI.DLL" called by thread 1.
          00:00:01.462: DllMain(0x70BD0000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\SHLWAPI.DLL" returned 1 (0x1) by thread 1.
          00:00:01.464: DllMain(0x78000000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\MSVCRT.DLL" called by thread 1.
          00:00:01.476: GetProcAddress(0xBFF60000
          [c:\windows\system\KERNEL32.DLL], "IsProcessorFeaturePresent") called
          from "c:\windows\system\MSVCRT.DLL" at address 0x78003BFF and returned
          0x8855E008 by thread 1.
          00:00:01.489: DllMain(0x78000000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\MSVCRT.DLL" returned 1 (0x1) by thread 1.
          00:00:01.491: DllMain(0x7FBC0000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\SHELL32.DLL" called by thread 1.
          00:00:01.495: DllMain(0x7FBC0000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\SHELL32.DLL" returned 1 (0x1) by thread 1.
          00:00:01.498: DllMain(0x7FE00000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\COMDLG32.DLL" called by thread 1.
          00:00:01.501: DllMain(0x7FE00000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\COMDLG32.DLL" returned 1 (0x1) by thread 1.
          00:00:01.503: DllMain(0x7FF20000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\OLE32.DLL" called by thread 1.
          00:00:01.507: DllMain(0x7FF20000, DLL_PROCESS_ATTACH, 0x00000001) in
          "c:\windows\system\OLE32.DLL" returned 1 (0x1) by thread 1.
          00:00:01.516: GetProcAddress(0x00400000 [c:\vim\vim61\GVIM_61.EXE],
          "___CPPdebugHook") called from "c:\vim\vim61\GVIM_61.EXE" at address
          0x004B3B06 and returned 0x004C1134 by thread 1.
          00:00:01.531: GetProcAddress(0x00400000 [c:\vim\vim61\GVIM_61.EXE],
          "___CPPdebugHook") called from "c:\vim\vim61\GVIM_61.EXE" at address
          0x004BEB16 and returned 0x004C1134 by thread 1.
          00:00:01.538: GetProcAddress(0xBFF60000
          [c:\windows\system\KERNEL32.DLL], "GetProcAddress") called from
          "c:\vim\vim61\GVIM_61.EXE" at address 0x004BCEFA and returned 0x08371A67
          by thread 1.
          00:00:01.553: GetProcAddress(0xBFF60000
          [c:\windows\system\KERNEL32.DLL], "Borland32") called from
          "c:\vim\vim61\GVIM_61.EXE" at address 0x004BCF02 and returned NULL by
          thread 1. Error: No se puede encontrar el mdulo especificado (126).
          00:00:01.565: LoadLibraryA("libintl.dll") called from
          "c:\vim\vim61\GVIM_61.EXE" at address 0x004AED82 by thread 1.
          00:00:01.587: Loaded "c:\vim\vim61\LIBICONV.DLL" at address 0x69500000
          by thread 1. Successfully hooked module.
          00:00:01.606: Loaded "c:\vim\vim61\LIBINTL.DLL" at address 0x67A80000 by
          thread 1. Successfully hooked module.
          00:00:01.610: DllMain(0x69500000, DLL_PROCESS_ATTACH, 0x00000000) in
          "c:\vim\vim61\LIBICONV.DLL" called by thread 1.
          00:00:01.613: DllMain(0x69500000, DLL_PROCESS_ATTACH, 0x00000000) in
          "c:\vim\vim61\LIBICONV.DLL" returned 1 (0x1) by thread 1.
          00:00:01.615: DllMain(0x67A80000, DLL_PROCESS_ATTACH, 0x00000000) in
          "c:\vim\vim61\LIBINTL.DLL" called by thread 1.
          00:00:01.620: DllMain(0x67A80000, DLL_PROCESS_ATTACH, 0x00000000) in
          "c:\vim\vim61\LIBINTL.DLL" returned 1 (0x1) by thread 1.
          00:00:01.624: LoadLibraryA("libintl.dll") returned 0x67A80000 by thread
          1.
          00:00:02.124: GetProcAddress(0x67A80000 [c:\vim\vim61\LIBINTL.DLL],
          "gettext") called from "c:\vim\vim61\GVIM_61.EXE" at address 0x004AEE28
          and returned 0x67A827F4 by thread 1.
          00:00:02.131: GetProcAddress(0x67A80000 [c:\vim\vim61\LIBINTL.DLL],
          "textdomain") called from "c:\vim\vim61\GVIM_61.EXE" at address
          0x004AEE28 and returned 0x67A828BC by thread 1.
          00:00:02.137: GetProcAddress(0x67A80000 [c:\vim\vim61\LIBINTL.DLL],
          "bindtextdomain") called from "c:\vim\vim61\GVIM_61.EXE" at address
          0x004AEE28 and returned 0x67A828D4 by thread 1.
          00:00:02.143: First chance exception 0xC0000005 (Access Violation)
          occurred in "c:\vim\vim61\GVIM_61.EXE" at address 0x004B2F18 by thread
          1.
          00:00:02.145: First chance exception 0xC0000005 (Access Violation)
          occurred in "c:\vim\vim61\GVIM_61.EXE" at address 0x004B2F18 by thread
          1.

          [messsage repeated until the process is killed]
        • Bruce Mellows
          I think your BC5.5 is fine. I *DON T* use anything but the cvs from sourceforge. From a standard shell (WIN2000,
          Message 4 of 22 , Jul 1 4:23 PM
            I think your BC5.5 is fine.

            I *DON'T* use anything but the cvs from sourceforge.

            From a standard shell (WIN2000,
            PATH=C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem), I just tested
            this on a *FRESH* cvs checkout...

            cd /d d:\sourceforge\vim\src
            set PATH=d:\bc55\bin;%PATH%
            set BOR=d:\bc55
            set CPU=6
            set GUI=yes
            make -f make_bc5.mak

            I could also try it from win98se if you think that's the problem.
          • P. Alejandro Lopez-Valencia
            ... From: Bruce Mellows To: vim-dev Sent: Monday, July 01, 2002 6:23 PM Subject: Re: patched vim on pc? ... Hmm...
            Message 5 of 22 , Jul 1 4:38 PM
              ----- Original Message -----
              From: "Bruce Mellows" <bruce@...>
              To: "vim-dev" <vim-dev@...>
              Sent: Monday, July 01, 2002 6:23 PM
              Subject: Re: patched vim on pc?


              > I think your BC5.5 is fine.
              >
              > I *DON'T* use anything but the cvs from sourceforge.
              >
              > From a standard shell (WIN2000,
              > PATH=C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem), I just tested
              > this on a *FRESH* cvs checkout...
              >
              > cd /d d:\sourceforge\vim\src
              > set PATH=d:\bc55\bin;%PATH%
              > set BOR=d:\bc55
              > set CPU=6
              > set GUI=yes
              > make -f make_bc5.mak
              >
              > I could also try it from win98se if you think that's the problem.
              >

              Hmm... Then the OS is to blame. Time to start the move to a dual
              win2k/linux system...
            • Bruce Mellows
              I just compiled it successfully on a WinME (virtual) machine... VIM - Vi IMproved 6.1 (2002 Mar 24, compiled Jul 2 2002 10:21:58) MS-Windows 32 bit GUI
              Message 6 of 22 , Jul 1 5:31 PM
                I just compiled it successfully on a WinME (virtual) machine...

                VIM - Vi IMproved 6.1 (2002 Mar 24, compiled Jul 2 2002 10:21:58)
                MS-Windows 32 bit GUI version
                Included patches: 1-118
                Big version with GUI. Features included (+) or not (-):
                +autocmd -balloon_eval +browse ++builtin_terms +byte_offset +cindent
                +clientserver +clipboard
                +cmdline_compl +cmdline_hist +cmdline_info +comments +cryptv -cscope
                +dialog_gui +diff +digraphs -ebcdic +emacs_tags +eval +ex_extra
                +extra_search +farsi +file_in_path +find_in_path +folding
                -footer +gettext/dyn -hangul_input +iconv/dyn +insert_expand +jumplist
                +keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap
                +menu +mksession +modify_fname +mouse +mouseshape
                +multi_byte_ime/dyn +multi_lang -ole -osfiletype +path_extra -perl
                -postscript +printer -python
                +quickfix +rightleft -ruby +scrollbind +signs +smartindent -sniff
                +statusline -sun_workshop
                +syntax +tag_binary +tag_old_static -tag_any_white -tcl -tgetent
                -termresponse +textobjects
                +title +toolbar +user_commands +vertsplit +virtualedit +visual
                +visualextra +viminfo +vreplace
                +wildignore +wildmenu +windows +writebackup -xfontset -xim -xterm_save
                system vimrc file: "$VIM\vimrc"
                user vimrc file: "$HOME\_vimrc"
                2nd user vimrc file: "$VIM\_vimrc"
                user exrc file: "$HOME\_exrc"
                2nd user exrc file: "$VIM\_exrc"
                system gvimrc file: "$VIM\gvimrc"
                user gvimrc file: "$HOME\_gvimrc"
                2nd user gvimrc file: "$VIM\_gvimrc"
                system menu file: "$VIMRUNTIME\menu.vim"

                The problem has got to be something in your environment.

                P. Alejandro Lopez-Valencia wrote:

                >----- Original Message -----
                >From: "Bruce Mellows" <bruce@...>
                >To: "vim-dev" <vim-dev@...>
                >Sent: Monday, July 01, 2002 6:23 PM
                >Subject: Re: patched vim on pc?
                >
                >
                >
                >
                >>I think your BC5.5 is fine.
                >>
                >>I *DON'T* use anything but the cvs from sourceforge.
                >>
                >> From a standard shell (WIN2000,
                >>PATH=C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem), I just tested
                >>this on a *FRESH* cvs checkout...
                >>
                >>cd /d d:\sourceforge\vim\src
                >>set PATH=d:\bc55\bin;%PATH%
                >>set BOR=d:\bc55
                >>set CPU=6
                >>set GUI=yes
                >>make -f make_bc5.mak
                >>
                >>I could also try it from win98se if you think that's the problem.
                >>
                >>
                >>
                >
                >Hmm... Then the OS is to blame. Time to start the move to a dual
                >win2k/linux system...
                >
                >
                >
                >
                >
              • Vlad Sandrini
                Aye Engengah P. Alejandro Lopez-Valencia H ee L geb F ai Throdog Re: patched vim on pc? Mon, 1 Jul 2002 18:38:45 -0500: PALV I could also try it from
                Message 7 of 22 , Jul 2 10:30 AM
                  Aye Engengah P. Alejandro Lopez-Valencia H'ee L'geb F'ai Throdog Re:
                  patched vim on pc? Mon, 1 Jul 2002 18:38:45 -0500:

                  PALV> > I could also try it from win98se if you think that's the
                  PALV> > problem.
                  PALV> >
                  PALV>
                  PALV> Hmm... Then the OS is to blame. Time to start the move to a dual
                  PALV> win2k/linux system...

                  Not all of us are allowed. Unxutils+Mingw works fine under NT4, just
                  compiled 6.1.118 yesterday at work.

                  I compiled 6.1.119 today but I used MSVC6 (unxutils's patch for
                  patching, as usual).


                  --
                  Sator <sator72/at/libero/dot/it> <vlad72/at/inwind/dot/it>
                  icq#906246 - http://sator.250x.com - http://www.iammol.com
                  Linux 2.4.19-rc1 - Sylpheed version 0.7.7
                  - Werewolf. - Werewolf? - There.
                Your message has been successfully submitted and would be delivered to recipients shortly.