all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yavor Doganov <yavor@gnu.org>
To: 647@emacsbugs.donarmstrong.com
Subject: bug#647: 23.0.60; NSInteger changes in nsterm.h break the GNUstep build
Date: Tue, 05 Aug 2008 21:21:24 +0300	[thread overview]
Message-ID: <87zlnr9vbv.GNU's_Not_Unix!%yavor@gnu.org> (raw)

reopen 647
tags 647 + patch
thanks

I just tried with an older version of GNUstep Base (1.14.1) and
because of a typo in the fix of this bug, NS_HAVE_INTEGER is
unconditionally defined -- so the build fails.

*** configure.in	05 авг 2008 21:06:42 +0300	1.553
--- configure.in	05 авг 2008 21:07:00 +0300	
***************
*** 2054,2062 ****
    if test "${NS_IMPL_GNUSTEP}" = "yes"; then
      AC_DEFINE(NS_IMPL_GNUSTEP, 1, [Define to 1 if you are using NS windowing under GNUstep.])
    fi
!   dnl if test "${NS_HAVE_INTEGER}" = "yes"; then
      AC_DEFINE(NS_HAVE_INTEGER, 1, [Define to 1 if `NSInteger' is defined.])
!   dnl fi
    # We also have mouse menus.
    HAVE_MENUS=yes
  fi
--- 2054,2062 ----
    if test "${NS_IMPL_GNUSTEP}" = "yes"; then
      AC_DEFINE(NS_IMPL_GNUSTEP, 1, [Define to 1 if you are using NS windowing under GNUstep.])
    fi
!   if test "${NS_HAVE_INTEGER}" = "yes"; then
      AC_DEFINE(NS_HAVE_INTEGER, 1, [Define to 1 if `NSInteger' is defined.])
!   fi
    # We also have mouse menus.
    HAVE_MENUS=yes
  fi






             reply	other threads:[~2008-08-05 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-05 18:21 Yavor Doganov [this message]
2008-08-05 18:30 ` Processed: Re: 23.0.60; NSInteger changes in nsterm.h break the GNUstep build Emacs bug Tracking System
  -- strict thread matches above, loose matches on Subject: below --
2008-08-04 16:05 bug#647: " Chong Yidong
2008-08-04 17:40 ` Yavor Doganov
2008-08-04 14:24 Yavor Doganov

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='87zlnr9vbv.GNU'\''s_Not_Unix'\!'%yavor@gnu.org' \
    --to=yavor@gnu.org \
    --cc=647@emacsbugs.donarmstrong.com \
    /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.