From: Warren Young <wyml@etr-usa.com>
To: cygwin@cygwin.com, Rainer.Woitok@Gmail.Com
Subject: Re: How to correctly rebase?
Date: Thu, 15 Oct 2015 20:54:00 -0000 [thread overview]
Message-ID: <41C9E795-AEEC-4378-8548-44DAF7DB98E7@etr-usa.com> (raw)
In-Reply-To: <22047.42793.36600.773496@woitok.gmail.com>
On Oct 15, 2015, at 7:16 AM, Dr Rainer Woitok <rainer.woitok@gmail.com> wrote:
>
> /usr/share/texmf-dist/tex/plain/gustlib/licz/licz-tst.mex: skipped because not rebaseable
I think these are a harmless confusion of mex-the-Metafont-format with mex-the-Octave-plugin-format.
You can ignore them.
It would be nice if rebase were smart enough to look for *.mex and *.oct only in known Octave directories, but it isn’t my itch, so I’m not going to be doing anything about it.
> The following DLLs couldn't be rebased due to errors:
> /usr/bin/cygintl-8.dll
> /usr/bin/cygiconv-2.dll
I got similar errors in my testing, though with different libraries. I reinstalled those library packages and the errors went away.
The only complaints I still see are about a 32-bit libstdc++ for cross-compiling on this 64-bit system, which is harmless.
> QUESTION: I called "rebaselst" with the "--cleardb" option which should
> cause it to pass "-b 0x70000000" to "rebase" (this is an "i386" system).
> Why then are we starting above at a base of 0x32b40000?
Because BLODA? I don’t see that you’ve reported going through the BLODA list and ruling out all the possibilities there:
https://cygwin.com/faq/faq.html#faq.using.bloda
As for the 32-bit issue, that may be part of the problem. 64-bit greatly reduces the problems that rebase tries to cure, simply because it’s much harder to have a collision in such a large address space.
> PS: And since I'm still not on this list because I can't really handle
> the traffic, please also reply to me personally. Thanks.
Your inability to filter 50 messages a day to a junk folder or use Gmane does not constitute a requirement that we send email directly to you.
Gmail even has a feature for this, sending mailing list traffic off to the Forums tab by default, so you don’t even have to go see it if you don’t want to.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2015-10-15 20:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 14:26 Dr Rainer Woitok
2015-10-14 17:27 ` Warren Young
2015-10-14 19:27 ` Achim Gratz
2015-10-14 21:30 ` Warren Young
2015-10-14 22:08 ` Warren Young
2015-10-14 22:37 ` Warren Young
2015-10-15 7:53 ` Achim Gratz
2015-10-15 7:15 ` Achim Gratz
2015-10-15 13:16 ` Dr Rainer Woitok
2015-10-15 20:54 ` Warren Young [this message]
2015-10-15 21:10 ` Ken Brown
2015-10-16 12:57 ` Dr Rainer Woitok
2015-10-16 12:58 ` Ken Brown
2015-10-16 15:08 ` Ken Brown
2015-10-16 15:16 ` cyg Simple
2015-10-16 15:29 ` Ken Brown
2015-10-16 15:50 ` Andrey Repin
2015-10-18 11:15 ` Dr Rainer Woitok
2015-10-18 11:59 ` Achim Gratz
2015-10-18 12:45 ` Ken Brown
2015-10-18 16:20 ` Dr Rainer Woitok
2015-10-19 23:59 ` Warren Young
2015-10-20 16:55 ` Dr Rainer Woitok
2015-10-16 7:21 ` Achim Gratz
2015-10-16 20:11 ` Warren Young
2015-12-18 16:28 ` Achim Gratz
2015-10-14 19:58 ` Achim Gratz
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41C9E795-AEEC-4378-8548-44DAF7DB98E7@etr-usa.com \
--to=wyml@etr-usa.com \
--cc=Rainer.Woitok@Gmail.Com \
--cc=cygwin@cygwin.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).