From: Ken Brown <kbrown@cornell.edu>
To: Glenn Morris <rgm@gnu.org>
Cc: "7127@debbugs.gnu.org" <7127@debbugs.gnu.org>
Subject: bug#7127: 23.2; M-x help throws an error
Date: Wed, 29 Sep 2010 14:58:57 -0400 [thread overview]
Message-ID: <4CA38C71.3040906@cornell.edu> (raw)
In-Reply-To: <n6k4m432cf.fsf@fencepost.gnu.org>
On 9/29/2010 1:07 PM, Glenn Morris wrote:
> Ken Brown wrote:
>
>> This turns out not to be so easy. That patch is intertwined with a
>> lot of changes to the build system that were made only in the trunk,
>> so there's no way to quickly test whether that patch is relevant to
>> the present bug.
>
> Would this have the same effect?
>
> *** src/s/cygwin.h 2010-01-13 08:35:10 +0000
> --- src/s/cygwin.h 2010-09-29 17:04:58 +0000
> ***************
> *** 104,109 ****
> --- 104,110 ----
> #define PENDING_OUTPUT_COUNT(FILE) ((FILE)->_p - (FILE)->_bf._base)
> #define SYSV_SYSTEM_DIR 1
> #define UNEXEC unexcw.o
> + #define START_FILES pre-crt0.o
> #define POSIX_SIGNALS 1
> #define LINKER $(CC)
That's the first thing I tried, but emacs wouldn't compile because of an
undefined reference in src/sysdep.c. So I patched that. Then emacs
wouldn't compile because of an undefined reference in src/vm-limit.c.
That's when I decided that it might not be worth the trouble to put more
time into this. I'd also be a little worried about what side-effects
might result from selectively backporting changes to the build system.
Ken
next prev parent reply other threads:[~2010-09-29 18:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 23:03 bug#7127: 23.2; M-x help throws an error Aidan Kehoe
2010-09-28 23:27 ` Glenn Morris
2010-09-29 7:17 ` Aidan Kehoe
2010-09-29 7:58 ` Glenn Morris
2010-09-29 13:02 ` Ken Brown
2010-09-29 17:00 ` Ken Brown
2010-09-29 17:07 ` Glenn Morris
2010-09-29 18:58 ` Ken Brown [this message]
2010-09-30 0:35 ` Glenn Morris
2010-09-30 2:15 ` Ken Brown
2010-09-30 7:12 ` Glenn Morris
2010-09-30 17:30 ` Ken Brown
2010-10-01 14:00 ` Ken Brown
2010-10-01 18:33 ` Glenn Morris
2010-10-02 1:55 ` Ken Brown
2010-10-02 2:57 ` Glenn Morris
2010-10-02 13:57 ` Ken Brown
2010-10-02 15:12 ` Eli Zaretskii
2010-10-02 15:47 ` Ken Brown
2010-10-08 15:14 ` Ken Brown
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4CA38C71.3040906@cornell.edu \
--to=kbrown@cornell.edu \
--cc=7127@debbugs.gnu.org \
--cc=rgm@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).