From: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: make bootstrap: need moral support. :-(
Date: Mon, 20 Feb 2006 22:32:29 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.3.96.1060220214227.253B-100000@acm.acm> (raw)
In-Reply-To: <ufymdbvnh.fsf@gnu.org>
Hi, Eli!
On Mon, 20 Feb 2006, Eli Zaretskii wrote:
>> Date: Mon, 20 Feb 2006 04:03:39 +0000 (GMT)
>> From: Alan Mackenzie <acm@muc.de>
>> cc: emacs-devel@gnu.org
>> process.c: In function `conv_sockaddr_to_lisp':
>> process.c:2245: dereferencing pointer to incomplete type
>> process.c:2246: dereferencing pointer to incomplete type
>> process.c:2249: dereferencing pointer to incomplete type
>> process.c:2249: dereferencing pointer to incomplete type
>> process.c:2249: dereferencing pointer to incomplete type
>> <etc>
>> The source code in process.c looks like this:
>> #ifdef AF_INET6
>> case AF_INET6:
>> {
>> struct sockaddr_in6 *sin6 = (struct sockaddr_in6 *) sa;
>> uint16_t *ip6 = (uint16_t *)&sin6->sin6_addr; <======= L2245
>This means that the IPv6 configury test is misbehaving. Please look
>into your headers and try to find out why the configure-time test
>decides that your system supports IPv6, but `struct sockaddr_in6' is
>not defined by your system headers.
In Linux 2.4.17, that struct is defined in the file
linux-2.4.17/include/linux/in6.h/. Emacs files.c don't #include this
file at all. I'll have a look at ./configure, sometime.
[ .... ]
>> I worked around this problem by putting #undef AF_INET6 near the top
>> of the file.
>> Emacs then built immediately!
>Well, that's good for you, but what about all the other users who will
>have the same problem? I'd suggest not to sweep the problem under the
>carpet, but rather try to find out what is wrong with the
>configure-time test, so that it could be fixed for others as well.
OK. It's just that I didn't have enough confidence in my ability to
build Emacs to assume that this problem was a bug (as contrasted to me
not giving some parameter to ./configure, or something).
>> However, when I started it up, it complained about this form in my
>> site-start.el:
>> (define-key help-mode-map "\M-n" 'clone-buffer)
>> I had to wrap this form in an (eval-after-load "help-mode" ....). Is
>> this failure to load help-mode at start-up deliberate, or is it a bug?
>I think it's deliberate: why should we load help-mode before Help
>commands are used?
:-) It has historically always been so loaded. Who gets through an
Emacs session without C-h? But then, loading it early is not that
important.
>Btw, your workaround is not the best way to solve this, I think: each
>mode has a mode hook, precisely for these situations. Just define a
>function that binds that key and add that function to help-mode-hook.
The key sequence needs binding only once. Won't help-mode-hook be called
every time a help command is invoked?
--
Alan.
next prev parent reply other threads:[~2006-02-20 22:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-19 15:07 make bootstrap: need moral support. :-( Alan Mackenzie
2006-02-19 21:27 ` Giorgos Keramidas
2006-02-20 2:31 ` Robert J. Chassell
2006-02-20 4:09 ` Miles Bader
2006-02-20 15:24 ` Randal L. Schwartz
2006-02-20 20:47 ` Michael Price
2006-02-20 20:57 ` Giorgos Keramidas
2006-02-20 22:33 ` Giorgos Keramidas
2006-02-20 4:58 ` Eli Zaretskii
2006-02-20 4:03 ` Alan Mackenzie
2006-02-20 20:52 ` Eli Zaretskii
2006-02-20 22:32 ` Alan Mackenzie [this message]
2006-02-21 4:34 ` Eli Zaretskii
2006-02-21 9:06 ` Jan D.
2006-02-21 9:44 ` Kim F. Storm
2006-02-20 16:21 ` Eric Hanchrow
2006-02-20 21:38 ` Giorgos Keramidas
2006-02-21 5:18 ` Ken Raeburn
2006-02-21 8:52 ` Giorgos Keramidas
2006-02-21 9:22 ` Ken Raeburn
2006-02-20 18:42 ` Richard M. Stallman
2006-02-20 22:37 ` Alan Mackenzie
2006-02-21 20:22 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2006-02-22 10:30 Francesco Potorti`
2006-02-22 10:54 ` Giorgos Keramidas
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=Pine.LNX.3.96.1060220214227.253B-100000@acm.acm \
--to=acm@muc.de \
--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 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).