all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <oneingray@gmail.com>
To: 16001@debbugs.gnu.org
Cc: Ivan Shmakov <oneingray@gmail.com>
Subject: bug#16001: [5ef95e85] fails to build with --enable-gcc-warnings in some configurations
Date: Sat, 30 Nov 2013 18:15:45 +0000	[thread overview]
Message-ID: <87li05bvse.fsf@violet.siamics.net> (raw)
In-Reply-To: <0BB9EA99-8478-4026-ABFA-8828F793CA5B@swipnet.se> ("Jan \=\?utf-8\?Q\?Dj\=C3\=A4rv\=22's\?\= message of "Sat, 30 Nov 2013 14:32:30 +0100")

>>>>> Jan Djärv <jan.h.d@swipnet.se> writes:
>>>>> 29 nov 2013 kl. 18:02 skrev Ivan Shmakov <oneingray@gmail.com>:

 >> As of 5ef95e85, building with GCC 4.8.2, --enable-gcc-warnings,
 >> --without-x-toolkit, and GnuTLS 2, fails with:

[…]

 > There are lot of new errors in window.c, xterm.c and xdisp.c after
 > the pixelwise resize checkin, so this report is kind of obsolete.

	JFTR, while I didn’t look at the current state of the code,
	“pixelwise resize” seem to be something related to the Emacs
	support for graphical terminals.  However, the xfaces.c issue is
	likely to only manifest itself when building Emacs with no such
	support enabled (IOW, character cell only; which is what I did.)

	The gnutls.c issue isn’t entirely dissimilar, as it’s likely to
	arise only in some configurations, but not the others.

 > But I checked in fixes for the issues below.

	ACK, thanks.

-- 
FSF associate member #7257





      parent reply	other threads:[~2013-11-30 18:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-29 17:02 bug#16001: [5ef95e85] fails to build with --enable-gcc-warnings in some configurations Ivan Shmakov
2013-11-30 13:32 ` Jan Djärv
2013-11-30 16:26   ` martin rudalics
2013-11-30 18:15   ` Ivan Shmakov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87li05bvse.fsf@violet.siamics.net \
    --to=oneingray@gmail.com \
    --cc=16001@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.