From: chad brown <y@MIT.EDU>
To: emacs-devel@gnu.org
Subject: Re: CVS HEAD fails to build on OSX 10.4 (macterm.c broken?)
Date: Wed, 29 Aug 2007 13:14:56 -0700 [thread overview]
Message-ID: <F7525EDE-9C10-43DF-B4F3-9BF0BC5F6654@mit.edu> (raw)
In-Reply-To: <200708291749.l7THnAQ3014968@oogie-boogie.ics.uci.edu>
The current problem with multi-tty on macosx seems to come from
configure. Namely, this code in src/config.in:
> /* If we're using the Carbon API on Mac OS X, define a few more
> variables as well. */
> #ifdef HAVE_CARBON
> #define HAVE_WINDOW_SYSTEM
> #define HAVE_MOUSE
> /* XXX The MULTI_KBOARD support does not work yet on this platform. */
> #undef MULTI_KBOARD
> #endif
results in:
> /* If we're using the Carbon API on Mac OS X, define a few more
> variables as well. */
> #ifdef HAVE_CARBON
> #define HAVE_WINDOW_SYSTEM
> #define HAVE_MOUSE
> /* XXX The MULTI_KBOARD support does not work yet on this platform. */
> /* #undef MULTI_KBOARD */
> #endif
with the #undef MULTI_KBOARD line commented out. This seems to be a
feature of autoconf, but I'm not familiar enough with autoconf to be
sure, or figure out how to work around it. Can someone more familiar
with autoconf either fix src/config.in or tell me how to do it, so I
can verify the diagnosis (and look for further problems)?
Thanks,
*chad
next prev parent reply other threads:[~2007-08-29 20:14 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 15:14 CVS HEAD fails to build on OSX 10.4 (macterm.c broken?) Randal L. Schwartz
2007-08-29 15:31 ` Dan Nicolaescu
2007-08-29 15:42 ` Randal L. Schwartz
2007-08-29 15:45 ` Randal L. Schwartz
2007-08-29 16:04 ` Dan Nicolaescu
2007-08-29 16:08 ` Randal L. Schwartz
2007-08-29 16:28 ` Dan Nicolaescu
2007-08-30 0:33 ` YAMAMOTO Mitsuharu
2007-08-30 0:47 ` Dan Nicolaescu
2007-08-30 1:06 ` YAMAMOTO Mitsuharu
2007-08-30 1:21 ` Dan Nicolaescu
2007-08-30 1:34 ` YAMAMOTO Mitsuharu
2007-08-30 1:42 ` Dan Nicolaescu
2007-08-30 1:52 ` YAMAMOTO Mitsuharu
2007-08-30 3:10 ` Dan Nicolaescu
2007-08-30 20:50 ` Richard Stallman
2007-08-30 23:59 ` YAMAMOTO Mitsuharu
2007-08-31 18:21 ` Richard Stallman
2007-08-31 23:50 ` YAMAMOTO Mitsuharu
2007-09-01 2:06 ` Stefan Monnier
2007-09-01 8:13 ` Eli Zaretskii
2007-09-02 15:50 ` Richard Stallman
2007-09-03 20:43 ` Stefan Monnier
2007-09-04 3:06 ` Eli Zaretskii
2007-09-04 16:45 ` Richard Stallman
2007-09-04 21:29 ` Dan Nicolaescu
2007-09-05 0:16 ` YAMAMOTO Mitsuharu
2007-09-05 6:16 ` Richard Stallman
2007-09-05 14:27 ` Stefan Monnier
2007-09-06 4:59 ` Richard Stallman
2007-08-31 18:21 ` Richard Stallman
2007-08-29 16:30 ` Randal L. Schwartz
2007-08-29 16:41 ` Dan Nicolaescu
2007-08-29 16:45 ` Randal L. Schwartz
2007-08-29 16:59 ` Dan Nicolaescu
2007-08-29 17:09 ` chad brown
2007-08-29 17:18 ` chad brown
2007-08-29 17:49 ` Dan Nicolaescu
2007-08-29 20:14 ` chad brown [this message]
2007-08-29 22:05 ` Glenn Morris
2007-08-29 22:40 ` Dan Nicolaescu
2007-08-30 3:23 ` chad brown
2007-08-31 0:08 ` YAMAMOTO Mitsuharu
2007-08-31 0:53 ` Randal L. Schwartz
2007-08-31 1:03 ` YAMAMOTO Mitsuharu
2007-08-31 1:06 ` YAMAMOTO Mitsuharu
2007-08-31 8:12 ` Dan Nicolaescu
2007-08-31 10:04 ` YAMAMOTO Mitsuharu
2007-09-03 14:23 ` Randal L. Schwartz
2007-09-03 14:49 ` Jason Rumney
2007-09-04 1:01 ` YAMAMOTO Mitsuharu
2007-09-04 6:47 ` Yavor Doganov
2007-09-04 7:54 ` YAMAMOTO Mitsuharu
2007-09-04 22:58 ` Richard Stallman
2007-09-05 0:24 ` YAMAMOTO Mitsuharu
2007-09-05 20:02 ` Richard Stallman
2007-09-05 23:58 ` YAMAMOTO Mitsuharu
2007-09-06 5:53 ` Yavor Doganov
2007-09-06 8:28 ` YAMAMOTO Mitsuharu
2007-09-06 9:17 ` Yavor Doganov
2007-09-06 10:23 ` YAMAMOTO Mitsuharu
2007-09-07 6:31 ` Richard Stallman
2007-09-07 7:02 ` YAMAMOTO Mitsuharu
2007-09-08 7:00 ` Richard Stallman
2007-09-07 6:30 ` Richard Stallman
2007-09-03 14:55 ` dhruva
2007-09-03 15:16 ` Jason Rumney
2007-09-04 0:57 ` Richard Stallman
2007-09-04 6:07 ` David Kastrup
2007-09-04 22:57 ` Richard Stallman
2007-09-04 0:57 ` Richard Stallman
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=F7525EDE-9C10-43DF-B4F3-9BF0BC5F6654@mit.edu \
--to=y@mit.edu \
--cc=emacs-devel@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.