From: Lee <ler762@gmail.com>
To: cygwin@cygwin.com
Subject: gcc -fsanitize => cannot find -lubsan
Date: Tue, 27 Mar 2018 18:48:00 -0000 [thread overview]
Message-ID: <CAD8GWssb0Ka-GmULAtb=dLnNFt=ssbT-Cc1viNTWMC7_E=bfzw@mail.gmail.com> (raw)
How do you figure out which package is missing from your install?
$cat sbstrict.c
int main () {
return 0;
}
$i686-w64-mingw32-gcc -fsanitize=bounds-strict sbstrict.c
/usr/lib/gcc/i686-w64-mingw32/6.4.0/../../../../i686-w64-mingw32/bin/ld:
cannot find -lubsan
collect2: error: ld returned 1 exit status
$gcc -fsanitize=bounds-strict sbstrict.c
/usr/lib/gcc/x86_64-pc-cygwin/6.4.0/../../../../x86_64-pc-cygwin/bin/ld:
cannot find -lubsan
collect2: error: ld returned 1 exit status
I looked at
https://cygwin.com/cgi-bin2/package-grep.cgi?grep=ubsan&arch=x86_64
and both
gcc-debuginfo-6.4.0-5
mingw64-i686-gcc-debuginfo-6.4.0-1
have a ubsan.c, but ld wouldn't be looking for that. Right??
Thanks
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
next reply other threads:[~2018-03-27 17:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-27 18:48 Lee [this message]
2018-03-27 19:15 ` Brian Inglis
2018-03-28 3:13 ` 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='CAD8GWssb0Ka-GmULAtb=dLnNFt=ssbT-Cc1viNTWMC7_E=bfzw@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).