From: "Dhruva Krishnamurthy" <seagull@fastmail.fm>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Emacs 21.2.93 - NFS issue
Date: Wed, 11 Dec 2002 17:20:01 +0530 [thread overview]
Message-ID: <20021211115001.6A0C935AE0@server2.fastmail.fm> (raw)
In-Reply-To: <4871353.1039606136633.JavaMail.root@127.0.0.1>
On Wed, 11 Dec 2002 11:28:56 +0000 (GMT), jasonr@btinternet.com said:
> > I was looking in to the "etc/PROBLEMS" file and I am refering to the
> > following problem.
> > * Building Emacs over NFS fails with ``Text file busy''.
> [snip]
> > Maybe we could modify the "etc/PROBLEMS" file to reflect this result.
>
> I don't see anything that needs changing. The PROBLEMS entry already
> starts with "This was reported to happen when building Emacs on a
> GNU/Linux system (RedHat Linux 6.2) using a build directory
> automounted from Solaris (SunOS 5.6) file server, but it might not
> be limited to that configuration alone."
>
>
>
Sorry about the wrong info: I was looking at this from "etc/PROBLEM":
* Emacs binary is not in executable format, and cannot be run.
This was reported to happen when Emacs is built in a directory mounted
via NFS. Usually, the file `emacs' produced in these cases is full of
binary null characters, and the `file' utility says:
emacs: ASCII text, with no line terminators
We don't know what exactly causes this failure. A work-around is to
build Emacs in a directory on a local disk.
with regards,
dhruva
--
Dhruva Krishnamurthy
Home: http://www.geocities.com/gnued/
next prev parent reply other threads:[~2002-12-11 11:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 11:28 Emacs 21.2.93 - NFS issue jasonr
2002-12-11 11:50 ` Dhruva Krishnamurthy [this message]
2002-12-12 17:08 ` Richard Stallman
2002-12-13 4:23 ` Dhruva Krishnamurthy
2002-12-13 15:45 ` Stefan Monnier
2002-12-14 18:32 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2002-12-11 10:38 Dhruva Krishnamurthy
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=20021211115001.6A0C935AE0@server2.fastmail.fm \
--to=seagull@fastmail.fm \
--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).