From: Andreas Jaeger <aj@suse.de>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: gcc@gcc.gnu.org
Subject: Re: Top level configure unsupported targets
Date: Wed, 21 Nov 2001 13:56:00 -0000 [thread overview]
Message-ID: <hoelmh1zzd.fsf@gee.suse.de> (raw)
In-Reply-To: <10111291257.AA21720@vlsi1.ultra.nyu.edu> (kenner@vlsi1.ultra.nyu.edu's message of "Thu, 29 Nov 01 07:57:15 EST")
kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
> Does this look correct:
>
> Configuring for a alphaev56-dec-osf4.0c host.
> *** This configuration is not supported in the following subdirectories:
> target-libffi target-boehm-gc target-zlib target-libjava target-libchill
libchill is correct. The rest are java and its support libraries. On
Linux those are supported but apprently not everywhere. The top level
configure.in disables them via:
alpha*-dec-osf*)
# ld works, but does not support shared libraries. emacs doesn't
# work. newlib is not 64 bit ready. I'm not sure about fileutils.
# gas doesn't generate exception information.
noconfigdirs="$noconfigdirs gas ld emacs fileutils target-newlib target-libgloss ${libgcj}"
;;
I don't rember what needs to be done to enable the libgcj libraries
but with that line in configure.in your output is correct.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
WARNING: multiple messages have this Message-ID
From: Andreas Jaeger <aj@suse.de>
To: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
Cc: gcc@gcc.gnu.org
Subject: Re: Top level configure unsupported targets
Date: Thu, 29 Nov 2001 05:14:00 -0000 [thread overview]
Message-ID: <hoelmh1zzd.fsf@gee.suse.de> (raw)
Message-ID: <20011129051400.dUdbgrnsuGrEotkLhwQjYb7DSP11_F5XqNJjZkEy6ao@z> (raw)
In-Reply-To: <10111291257.AA21720@vlsi1.ultra.nyu.edu>
kenner@vlsi1.ultra.nyu.edu (Richard Kenner) writes:
> Does this look correct:
>
> Configuring for a alphaev56-dec-osf4.0c host.
> *** This configuration is not supported in the following subdirectories:
> target-libffi target-boehm-gc target-zlib target-libjava target-libchill
libchill is correct. The rest are java and its support libraries. On
Linux those are supported but apprently not everywhere. The top level
configure.in disables them via:
alpha*-dec-osf*)
# ld works, but does not support shared libraries. emacs doesn't
# work. newlib is not 64 bit ready. I'm not sure about fileutils.
# gas doesn't generate exception information.
noconfigdirs="$noconfigdirs gas ld emacs fileutils target-newlib target-libgloss ${libgcj}"
;;
I don't rember what needs to be done to enable the libgcj libraries
but with that line in configure.in your output is correct.
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next prev parent reply other threads:[~2001-11-29 13:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 13:53 Richard Kenner
2001-11-21 13:56 ` Andreas Jaeger [this message]
2001-11-29 5:14 ` Andreas Jaeger
2001-11-21 13:56 ` Andreas Schwab
2001-11-29 5:26 ` Andreas Schwab
2001-11-21 14:14 ` Jeff Sturm
2001-11-21 14:40 ` Anthony Green
2001-11-29 6:53 ` Anthony Green
2001-11-21 15:02 ` Tom Tromey
2001-11-21 15:18 ` Jeff Sturm
2001-11-29 8:11 ` Jeff Sturm
2001-11-29 7:52 ` Tom Tromey
2001-11-29 6:03 ` Jeff Sturm
2001-11-29 5:02 ` Richard Kenner
2001-11-21 13:59 Richard Kenner
2001-11-21 14:22 ` Rainer Orth
2001-11-29 6:12 ` Rainer Orth
2001-11-29 5:41 ` Richard Kenner
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=hoelmh1zzd.fsf@gee.suse.de \
--to=aj@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).