public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: cyg Simple <cygsimple@gmail.com>
To: cygwin@cygwin.com
Subject: Re: sys/cdefs.h or maybe gcc build issue
Date: Mon, 31 Oct 2016 11:05:00 -0000	[thread overview]
Message-ID: <e2ab48da-47f6-8f1d-48a0-7c1e8059836c@gmail.com> (raw)
In-Reply-To: <b9a26d6c-6c17-7486-4abb-fcfbf8915c09@SystematicSw.ab.ca>

On 10/30/2016 5:09 PM, Brian Inglis wrote:
> 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
> 

I figured that out but that means sys/cdefs.h as delivered needs to ...

> 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

consider this and define __hidden and other visibility helper macros as
empty.

> MinGW and ARM-PE (W10 Surface, IoT) targets using PE format not ELF;
> gcc notes not all ELF targets support this:
>  

If others deliver a sys/cdefs.h then it should at least declare these
helper macros as empty but that isn't for this list.

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

Maybe but I don't know.

-- 
cyg Simple

--
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:[~2016-10-31  1:01 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
2016-10-31 11:05   ` cyg Simple [this message]
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=e2ab48da-47f6-8f1d-48a0-7c1e8059836c@gmail.com \
    --to=cygsimple@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).