From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Building libsigsegv on Cygwin64
Date: Sat, 22 Feb 2014 15:33:00 -0000 [thread overview]
Message-ID: <53089698.9070103@cornell.edu> (raw)
In-Reply-To: <20140221154627.GC2246@calimero.vinschen.de>
On 2/21/2014 10:46 AM, Corinna Vinschen wrote:
> On Feb 21 16:32, Angelo Graziosi wrote:
>> Trying to build libsigsegv-2.10 on Cygwin64 (using the src tarball
>> and its .cygport file from x86 distribution), fails as follows
>>
>> [...]
>> libtool: compile: gcc -DHAVE_CONFIG_H -I.
>> -I/works/tmp/libsigsegv-2.10-1/src/libsigsegv-2.10/src -I.. -I.
>> -I/works/tmp/libsigsegv-2.10-1/src/libsigsegv-2.10/src -ggdb -O2
>> -pipe -Wimplicit-function-declaration -fdebug-prefix-map=/works/tmp/libsigsegv-2.10-1/build=/usr/src/debug/libsigsegv-2.10-1 -fdebug-prefix-map=/works/tmp/libsigsegv-2.10-1/src/libsigsegv-2.10=/usr/src/debug/libsigsegv-2.10-1
>> -c /works/tmp/libsigsegv-2.10-1/src/libsigsegv-2.10/src/handler.c
>> -DDLL_EXPORT -DPIC -o .libs/handler.o
>> In file included from
>> /works/tmp/libsigsegv-2.10-1/src/libsigsegv-2.10/src/handler.c:20:0:
>> /works/tmp/libsigsegv-2.10-1/src/libsigsegv-2.10/src/handler-win32.c:
>> In function 'main_exception_filter':
>> /works/tmp/libsigsegv-2.10-1/src/libsigsegv-2.10/src/handler-win32.c:218:43:
>> error: 'struct _CONTEXT' has no member named 'Esp'
>> ExceptionInfo->ContextRecord->Esp = new_safe_esp;
>> ^
>> /works/tmp/libsigsegv-2.10-1/src/libsigsegv-2.10/src/handler-win32.c:220:43:
>> error: 'struct _CONTEXT' has no member named 'Eip'
>> ExceptionInfo->ContextRecord->Eip = (unsigned
>> long)&stack_overflow_handler;
>> ^
>> Makefile:399: set di istruzioni per l'obiettivo "handler.lo" non riuscito
>> make[1]: *** [handler.lo] Errore 1
>> make[1]: uscita dalla directory "/works/tmp/libsigsegv-2.10-1/build/src"
>> Makefile:344: set di istruzioni per l'obiettivo "install-recursive"
>> non riuscito
>> make: *** [install-recursive] Errore 1
>>
>> Since my Cygwin64 is a fesh installation, I wonder if I missed to
>> installe some needed packages... or is that error to be expected on
>> Cygwin64?
>
> Yes. The above code appears not to know 64 bit CPUs. The 64 bit
> instruction pointer register is called Rip, rather than Eip, for
> instance.
I just took a glance at the libsigsegv source code, and it supports
several x86_64 platforms. It should be possible to add support for
x86_64-cygwin. Reini, any chance you could look into this?
Ken
--
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:[~2014-02-22 12:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 15:46 Angelo Graziosi
2014-02-21 16:11 ` Corinna Vinschen
2014-02-22 15:33 ` Ken Brown [this message]
2014-03-02 17:21 ` Ken Brown
2014-03-02 18:33 ` Ken Brown
2014-03-03 15:02 ` Corinna Vinschen
2014-03-03 15:15 ` Kai Tietz
2014-03-03 15:45 ` Corinna Vinschen
2014-03-03 17:24 ` Corinna Vinschen
2014-03-03 20:05 ` Ken Brown
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=53089698.9070103@cornell.edu \
--to=kbrown@cornell.edu \
--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).