From: Andrew Pennebaker <andrew.pennebaker@gmail.com>
To: Cygwin <cygwin@cygwin.com>
Subject: MinGW's GCC and __attribute__((weak))
Date: Thu, 13 Sep 2012 00:03:00 -0000 [thread overview]
Message-ID: <CAHXt_SVJTPFfEkW1zJcWiY84PhTNfbVRCxZKyfb+sziRYs=u8g@mail.gmail.com> (raw)
Am I correct in assuming that gcc/MinGW builds on top of Cygwin?
Because I'm having trouble getting gcc to recognize
__attribute__((weak)) in Windows, where the exact same C source code
compile just fine with gcc in an ordinary Unix (Mac OS X as it
happens) environment.
I love how you can bundle a framework and CLI in the same Perl script,
by using unless(caller) { main; }. For lack of a better name, I've
started calling this behavior scriptedmain. Here's a Perl script
example (https://github.com/mcandre/scriptedmain/tree/master/perl).
I want to be able to do the same thing in C, and with help from
StackOverflow I've gotten working C code to do just that, in Unix.
Unfortunately, the C code
(http://stackoverflow.com/questions/12395130/trouble-using-scriptedmain-in-mingw)
doesn't compile in Windows, because gcc/MinGW and gcc/Strawberry Perl
fail to recognize __attribute__((weak)) syntax. Is there another way I
can rewrite my code for MinGW's gcc so that it compiles and works like
the Perl scriptedmain? Or can we add __attribute__((weak)) to MinGW's
gcc lexicon?
I will also be asking the Strawberry Perl project about their gcc in
case some minor configuration tweak can get this working.
Cheers,
Andrew Pennebaker
www.yellosoft.us
--
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:[~2012-09-12 21:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 0:03 Andrew Pennebaker [this message]
2012-09-13 3:41 ` Andrew Pennebaker
2012-09-13 6:29 ` Christopher Faylor
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='CAHXt_SVJTPFfEkW1zJcWiY84PhTNfbVRCxZKyfb+sziRYs=u8g@mail.gmail.com' \
--to=andrew.pennebaker@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).