public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Claes Lilliesköld <clli@enea.se>
To: GCC Help <gcc-help@gcc.gnu.org>
Subject: which include-files for mingw32 (cross-built)
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <38A986BC.9FECCF00@enea.se> (raw)
Message-ID: <20000401000000.cq0eH_nYYAqVS9pMUPKdmUeTnLHKAg6KCoAsBP0Ez7A@z> (raw)

Hello
Where do I find the include files needed to build a mingw32 cross
compiler (GCC 2.95.2)
when building on solaris 2.6 machine. Should they be the include files
of
my target? In that case, I can perhaps use include files from a native
windows
compiler (no name).
I though of specifying the include directory with --with-headers.

thanks / Claes

             reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-15  9:00 Claes Lilliesköld [this message]
2000-04-01  0:00 ` Claes Lilliesköld

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=38A986BC.9FECCF00@enea.se \
    --to=clli@enea.se \
    --cc=gcc-help@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).