From: Thomas L Roche <tlroche@us.ibm.com>
Subject: [OT?] rebasing cygwin, was: cygwin/xfree86/emacs problems after upgrading
Date: Sun, 15 Feb 2004 20:04:18 -0500 [thread overview]
Message-ID: <OFC499DCE7.2B3EC893-ON85256E3C.0005C8B0-85256E3C.0005E349@us.ibm.com> (raw)
In-Reply-To: <E1Arq3I-0000UF-R6@monty-python.gnu.org>
Al Williams 13 Feb 2004 13:18:32 -0800
> I was having this problem. Rebasing the Cygwin DLLs seems to have
> cleared it up. Install rebase using setup and then exit all Cygwin
> stuff (including httpd, etc.). Then open a plain shell (not an xterm)
> and enter:
> rebaseall -v
Could you give me, or pass pointers to, a bit more information about
rebase? I'm asking because I can't find much online, except
http://sources.redhat.com/ml/cygwin-announce/2003-09/msg00039.html
> <WARNING>
> It is *strongly* recommended that users only use rebaseall unless
> they *really* know what they are doing or are instructed by one of
> the Cygwin developers.
> </WARNING>
which is pretty scary. It continues,
> The Cygwin rebase package contains two utilities, rebase and
> rebaseall. The first utility is modeled after Microsoft's SDK
> rebase:
> http://msdn.microsoft.com/library/en-us/tools/perfutil_2z39.asp
which 404s.
next parent reply other threads:[~2004-02-16 1:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Arq3I-0000UF-R6@monty-python.gnu.org>
2004-02-16 1:04 ` Thomas L Roche [this message]
[not found] <mailman.2448.1076893498.928.help-gnu-emacs@gnu.org>
2004-02-17 1:24 ` [OT?] rebasing cygwin, was: cygwin/xfree86/emacs problems after upgrading Al Williams
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=OFC499DCE7.2B3EC893-ON85256E3C.0005C8B0-85256E3C.0005E349@us.ibm.com \
--to=tlroche@us.ibm.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.
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).