This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

PATCH: Document PR 10657

This patch to the FAQ will serve as the resolution of PR 10657 for the
3.3 release, since there's no easy solution to the underlying problem
(namely that the configure script is finding libraries we can't find
when we build jc1).

Tested by looking at the web page, installed.

Mark Mitchell
CodeSourcery, LLC

Index: faq.html
RCS file: /cvs/gcc/wwwdocs/htdocs/faq.html,v
retrieving revision 1.187
retrieving revision 1.188
diff -c -5 -p -r1.187 -r1.188
*** faq.html	26 Mar 2003 01:51:47 -0000	1.187
--- faq.html	9 May 2003 00:24:09 -0000	1.188
*************** Information page</a>.</p>
*** 43,52 ****
--- 43,53 ----
      <li><a href="#rpath">Dynamic linker is unable to find GCC libraries</a></li>
      <li><a href="#rpath">libstdc++/libio tests fail badly with --enable-shared</a></li>
      <li><a href="#gas">GCC can not find GNU as/GNU ld</a></li>
      <li><a href="#environ">cpp: Usage:... Error</a></li>
      <li><a href="#optimizing">Optimizing the compiler itself</a></li>
+     <li><a href="#iconv">Why does <code>libiconv</code> get linked into <code>jc1</code> on Solaris?</a></li>
    <li><a href="#testsuite">Testsuite problems</a>
      <li><a href="#dejagnu">Unable to run the testsuite</a></li>
*************** or end of these variables is an implicit
*** 382,391 ****
--- 383,413 ----
  bootstrapping the compiler with that option turned on.  For example, to 
  test the <code>-fssa</code> option, you could bootstrap like this:</p>
  <pre>make BOOT_CFLAGS="-O2 -fssa" bootstrap</pre>
+ <hr />
+ <h2><a name="iconv">Why does <code>libiconv</code> get linked into <code>jc1</code> on Solaris?</h2>
+ <p>The Java front end requires <code>iconv</code>.  If the compiler
+ used to bootstrap GCC finds <code>libiconv</code> (because the GNU
+ version of <code>libiconv</code> has been installed in the same prefix
+ as the bootstrap compiler), but the newly built GCC does not find the
+ library (because it will be installed with a different prefix), then a
+ link-time error will occur when building <code>jc1</code>.  This
+ problem does not show up so often on platforms that have
+ <code>libiconv</code> in a default location (like
+ <code>/usr/lib</code>) because then both compilers can find a library
+ named <code>libiconv</code>, even though it is a different
+ library.</p>
+ <p>Using <code>--disable-nls</code> at configure-time does not
+ prevent-- this problem because <code>jc1</code> uses
+ <code>iconv</code> even in that case.  Solutions including temporarily
+ removing the GNU <code>libiconv</code>, coying it to a default
+ location such as <code>/usr/llib</code>, and by using
+ <code>--enable-languages</code> at configure-time to disable Java.</p>
  <hr />
  <a name="testsuite"></a>
  <h1>Testsuite problems</h1>

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]