public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Sturm <jsturm@one-point.com>
To: Adam Megacz <gcc@lists.megacz.com>
Cc: gcc@gcc.gnu.org
Subject: Re: mingw32 target broken [cygwin as well] [the saga continues]
Date: Sun, 09 Dec 2001 09:07:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.10.10112091043400.10112-100000@mars.deadcafe.org> (raw)
In-Reply-To: <86snalxhfu.fsf@megacz.com>



On 8 Dec 2001, Adam Megacz wrote:
> > http://gcc.gnu.org/ml/libstdc++/2001-03/msg00144.html
> 
> A bit stale, but I was able to hand-edit for the same effect, and it
> worked.

A dirty little secret: if all you want is the java runtime, you can skip
building libstdc++.  Just remove it from the toplevel Makefile.

Unfortunately, libjava assumes cross compilers target newlib, just as
libstdc++ does...

if test -n "${with_cross_host}"; then
   # We are being configured with a cross compiler.  AC_REPLACE_FUNCS
   # may not work correctly, because the compiler may not be able to
   # link executables.

   # We assume newlib.  This lets us hard-code the functions we know
   # we'll have.

This never seemed like desirable behavior to me, in part because newlib
isn't even GNU software.  I'd prefer that configure attempt to link a
program before it assumes it cannot.

> I've also noticed that the configure in the root directory of the gcc
> checkout does not pass the --target=$TARGET option to the invocation
> of configure for libstdc++-v3, although it does pass --with-target-dir

In the target subdirs, "target" becomes "host".

Jeff

  parent reply	other threads:[~2001-12-09 16:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-07 21:06 mingw32 target broken Adam Megacz
2001-12-07 22:01 ` Adam Megacz
     [not found]   ` <20011208003722.A14955@mediaone.net>
2001-12-07 23:12     ` mingw32 target broken [cygwin as well] Adam Megacz
2001-12-07 23:40       ` Craig Rodrigues
2001-12-08  0:00         ` mingw32 target broken [cygwin as well] [didn't know cross-compilers were such an ordeal] Adam Megacz
2001-12-08 16:00           ` Jeff Sturm
2001-12-08 16:05             ` Adam Megacz
2001-12-08 14:42       ` mingw32 target broken [cygwin as well] Jeff Sturm
2001-12-08 16:04         ` mingw32 target broken [cygwin as well] [the saga continues] Adam Megacz
2001-12-08 18:19           ` Craig Rodrigues
2001-12-08 18:30             ` Adam Megacz
2001-12-08 18:39               ` Craig Rodrigues
2001-12-08 18:56                 ` Adam Megacz
2001-12-09  9:07               ` Jeff Sturm [this message]
2001-12-09 20:38                 ` Adam Megacz
2001-12-10 12:36                 ` DJ Delorie
2001-12-10 12:48                   ` Joseph S. Myers
2001-12-10 12:57                     ` DJ Delorie
2001-12-10 21:06                   ` Jeff Sturm
2001-12-10 21:08                     ` DJ Delorie

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=Pine.LNX.4.10.10112091043400.10112-100000@mars.deadcafe.org \
    --to=jsturm@one-point.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gcc@lists.megacz.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).