From: Asfand Yar Qazi <email@asfandyar.cjb.net>
To: gcc-help@gcc.gnu.org
Subject: --with-sysroot usage
Date: Mon, 08 Nov 2004 18:57:00 -0000 [thread overview]
Message-ID: <418FC290.9020707@asfandyar.cjb.net> (raw)
Hi,
Sorry if this is a bad question, but its driving me crazy.
I'm trying to get a cross-compiler for mingw32 hosted on Linux.
I downloaded the win32 libs and headers and stuff and placed them in
the directory /opt/mingw32-cross/i386-mingw32
Binutils 'i386-mingw32-as' etc go in /opt/mingw32-cross/bin, man pages
in /opt/mingw32-cross/man (prefix to all packages is /opt/mingw32-cross)
Libraries and stuff go in /opt/mingw32-cross/i386-mingw32/lib and
/opt/mingw32-cross/i386-mingw32/include and
/opt/mingw32-cross/i386-mingw32/bin, etc.
I'm fine with the rest of the stuff, but here's the question:
To the GCC configure script, which of the following do I pass:
* --with-sysroot=/opt/mingw32-cross/i386-mingw32
* --with-sysroot=/opt/mingw32-cross
* something completely different
I'm not sure about this. I went with number 1
(--with-sysroot=/opt/mingw32-cross/i386-mingw32) and discovered I had
to (cd /opt/mingw32-cross/i386-mingw32 ; mkdir usr; cd usr; ln -s
../lib .; ln -s ../include .)
There has to be a better (less 'kludgey') way to get this setup going.
It seems to work fine (apart from cross-compiled C++ programs that
use the Boost library that mysteriously crash on startup) but I want
to get the --with-sysroot flag figured out.
Before you tell me, the install docs are a bit vague, and I haven't
found any answers on the web or on the archives of this mailing list,
so I'm asking here.
Thanks,
Asfand Yar
--
http://www.it-is-truth.org/
reply other threads:[~2004-11-08 18:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=418FC290.9020707@asfandyar.cjb.net \
--to=email@asfandyar.cjb.net \
--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).