From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: sys/cdefs.h or maybe gcc build issue
Date: Sun, 30 Oct 2016 21:33:00 -0000 [thread overview]
Message-ID: <b9a26d6c-6c17-7486-4abb-fcfbf8915c09@SystematicSw.ab.ca> (raw)
In-Reply-To: <57cbf5e2-f37b-ae50-f65c-dd6782481962@gmail.com>
On 2016-10-30 12:23, cyg Simple wrote:
> The below sample code will give a warning that visibility isn't
> supported in this configuration. Either the GCC build is incorrect or
> the sys/cdefs.h needs to be modified to define __hidden to empty.
https://cygwin.com/ml/cygwin/2005-08/msg01057.html
gcc wiki demonstrates what needs to be done instead:
https://gcc.gnu.org/wiki/Visibility#line-76
at a minimum add `&& !define(__CYGWIN__)`; other posts also exclude
MinGW and ARM-PE (W10 Surface, IoT) targets using PE format not ELF;
gcc notes not all ELF targets support this:
https://gcc.gnu.org/onlinedocs/gcc-3.3.5/gcc/Function-Attributes.html#index-_0040code_007bvisibility_007d-attribute-1624
Which raises the interesting question - anyone tried porting Cygwin
to non-x86 arch?
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
--
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:[~2016-10-30 21:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-30 18:37 cyg Simple
2016-10-30 21:33 ` Brian Inglis [this message]
2016-10-31 11:05 ` cyg Simple
2016-11-01 19:42 ` Ken Brown
2016-11-02 2:29 ` cyg Simple
2016-11-08 15:17 ` Corinna Vinschen
2016-11-09 2:09 ` cyg Simple
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=b9a26d6c-6c17-7486-4abb-fcfbf8915c09@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).