public inbox for java@gcc.gnu.org
 help / color / mirror / Atom feed
From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
Cc: Richard Henderson <rth@redhat.com>,
	Joe Buck <Joe.Buck@synopsys.com>,
	Alexandre Oliva <aoliva@redhat.com>, <glebourgeois@amadeus.net>,
	<gcc@gcc.gnu.org>, <java@gcc.gnu.org>,
	Tom Tromey <tromey@redhat.com>
Subject: Re: Still failing to bootstrap on Solaris (CONFIG_SHELL doesn't help)
Date: Thu, 02 May 2002 09:36:00 -0000	[thread overview]
Message-ID: <Pine.BSF.4.44.0205021507520.92391-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <yddpu0ex1zc.fsf@xayide.TechFak.Uni-Bielefeld.DE>

[ I added an explicit Cc: to Tom and the java list, as Tom has spent
  most time with this "nice" bug. ]

On 2 May 2002, Rainer Orth wrote:
>> But java is *not* default on solaris, so at this late date
>> I am unconcerned.
> It used to be up to solaris 2.7, and disabled for 2.8 in the toplevel
> configure.in.  This has changed, though: now it's on by default for all
> releases, with a check which bails out if libgcj.la is present in $libdir.
> This check is for sparc-*-solaris2.8 only at the moment.  The new reports
> indicate that this problem occurs at least with some ld patchlevels on
> solaris 2.7.  I've just verified that it happens with the latest solaris
> 2.6 (107733-10) and 2.5.1 (103627-15) ld patches as well.
>
> So the safest approach seems to be to match *-*-solaris2* there to
> accomodate all of sparc, sparcv9 and i?86.

As the one having reported the problem originally (and tried various
fixes Tom and others have suggested) I agree.

Given your new information, this seems to be the safest approach. (Can
one of you submit a patch for configure and the installation docs for
this?)

Gerald
-- 
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/

       reply	other threads:[~2002-05-02 16:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <yddpu0ex1zc.fsf@xayide.TechFak.Uni-Bielefeld.DE>
2002-05-02  9:36 ` Gerald Pfeifer [this message]
     [not found] <20020502135546.A5069@redhat.com>
     [not found] ` <15569.45674.297203.299627@xayide.TechFak.Uni-Bielefeld.DE>
     [not found]   ` <20020502144819.A5145@redhat.com>
     [not found]     ` <20020502.143920.20510740.davem@redhat.com>
     [not found]       ` <15569.46538.150141.211082@xayide.TechFak.Uni-Bielefeld.DE>
2002-05-02 19:22         ` Alexandre Oliva
2002-05-03  0:45           ` Mark Mitchell
2002-05-03 11:27             ` Alexandre Oliva
2002-05-03  4:05           ` Rainer Orth
2002-05-03 21:56           ` Alexandre Oliva
2002-05-03 22:04             ` David S. Miller
2002-05-03 22:22               ` Mark Mitchell
2002-05-03 22:23               ` Alexandre Oliva
2002-05-03 22:28                 ` David S. Miller
2002-05-03 22:41                   ` Alexandre Oliva

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.BSF.4.44.0205021507520.92391-100000@naos.dbai.tuwien.ac.at \
    --to=pfeifer@dbai.tuwien.ac.at \
    --cc=Joe.Buck@synopsys.com \
    --cc=aoliva@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=glebourgeois@amadeus.net \
    --cc=java@gcc.gnu.org \
    --cc=ro@TechFak.Uni-Bielefeld.DE \
    --cc=rth@redhat.com \
    --cc=tromey@redhat.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).