From: Gerald Pfeifer <gerald@pfeifer.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>,
java-patches@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [wwwdocs,Java] Obsolete GCJ FAQ entry for Solaris?
Date: Fri, 21 Dec 2012 04:02:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1212201801500.2358@tuna.site> (raw)
In-Reply-To: <alpine.LNX.2.00.1211022129370.2266@tuna.site>
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 @@
> <ol>
> <li><a href="#3_1">I need something more recent than the last release; how
> should I build it?</a></li>
> - <li><a href="#3_2">Linker bug on Solaris</a></li>
> </ol>
> </li>
> <li><a href="#4_0">Gcj Compile/Link Questions</a>
> @@ -278,33 +277,6 @@ $ gij HelloWorld
> </dd>
> </dl>
>
> - <hr />
> - <h3><a name="3_2">3.2 Linker bug on Solaris</a></h3>
> - <dl>
> - <dd>
> - There is a known problem with the <a href="http://gcc.gnu.org/ml/gcc-bugs/1999-10/msg00159.html">
> - native Solaris linker</a> 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:
> - <pre>
> -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
> - </pre>
> - A known workaround for this and other reported link problems on the
> - various releases of Solaris is to build gcc/gcj with the <a href="ftp://sources.redhat.com/pub/binutils/snapshots">
> - latest GNU binutils</a> instead of the native Solaris <tt>ld</tt>. The
> - most straightforward way to do this is to build and install binutils,
> - and then reference it in the configure for gcc via <tt>--with-ld=/path_to_binutils_install/bin/ld</tt>
> - (<tt>--with-as</tt> may also be similarly specified but is not believed
> - to be required).
> - <br />
> - Please note, gcc/gcj must be built using GNU ld prior to doing a
> - clean build of libgcj!
> - </dd>
> - </dl>
> -
> <h2><a name="4_0">Gcj Compile/Link Questions</a></h2>
>
> <h3><a name="4_1">4.1 Why do I get <tt>undefined reference to `main'</tt>
next prev parent reply other threads:[~2012-12-21 4:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 20:32 Gerald Pfeifer
2012-12-21 4:02 ` Gerald Pfeifer [this message]
2012-12-21 9:51 ` Andrew Haley
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=alpine.LNX.2.00.1212201801500.2358@tuna.site \
--to=gerald@pfeifer.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=java-patches@gcc.gnu.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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).