Build error in screen.c in Tiny and Small after applying patches 2028 to 2031

8 views
Skip to first unread message

Tony Mechelynck

unread,
Sep 14, 2019, 4:40:44 PM9/14/19
to Bram Moolenaar, vim_dev
Build error in screen.c in Tiny and Small after applying patches
8.1.2028 to 8.1.2031. No change after 8.1.2032.

screen.c: In function ‘win_line’:
screen.c:5386:10: error: ‘line_attr’ undeclared (first use in this
function); did you mean ‘win_attr’?
if (line_attr)
^~~~~~~~~
win_attr
screen.c:5386:10: note: each undeclared identifier is reported only
once for each function it appears in
make: *** [Makefile:3336: objects/screen.o] Error 1
exit status 2


Best regards,
Tony.

Bram Moolenaar

unread,
Sep 14, 2019, 4:51:31 PM9/14/19
to vim...@googlegroups.com, Tony Mechelynck
Travis was not picking up builds, so it took a while before I noticed.
Fixed with 8.1.2033.

--
hundred-and-one symptoms of being an internet addict:
261. You find diskettes in your pockets when doing laundry.

/// Bram Moolenaar -- Br...@Moolenaar.net -- 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 ///

Tony Mechelynck

unread,
Sep 14, 2019, 5:17:25 PM9/14/19
to Bram Moolenaar, vim_dev
On Sat, Sep 14, 2019 at 10:51 PM Bram Moolenaar <Br...@moolenaar.net> wrote:
>
>
> Tony wrote:
>
> > Build error in screen.c in Tiny and Small after applying patches
> > 8.1.2028 to 8.1.2031. No change after 8.1.2032.
> >
> > screen.c: In function ‘win_line’:
> > screen.c:5386:10: error: ‘line_attr’ undeclared (first use in this
> > function); did you mean ‘win_attr’?
> > if (line_attr)
> > ^~~~~~~~~
> > win_attr
> > screen.c:5386:10: note: each undeclared identifier is reported only
> > once for each function it appears in
> > make: *** [Makefile:3336: objects/screen.o] Error 1
> > exit status 2
>
> Travis was not picking up builds, so it took a while before I noticed.
> Fixed with 8.1.2033.

Yeah, I saw it practically as soon as I'd sent this problem report.

Best regards,
Tony.
Reply all
Reply to author
Forward
0 new messages