public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: Re: i686-w64-mingw32-gcc -fstack-protector-strong
Date: Fri, 08 Sep 2017 23:10:00 -0000	[thread overview]
Message-ID: <CAD8GWstmF5=0yOYzcPLqK3OOmHeYebq=fM4J9yR8__roR=H_GA@mail.gmail.com> (raw)
In-Reply-To: <4a702e1e-5ce1-175f-ca52-088dd21ef905@cygwin.com>

On 9/8/17, Yaakov Selkowitz <yselkowitz@cygwin.com> wrote:
> On 2017-09-08 16:08, Lee wrote:
>> $ i686-w64-mingw32-gcc --version
>> i686-w64-mingw32-gcc (GCC) 6.3.0
>> Copyright (C) 2016 Free Software Foundation, Inc.
>> This is free software; see the source for copying conditions.  There is
>> NO
>> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
>> PURPOSE.
>>
>> $ i686-w64-mingw32-gcc -fstack-protector-strong -o div.exe div.c
>> $ ./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
>> $ ls -l /usr/i686-w64-mingw32/sys-root/mingw/bin/libssp-0.dll
>> -rwxr-xr-x 1 root None 14336 Aug 17 08:26
>> /usr/i686-w64-mingw32/sys-root/mingw/bin/libssp-0.dll
>
> You created a MinGW executable which depends on other MinGW DLLs.
> Therefore, either you have to tell it where to find its dependencies:
>
> PATH="$(cygpath -S):$(cygpath
> -W):/usr/i686-w64-mingw32/sys-root/mingw/bin:$PATH" \
> ./div.exe
>
> Or, since you're only using GCC's libraries, just link with -static.

That was it.  Thank you!!

$ i686-w64-mingw32-gcc -static -fstack-protector-strong -o div.exe div.c
$ ./div
  works
$ i686-w64-mingw32-gcc -fstack-protector-strong -o div.exe div.c
$ PATH=/usr/i686-w64-mingw32/sys-root/mingw/bin:$PATH  ./div.exe
  works

and follow up question if I may - what should I have read that would
have told me that?

Lee

--
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

  reply	other threads:[~2017-09-08 23: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
2017-09-08 21:08           ` Lee
2017-09-08 22:34             ` Yaakov Selkowitz
2017-09-08 23:10               ` Lee [this message]
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='CAD8GWstmF5=0yOYzcPLqK3OOmHeYebq=fM4J9yR8__roR=H_GA@mail.gmail.com' \
    --to=ler762@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).