From: Dhruva Krishnamurthy <dhruva.krishnamurthy@gmail.com>
Subject: Build issues in emacs-unicode-2
Date: Fri, 15 Oct 2004 12:33:55 +0530 [thread overview]
Message-ID: <68c73b1a041015000353a5da59@mail.gmail.com> (raw)
Hello,
This is more a question as I am facing a problem building "leim"
under emacs-unicode-2 branch.
I have both the HEAD and emacs-unicode-2 branch. I am able to build
from HEAD with no issues. When the "leim" build fails in
emacs-unicode-2 branch, I just copied the "leim" folder from the
emacs-unicode-2 to HEAD. Built it in HEAD and copied back the built
"leim" back to emacs-unicode-2. I completed the build in
emacs-unicode-2 with the above approach.
My question: Is it important for "leim" where it is built (using Emacs
from HEAD or using Emacs from emacs-unicode-2)? This might sound a
lousy question but I prefer to ask than just keep quiet.
with best regards,
dhruva
--
Proud FSF member: #1935
http://schemer.fateback.com/
reply other threads:[~2004-10-15 7:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=68c73b1a041015000353a5da59@mail.gmail.com \
--to=dhruva.krishnamurthy@gmail.com \
/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).