public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kenton Varda <temporal@gauge3d.org>
To: cygwin@cygwin.com
Subject: -mno-cygwin and C++
Date: Tue, 27 Mar 2001 19:22:00 -0000	[thread overview]
Message-ID: <01032721225103.27978@sabin> (raw)

I just updated my copy of cygwin today, and it appears that using -mno-cygwin 
no longer works with C++.  When I try to include STL headers, I get "file not 
found" errors.  I tried adding -I/usr/include/g++-3 to the command line, but 
that just led to linker errors related to __errno and other symbols, 
presumably because it tried to link against cygwin's libstdc++.a rather than 
mingw's.

Next, I tried installing gcc-2.95.2-mingw-extra.tar.gz as I had to with my 
old copy of cygwin.  With this, my only error was "undefined reference to 
_imp___HUGE_dll".  I looked for a new version of this package for gcc-2.95.3, 
but found none...

So, what is the latest hack required to make C++ work with -mno-cygwin?  
Perhaps, in a future version, this will work without special hacks? :/

Thanks...

-Kenton Varda

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2001-03-27 19:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 19:22 Kenton Varda [this message]
2001-03-27 19:54 ` Christopher Faylor
2001-03-27 20:49   ` Danny Smith
2001-03-29 12:07     ` mingw-extra-2.95.3 [Was: Re: -mno-cygwin and C++] Danny Smith
2001-03-31 19:10       ` Christopher Faylor
2001-03-27 21:48   ` -mno-cygwin and C++ -- solved! Kenton Varda
2001-03-27 22:13     ` Christopher Faylor
2001-03-28 18:32     ` Paul Garceau
2001-03-29 11:54       ` Christopher Faylor
2001-03-29 19:33         ` Paul Garceau
2001-03-29 20:18         ` Mumit Khan
2001-03-29 20:46           ` Christopher Faylor
2001-03-29 20:57             ` Robert Collins
2001-03-29 21:13               ` Christopher Faylor
2001-03-29 23:00             ` Mumit Khan

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=01032721225103.27978@sabin \
    --to=temporal@gauge3d.org \
    --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).