GNU bug report logs - #21301
25.0.50; Emacs Trunk: Fringe bitmaps confuse foreground/background colors.

Previous Next

Package: emacs;

Reported by: Keith David Bershatsky <esq <at> lawlist.com>

Date: Thu, 20 Aug 2015 20:01:02 UTC

Severity: normal

Merged with 21561

Found in version 25.0.50

Done: Anders Lindgren <andlind <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #38 received at 21301 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Keith David Bershatsky <esq <at> lawlist.com>
Cc: 21301 <at> debbugs.gnu.org
Subject: Re: bug#21301: 25.0.50;
 Emacs Trunk:  Fringe bitmaps confuse foreground/background colors.
Date: Sat, 29 Aug 2015 19:34:47 +0300
> Date:  Sat, 29 Aug 2015 09:15:02 -0700
> From:  Keith David Bershatsky <esq <at> lawlist.com>
> Cc:  21301 <at> debbugs.gnu.org
> 
> I reverted 67a878f, but was unable to build due to the following error:
> 
> ***
> 
> fontset.c: In function 'Finternal_char_font':
> fontset.c:1878: warning: comparison is always true due to limited range of data type
> fontset.c:1878: warning: comparison is always true due to limited range of data type
> fontset.c:1878: warning: comparison is always true due to limited range of data type
> fontset.c:1878: warning: comparison is always true due to limited range of data type
>   CC       fringe.o
>   CC       image.o
>   CC       nsterm.o
>   CC       nsfns.o
>   CC       nsmenu.o
>   CC       nsselect.o
>   CC       nsimage.o
> nsimage.m: In function '-[EmacsImage initFromSkipXBM:width:height:flip:length:]':
> nsimage.m:244: error: 'bpr' undeclared (first use in this function)
> nsimage.m:244: error: (Each undeclared identifier is reported only once
> nsimage.m:244: error: for each function it appears in.)
> make[1]: *** [nsimage.o] Error 1
> make: *** [src] Error 2

Can you build Emacs for the last commit before 67a878f, and see if the
problem exists?  If it doesn't, then build the tree as it was after
67a878f was committed; if the problem reappears, we will then know
this is the culprit.

Alternatively, "git bisect" between the last commit on May 14th and
the first commit on May 17th, and see which commit introduced the
problem.

Thanks.




This bug report was last modified 9 years and 202 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.