From: Jean-Pierre Flori <jpflori@gmail.com>
To: cygwin@cygwin.com
Subject: Re: libtool weirdness (was Re: Broken MPIR 2.6.0 on Cygwin64)
Date: Fri, 21 Jun 2013 17:27:00 -0000 [thread overview]
Message-ID: <kq215r$t2h$2@ger.gmane.org> (raw)
In-Reply-To: <kq20jn$t2h$1@ger.gmane.org>
Le Fri, 21 Jun 2013 16:56:23 +0000, Jean-Pierre Flori a écrit :
> And the bad news is: tests still segfault.
>
> I'll also check with the static library now.
>
With the same changes but trying a static lib I get to the same point as
for the shared one:
* ld doesn't segfault anymore, so tests executables are built,
* but the same tests as in the shared library setting segfault.
> I'll also check without assembly optimizations, or lowering gcc
> optimization level, etc.
So I'm going to try that now.
--
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:[~2013-06-21 17:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 22:56 Broken MPIR 2.6.0 on Cygwin64 Jean-Pierre Flori
2013-06-21 8:33 ` Corinna Vinschen
2013-06-21 9:30 ` Corinna Vinschen
2013-06-21 9:43 ` Jean-Pierre Flori
2013-06-21 10:57 ` Corinna Vinschen
2013-06-21 11:35 ` libtool weirdness (was Re: Broken MPIR 2.6.0 on Cygwin64) Corinna Vinschen
2013-06-21 17:00 ` Jean-Pierre Flori
2013-06-21 17:27 ` Jean-Pierre Flori [this message]
2013-06-21 17:35 ` Jean-Pierre Flori
2013-06-21 18:10 ` Jean-Pierre Flori
2013-06-21 22:44 ` Jean-Pierre Flori
2013-06-21 22:48 ` Jean-Pierre Flori
2013-06-24 9:20 ` Corinna Vinschen
2013-06-24 9:19 ` Corinna Vinschen
2013-06-21 18:05 ` Yaakov (Cygwin/X)
2013-06-24 9:22 ` Corinna Vinschen
2013-06-24 11:55 ` Corinna Vinschen
2013-06-24 16:21 ` Yaakov (Cygwin/X)
2013-06-21 13:39 ` Broken MPIR 2.6.0 on Cygwin64 Jean-Pierre Flori
2013-06-24 11:03 ` Corinna Vinschen
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='kq215r$t2h$2@ger.gmane.org' \
--to=jpflori@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).