From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: perl-5.14.4
Date: Sun, 08 Feb 2015 20:19:00 -0000 [thread overview]
Message-ID: <87386gtaub.fsf@Rainer.invalid> (raw)
In-Reply-To: <87bnl6n8uw.fsf@Rainer.invalid> (Achim Gratz's message of "Fri, 06 Feb 2015 20:22:15 +0100")
Achim Gratz writes:
> Major progress: the cygport file starts to look sane. I've ripped out
> the rebase changes in EU::MM and replaced them with an oblivious rebase,
> which is the first time I could compile and test on 32bit without manual
> intervention.
It turns out that doing so damages the debug information in the library
and then it can't be extracted later, so I'll have to skip this step
when building with cygport. I have no idea how and why this happens;
the debug information is still there, but quite obviously it can't be
correctly associated with the code after rebasing. Is that something
that can be fixed in rebase or objcopy?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
next prev parent reply other threads:[~2015-02-08 20:19 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 20:41 perl-5.14.4 Achim Gratz
2015-02-04 21:57 ` perl-5.14.4 David Stacey
2015-02-04 22:10 ` perl-5.14.4 Achim Gratz
2015-02-05 17:57 ` perl-5.14.4 Reini Urban
2015-02-05 19:16 ` perl-5.14.4 Achim Gratz
2015-02-05 8:49 ` perl-5.14.4 Corinna Vinschen
2015-02-05 16:13 ` perl-5.14.4 Achim Gratz
2015-02-05 17:53 ` perl-5.14.4 Reini Urban
2015-02-05 19:13 ` perl-5.14.4 Achim Gratz
2015-02-06 19:22 ` perl-5.14.4 Achim Gratz
2015-02-08 20:19 ` Achim Gratz [this message]
2015-02-09 10:25 ` perl-5.14.4 Corinna Vinschen
2015-02-09 17:16 ` perl-5.14.4 Achim Gratz
2015-02-09 18:49 ` perl-5.14.4 Corinna Vinschen
2015-02-09 19:06 ` perl-5.14.4 Corinna Vinschen
2015-02-09 19:41 ` perl-5.14.4 Achim Gratz
2015-02-09 20:20 ` perl-5.14.4 Corinna Vinschen
2015-02-14 20:04 ` perl-5.14.4 Achim Gratz
2015-02-14 21:12 ` perl-5.14.4 Achim Gratz
2015-02-15 10:32 ` perl-5.14.4 Corinna Vinschen
2015-02-15 13:18 ` perl-5.14.4 Achim Gratz
2015-02-15 14:31 ` perl-5.14.4 Corinna Vinschen
2015-02-15 16:22 ` perl-5.14.4 Achim Gratz
2015-02-15 19:14 ` perl-5.14.4 Achim Gratz
2015-02-16 9:17 ` perl-5.14.4 Corinna Vinschen
2015-02-16 9:46 ` perl-5.14.4 Achim Gratz
2015-02-16 10:25 ` perl-5.14.4 Corinna Vinschen
2015-02-16 12:25 ` perl-5.14.4 Corinna Vinschen
2015-02-16 14:29 ` perl-5.14.4 Achim Gratz
2015-02-16 15:32 ` perl-5.14.4 Corinna Vinschen
2015-02-16 15:42 ` perl-5.14.4 Achim Gratz
2015-03-05 13:21 ` perl-5.14.4 Corinna Vinschen
2015-03-05 16:45 ` perl-5.14.4 Achim Gratz
2015-03-10 9:10 ` perl-5.14.4 Corinna Vinschen
2015-03-14 20:30 ` perl-5.14.4 Achim Gratz
2015-03-16 9:06 ` perl-5.14.4 Corinna Vinschen
2015-02-10 19:55 ` perl-5.14.4 Achim Gratz
2015-02-11 20:01 ` perl-5.14.4 David Stacey
2015-02-13 18:36 ` perl-5.14.4 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=87386gtaub.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@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).