From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15368 invoked by alias); 21 Dec 2012 04:02:27 -0000 Received: (qmail 15341 invoked by uid 22791); 21 Dec 2012 04:02:25 -0000 X-SWARE-Spam-Status: No, hits=-3.1 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_HOSTKARMA_NO X-Spam-Check-By: sourceware.org Received: from ainaz.pair.com (HELO ainaz.pair.com) (209.68.2.66) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 21 Dec 2012 04:02:18 +0000 Received: from [192.168.0.10] (199.244.3.202.dsl.dyn.mana.pf [202.3.244.199]) by ainaz.pair.com (Postfix) with ESMTPSA id 706BD3F427; Thu, 20 Dec 2012 23:02:12 -0500 (EST) Date: Fri, 21 Dec 2012 04:02:00 -0000 From: Gerald Pfeifer To: Rainer Orth , java-patches@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: [wwwdocs,Java] Obsolete GCJ FAQ entry for Solaris? In-Reply-To: Message-ID: References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Mailing-List: contact java-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-patches-owner@gcc.gnu.org X-SW-Source: 2012-q4/txt/msg00062.txt.bz2 PING. On Fri, 2 Nov 2012, Gerald Pfeifer wrote: > Rainer (or others), > > the FAQ entry below seems obsolete to me (dates back more than a > decade). Shall we remove it, or is there something else we still > should document (in addition to gcc/doc/install.texi)? > > Gerald > > Index: faq.html > =================================================================== > RCS file: /cvs/gcc/wwwdocs/htdocs/java/faq.html,v > retrieving revision 1.69 > diff -u -3 -p -r1.69 faq.html > --- faq.html 2 Nov 2012 19:59:34 -0000 1.69 > +++ faq.html 2 Nov 2012 20:29:12 -0000 > @@ -36,7 +36,6 @@ >
    >
  1. I need something more recent than the last release; how > should I build it?
  2. > -
  3. Linker bug on Solaris
  4. >
> >
  • Gcj Compile/Link Questions > @@ -278,33 +277,6 @@ $ gij HelloWorld > > > > -
    > -

    3.2 Linker bug on Solaris

    > -
    > -
    > - There is a known problem with the > - native Solaris linker when using gcc/gcj. A good indication you've > - run into this problem is if you get an error that looks like the following > - when building libgcj: > -
    > -ld: warning: option -o appears more than once, first setting taken
    > -ld: fatal: file libfoo.so: cannot open file: No such file or directory
    > -ld: fatal: File processing errors. No output written to .libs/libfoo.so
    > -collect2: ld returned 1 exit status
    > -          
    > - A known workaround for this and other reported link problems on the > - various releases of Solaris is to build gcc/gcj with the > - latest GNU binutils instead of the native Solaris ld. The > - most straightforward way to do this is to build and install binutils, > - and then reference it in the configure for gcc via --with-ld=/path_to_binutils_install/bin/ld > - (--with-as may also be similarly specified but is not believed > - to be required). > -
    > - Please note, gcc/gcj must be built using GNU ld prior to doing a > - clean build of libgcj! > -
    > -
    > - >

    Gcj Compile/Link Questions

    > >

    4.1 Why do I get undefined reference to `main'