public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* [RAW_]_CXX_FOR_TARGET?
@ 2003-06-30  8:01 Mohan Embar
  0 siblings, 0 replies; only message in thread
From: Mohan Embar @ 2003-06-30  8:01 UTC (permalink / raw)
  To: gcc-help; +Cc: libstdc++, java

Hi People,

Sorry for the cross-posts, but I don't know who I should ask
about this.

I am doing a the following crossed-native build of gcc/gcj 3.4:

(build,host,target) = (i686-pc-linux-gnu,i686-pc-mingw32,i686-pc-mingw32)

Based on this configuration, the top-level configure script is
setting RAW_CXX_FOR_TARGET to only flags, with the compiler executable
being blank. This messes up the libsup++, libjava and I think
other builds, where the executable name ends up being blank
after the -tag CXX invocation of libtool.

I was able to "fix" this by setting CXX_FOR_TARGET and RAW_CXX_FOR_TARGET
to i686-pc-mingw32-c++ (a previously-built (i686-pc-linux-gnu,i686-pc-mingw32)
cross compiler) before I invoke the top-level configure script.

Do you know if this is by design? Or is the top-level configure logic messed
up when build!=host and host=target?

-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/




^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2003-06-30  2:33 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-06-30  8:01 [RAW_]_CXX_FOR_TARGET? Mohan Embar

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).