Re: failed to built xemacs port on FreeBSD
"Stephen J. Turnbull" <[email protected]> Fri, 6 May 2016 17:53:54 +0900
| Newsgroups | gmane.emacs.xemacs.beta |
|---|---|
| Message-ID | <[email protected]> |
KIRIYAMA Kazuhiko writes: > I dont know why, but anyway src/xemacs binary wants any > *.elc in mule-base package. I think you're going to have to learn more about the changes made to your port relative to our code. I can't reproduce with the code straight from our repository, so it seems likely that some patch in the FreeBSD port is responsible. > Without -no-autoloads option, passed building lisp stage in > lisp directory: That's probably because it can find the package mule files in the packages. But that means that users trying to build the port have to install the packages first, which should not be necessary. And if they happen to have .elcs that were built with 21.5 in their packages, that build command will fail because the bytecode has changed and so compiled Lisp is protected with a version check. > > Try "strings ./xemacs | grep kana-keyboard". If it doesn't show up > > there, I'm not sure offhand what to say. > > I refer in lisp/*.el and lisp/*.elc, the results as follows: That's not what I asked for. I know what is in lisp/ from the URL you posted earlier, and I've already confirmed that it's what I expected. So the problem is elsewhere. What I can't do without a lot of unnecessary effort is build XEmacs 21.4 on your platform. You have already done that to the point necessary, so please help me investigate your XEmacs. Please execute "strings ./xemacs | grep kana-keyboard" and tell me whether there is any output, and if so, what it is. While I'm thinking about it, I'd also like to know the output of "strings ./xemacs | grep /mule", and if there is none, also the output of "strings ./xemacs | grep mule" (same as before, but no slash before "mule"). If you get a complaint that "xemacs" is not found, use "temacs" instead. Steve