Re: Build problem and problem with region in 21.5 under Cygwin.

Rick Rankin <[email protected]>
Newsgroups gmane.emacs.xemacs.beta,gmane.emacs.xemacs.windows
Message-ID <[email protected]>
--- "Stephen J. Turnbull" wrote:
> >>>>> "Rick" == Rick Rankin writes:
> 
>     Rick> I just made my first pass at building 21.5 on Cygwin. So
>     Rick> far, I've found a (minor) problem with the build and a
>     Rick> runtime problem that I haven't been able to figure out.
> 
>     Rick> The build problem was fairly simple. There was a conflict
>     Rick> between some typedefs in src/lisp.h and
>     Rick> /usr/include/cygwin/types.h. The conflicting lines are
> 
> Something is very wrong.  Viz ChangeLog:
> 
> 2003-05-02  Stephen J. Turnbull  <[email protected]>
> 
> 	* configure.in (darwin): Collect random kludges in one place.
> 	(cygwin): Check for intptr_t in <sys/types.h>.
> 	(Berkeley db): Handle 4.1 functions decorated with version info.
> 
> and the build Just Worked for me.  Your Installation claims:
> 
>     Rick> XEmacs 21.5-b13 "cauliflower"  configured for `i686-pc-cygwin'.
> 
> but I don't think I believe it.  How did you get the source code, ftp,
> CVS?  Please
> 
> grep -i intptr_t configure.in configure src/config.h src/config.h.in
> src/lisp.h
> 
> and let's see if there's something missing.  Maybe all you have to do
> is "autoconf configure.in > configure".
> 
> If it's CVS and you've got decent connectivity, "cvs diff -r r21-5-13"
> would be useful, too.

Stephen,

The build problem went away when I checked out the source again using the tag
'r21-5-13', and running "cvs diff -r r21-5-13" as you suggested indicates that
I do now have a valid source tree. However, I still have the runtime problem
with the mark. I've tried renaming my $HOME/.emacs file (I've not converted to
$HOME/.xemacs/init.el) to eliminate any possibility that something there is
causing the problem, but the behavior is identical.

Any time I try to set the mark with C-@ or M-x set-mark-command, I get the
message

Symbol's value as variable is void: region

with the following backtrace when debug-on-error is set to true

Signaling: (void-variable region)
  zmacs-make-extent-for-region((#<marker at 395 in *scratch* 0x1028c8dc> .
#<marker at 395 in *scratch* 0x1028c8c4>))
  zmacs-activate-region()
  push-mark(nil nil t)
  set-mark-command(nil)
  call-interactively(set-mark-command)
  command-execute(set-mark-command t)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)

If I try highlighting text with the mouse, the text highlights as I drag the
mouse cursor, but I get the above message when I release the button, although
the backtrace is a bit different:

Signaling: (void-variable region)
  zmacs-make-extent-for-region((#<marker at 3 in *scratch* 0x1028c8dc> .
#<marker at 1 in *scratch* 0x1028c8c4>))
  zmacs-activate-region()
  default-mouse-track-maybe-own-selection((1 . 3) PRIMARY)
  default-mouse-track-drag-up-hook(#<buttonup-event button1up> 1)
  apply(default-mouse-track-drag-up-hook #<buttonup-event button1up> 1)
  mouse-track-run-hook(mouse-track-drag-up-hook nil #<buttonup-event button1up>
1)
  mouse-track(#<buttonup-event button1up>)
  call-interactively(mouse-track)
  recursive-edit()
  byte-code("..." [print-escape-newlines print-length debugger-buffer
debugger-value standard-output debugger-args pop-to-buffer erase-buffer t 50
backtrace debugger-mode re-search-forward "\n[* ] debug(" 1 debugger-reenable
(lambda debug) "Entering:\n" debug backtrace-debug 3 delete-char ?* 0 exit
"Return value: " prin1 ?\n ?\  error "Signaling: " "Beginning evaluation of
function call form:\n" nil message "" recursive-edit buffer-read-only
inhibit-trace] 3)
  debug(error (void-variable region))
  zmacs-make-extent-for-region((#<marker at 3 in *scratch* 0x1028c8dc> .
#<marker at 1 in *scratch* 0x1028c8c4>))
  zmacs-activate-region()
  push-mark(nil nil t)
  set-mark-command(nil)
  call-interactively(set-mark-command)
  command-execute(set-mark-command t)
  execute-extended-command(nil)
  call-interactively(execute-extended-command)

Just for completeness, here's the output of running "cvs diff -r r21-5-13"
against my current source tree:

cvs server: Diffing .
cvs server: Diffing dynodump
cvs server: Diffing dynodump/i386
cvs server: Diffing dynodump/ppc
cvs server: Diffing dynodump/sparc
cvs server: Diffing etc
cvs server: Diffing etc/custom
cvs server: Diffing etc/custom/example-themes
cvs server: Diffing etc/eos
cvs server: Diffing etc/idd
cvs server: Diffing etc/photos
cvs server: Diffing etc/sparcworks
cvs server: Diffing etc/tests
cvs server: Diffing etc/tests/external-widget
cvs server: Diffing etc/toolbar
cvs server: Diffing etc/unicode
cvs server: Diffing etc/unicode/ibm
cvs server: Diffing etc/unicode/mule-ucs
cvs server: Diffing etc/unicode/other
cvs server: Diffing etc/unicode/unicode-consortium
cvs server: Diffing info
cvs server: Diffing lib-src
cvs server: Diffing lisp
cvs server: Diffing lisp/mule
cvs server: Diffing lisp/term
cvs server: Diffing lock
cvs server: Diffing lwlib
cvs server: Diffing man
cvs server: Diffing man/internals
cvs server: Diffing man/lispref
cvs server: Diffing man/new-users-guide
cvs server: Diffing man/xemacs
cvs server: Diffing modules
cvs server: Diffing modules/base64
cvs server: Diffing modules/common
cvs server: Diffing modules/ldap
cvs server: Diffing modules/postgresql
cvs server: cannot find modules/postgresql/configure
cvs server: Diffing modules/sample
cvs server: Diffing modules/sample/external
cvs server: Diffing modules/sample/internal
cvs server: Diffing modules/zlib
cvs server: Diffing netinstall
cvs server: Diffing nt
cvs server: Diffing nt/installer
cvs server: Diffing nt/installer/Wise
cvs server: Diffing src
cvs server: Diffing src/m
cvs server: Diffing src/s
cvs server: Diffing tests
cvs server: Diffing tests/DLL
cvs server: Diffing tests/Dnd
cvs server: Diffing tests/automated
cvs server: Diffing tests/gtk
cvs server: Diffing tests/mule
cvs server: Diffing tests/tooltalk

Do you or anyone else have any suggestions?

Thanks,

--Rick
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.