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

Compile error in Tiny build after patchlevels 7.4.296 to 305

Expand Messages
  • Tony Mechelynck
    After pulling the changesets for patchlevels 7.4.296 to 7.4.305 and updating to the new head of the default repository branch, the following errors happen in
    Message 1 of 3 , May 22, 2014
    • 0 Attachment
      After pulling the changesets for patchlevels 7.4.296 to 7.4.305 and
      updating to the new head of the "default" repository branch, the
      following errors happen in the Tiny build only (Huge build compiles and
      links fine):

      gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
      -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/term.o term.c
      term.c: In function ‘did_request_esc_sequence’:
      term.c:3325:9: error: ‘crv_status’ undeclared (first use in this function)
      if (crv_status == CRV_GET)
      ^
      term.c:3325:9: note: each undeclared identifier is reported only once
      for each function it appears in
      term.c:3325:23: error: ‘CRV_GET’ undeclared (first use in this function)
      if (crv_status == CRV_GET)
      ^
      term.c:3327:9: error: ‘u7_status’ undeclared (first use in this function)
      if (u7_status == U7_GET)
      ^
      term.c:3327:22: error: ‘U7_GET’ undeclared (first use in this function)
      if (u7_status == U7_GET)
      ^
      term.c:3329:26: error: ‘CRV_SENT’ undeclared (first use in this function)
      return crv_status == CRV_SENT || u7_status == U7_SENT
      ^
      term.c:3329:51: error: ‘U7_SENT’ undeclared (first use in this function)
      return crv_status == CRV_SENT || u7_status == U7_SENT
      ^
      term.c:3334:1: warning: control reaches end of non-void function
      [-Wreturn-type]
      }
      ^
      make: *** [objects/term.o] Error 1
      exit status 2


      "exit status" at the end is $? as seen in the shell when "make" exits.



      Best regards,
      Tony.
      --
      Sally: C'mon, Ted, all I'm asking you to do is share your feelings
      with me.
      Ted: ALL? Do you realize what you're asking? Men aren't trained
      to share. We're trained to protect ourselves by not
      letting anyone too close. Good grief, if I go around
      sharing everything with you, you could hang me out to dry.
      Sally: It's called "trust," Ted.
      Ted: "Sharing"? "Trust"? You're really asking me to sail into
      uncharted waters here.
      -- Sally Forth

      --
      --
      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/d/optout.
    • Bram Moolenaar
      ... My tests also caught this, but they take a long time to run... I ll make a patch. -- % cat /usr/include/sys/errno.h #define EPERM 1 /* Operation not
      Message 2 of 3 , May 22, 2014
      • 0 Attachment
        Tony Mechelynck wrote:

        > After pulling the changesets for patchlevels 7.4.296 to 7.4.305 and
        > updating to the new head of the "default" repository branch, the
        > following errors happen in the Tiny build only (Huge build compiles and
        > links fine):
        >
        > gcc -c -I. -Iproto -DHAVE_CONFIG_H -O2 -fno-strength-reduce -Wall
        > -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -o objects/term.o term.c
        > term.c: In function ‘did_request_esc_sequence’:
        > term.c:3325:9: error: ‘crv_status’ undeclared (first use in this function)
        > if (crv_status == CRV_GET)
        > ^
        > term.c:3325:9: note: each undeclared identifier is reported only once
        > for each function it appears in
        > term.c:3325:23: error: ‘CRV_GET’ undeclared (first use in this function)
        > if (crv_status == CRV_GET)
        > ^
        > term.c:3327:9: error: ‘u7_status’ undeclared (first use in this function)
        > if (u7_status == U7_GET)
        > ^
        > term.c:3327:22: error: ‘U7_GET’ undeclared (first use in this function)
        > if (u7_status == U7_GET)
        > ^
        > term.c:3329:26: error: ‘CRV_SENT’ undeclared (first use in this function)
        > return crv_status == CRV_SENT || u7_status == U7_SENT
        > ^
        > term.c:3329:51: error: ‘U7_SENT’ undeclared (first use in this function)
        > return crv_status == CRV_SENT || u7_status == U7_SENT
        > ^
        > term.c:3334:1: warning: control reaches end of non-void function
        > [-Wreturn-type]
        > }
        > ^
        > make: *** [objects/term.o] Error 1
        > exit status 2
        >
        >
        > "exit status" at the end is $? as seen in the shell when "make" exits.

        My tests also caught this, but they take a long time to run...

        I'll make a patch.

        --
        % cat /usr/include/sys/errno.h
        #define EPERM 1 /* Operation not permitted */
        #define ENOENT 2 /* No such file or directory */
        #define ESRCH 3 /* No such process */
        [...]
        #define EMACS 666 /* Too many macros */
        %

        /// 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/d/optout.
      • Tony Mechelynck
        On 22/05/14 20:30, Bram Moolenaar wrote: [...] ... The only tests I run consist of building (or trying to build ;-) ) a Tiny build in addition to my Huge
        Message 3 of 3 , May 22, 2014
        • 0 Attachment
          On 22/05/14 20:30, Bram Moolenaar wrote:
          [...]
          > My tests also caught this, but they take a long time to run...
          >
          > I'll make a patch.
          >

          The only tests I run consist of building (or trying to build ;-) ) a
          Tiny build in addition to my Huge build. This doesn't catch all
          misplaced and missing #ifdef directives (I've seen cases where Huge and
          Tiny were OK but Normal wasn't) but it already catches some of them.

          I confirm that Vim 7.4.307 builds OK again for both Huge and Tiny.


          Best regards,
          Tony.
          --
          Excuse me, but didn't I tell you there's NO HOPE for the survival of
          OFFSET PRINTING?

          --
          --
          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/d/optout.
        Your message has been successfully submitted and would be delivered to recipients shortly.