From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Broken MPIR 2.6.0 on Cygwin64
Date: Mon, 24 Jun 2013 11:03:00 -0000 [thread overview]
Message-ID: <20130624092232.GG14319@calimero.vinschen.de> (raw)
In-Reply-To: <kq1kib$9gt$1@ger.gmane.org>
On Jun 21 13:30, Jean-Pierre Flori wrote:
> Le Fri, 21 Jun 2013 11:43:44 +0200, Corinna Vinschen a écrit :
>
> > On Jun 21 09:27, Jean-Pierre Flori wrote:
> >> Hey,
> >>
> >> Thanks for the quick reply.
> >>
> >> Le Fri, 21 Jun 2013 10:30:39 +0200, Corinna Vinschen a écrit :
> >>
> >> >> /bin/sh ../libtool --tag=CC --mode=link gcc -std=gnu99 -m64 -O2
> >> >> -march=corei7-avx -mtune=corei7-avx -o t-bswap.exe t-bswap.o
> >>
> > The easiest way to do that is to fetch the binutils-2.23.52-5 source
> > package from a Cygwin mirror and to use cygport for building. Just
> > tweak the cygport file to set MAKEOPTS to 'CFLAGS=-g'.
> >
> I did it using configure/make/make install directly.
> Here is the backtrace I got (when trying to build a static library, first
> of the unsolved problems I reported):
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x000000000000003e in ?? ()
> (gdb) bt
> #0 0x000000000000003e in ?? ()
> #1 0x0000000100499ece in coff_link_check_ar_symbols (abfd=0x60013d1c0,
> info=0x10058a720 <link_info>, pneeded=0xc2a6fc, subsbfd=0xc2a6d0)
> at cofflink.c:217
> #2 0x000000010049a08f in coff_link_check_archive_element
> (abfd=0x60013d1c0,
> info=0x10058a720 <link_info>, pneeded=0xc2a6fc) at cofflink.c:279
Unfortunately this doesn't tell as why it crashes. Is that with the
wrong assembler files? Does it work when using the correct assembler
files?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
--
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
prev parent reply other threads:[~2013-06-24 9:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 22:56 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
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 [this message]
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=20130624092232.GG14319@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).