From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Joel Brobecker <brobecker@adacore.com>,
Dmitry Smirnov <divis1969@mail.ru>
Subject: Re: Build GDB 7.0 with Cygwin -mno-cygwin option.
Date: Wed, 07 Oct 2009 17:14:00 -0000 [thread overview]
Message-ID: <200910071814.01611.pedro@codesourcery.com> (raw)
In-Reply-To: <20091007165818.GG16338@adacore.com>
On Wednesday 07 October 2009 17:58:18, Joel Brobecker wrote:
> We build GDB under the same conditions all the time without any problem.
> But our compiler is based on GCC 4.3.3, so you might want to try upgrading
> your compiler. Just a guess.
Joel tells me on IRC that he condition he refers to,
is the --build=... bit, not the use of -mno-cygwin.
On Wednesday 07 October 2009 17:30:02, Dmitry Smirnov wrote:
> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/winsock2.h:101: err
> or: redefinition of `struct timeval'
> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/winsock2.h:611: err
> or: conflicting types for 'select'
> /usr/include/sys/select.h:31: error: previous declaration of 'select' was here
> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/winsock2.h:611: err
> or: conflicting types for 'select'
> /usr/include/sys/select.h:31: error: previous declaration of 'select' was here
> /usr/lib/gcc/i686-pc-cygwin/3.4.4/../../../../include/w32api/winsock2.h:614: err
> or: conflicting types for 'gethostname'
Cygwin's gcc is pulling Cygwin headers, while the build is assuming a mingw host.
Things are expected to break this way. I would assume at least you'd need
--host,build=i686-pc-mingw32 _and_ CC="gcc -mno-cygwin". A real mingw gcc
would be better.
--
Pedro Alves
next prev parent reply other threads:[~2009-10-07 17:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-07 16:30 Dmitry Smirnov
2009-10-07 16:58 ` Joel Brobecker
2009-10-07 17:12 ` Joel Brobecker
2009-10-07 17:14 ` Pedro Alves [this message]
2009-10-08 11:01 ` Re[2]: " Dmitry Smirnov
2009-10-08 21:33 ` 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=200910071814.01611.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=divis1969@mail.ru \
--cc=gdb@sourceware.org \
/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