From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: i686-w64-mingw32-gcc -fstack-protector-strong
Date: Fri, 08 Sep 2017 20:10:00 -0000 [thread overview]
Message-ID: <75eecba1-f968-a596-778f-77bbd8bb5c59@gmail.com> (raw)
In-Reply-To: <CAD8GWsuCBxO_8R9uBZwkGnbnJnV5-DdnvMvJ7txF0Ww6McYXoQ@mail.gmail.com>
On 08/09/2017 22:01, Lee wrote:
> On 9/8/17, Marco Atzeri wrote:
>> On 08/09/2017 20:53, Lee wrote:
>>> On 9/8/17, Marco Atzeri wrote:
>>>> On 08/09/2017 16:14, Lee wrote:
> I've still got the 'i686-w64-mingw32-gcc -fstack-protector-strong' executable:
> $ ./div.exe
> C:/cygwin/home/Lee/t/div.exe: error while loading shared libraries: ?:
> cannot open shared object file: No such file or directory
>
> $ objdump -x ./div.exe | egrep -i "dll name"
> DLL Name: KERNEL32.dll
> DLL Name: msvcrt.dll
> DLL Name: libssp-0.dll
>
> https://cygwin.com/cgi-bin2/package-grep.cgi?grep=libssp&arch=x86_64
> shows libssp0 as the GCC Stack-Smashing Protection runtime library
> but I don't see anything like that with a leading "mingw64-i686-"
> name, so I'm out of luck?
>
https://cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Fmingw64-i686-gcc-core%2Fmingw64-i686-gcc-core-6.3.0-1&grep=libssp-0.dll
almost at the end:
usr/i686-w64-mingw32/sys-root/mingw/bin/libssp-0.dll
--
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:[~2017-09-08 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 14:15 Lee
2017-09-08 15:04 ` Marco Atzeri
2017-09-08 18:53 ` Lee
2017-09-08 19:25 ` Marco Atzeri
2017-09-08 20:01 ` Lee
2017-09-08 20:10 ` Marco Atzeri [this message]
2017-09-08 21:08 ` Lee
2017-09-08 22:34 ` Yaakov Selkowitz
2017-09-08 23:10 ` Lee
2017-09-08 21:09 ` Nellis, Kenneth
2017-09-08 21:42 ` Lee
2017-09-08 23:01 ` Steven Penny
2017-09-08 23:22 ` Lee
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=75eecba1-f968-a596-778f-77bbd8bb5c59@gmail.com \
--to=marco.atzeri@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).