This is the mail archive of the gcc@gcc.gnu.org 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]

Re: Configure/make problem


On Fri, 27 Aug 1999, Gerald Pfeifer wrote:

> On Fri, 27 Aug 1999, Brian Ford wrote:
> > It seems that the "what does properly unpacked mean" question often
> > appears.  Maybe a sentence or two in the FAQ describing what this
> > means would be appropriate?  I'm not sure if I'm qualified to make
> > that clarification, but I could try if you like.
> 
> As a matter of fact, asking whether you could give it a try was on my
> TODO list. No kidding! :-)
> 

Wow!  I didn't know anyone really noticed me.  Cool.

> Just one suggestion: Instead of *answering* FAQs, I would like to *avoid*
> FAQs, so I believe we want to improve install/build.html itself instead of
> adding a new FAQ entry.
> 

Agreed.  I guess this was what I really meant in the first place.

Ok, This isn't really good, but I believe it is better than what we had
before.  I also made the list for the native and cross compilers have the
same single spacing and added </li>'s where appropriate.

--
Brian Ford
Software Engineer
Vital Visual Simulation Systems
FlightSafety International
Phone: 314-551-8460
Fax:   314-551-8444
Index: build.html
===================================================================
RCS file: /egcs/carton/cvsfiles/wwwdocs/htdocs/install/build.html,v
retrieving revision 1.21
diff -u -r1.21 build.html
--- build.html	1999/08/27 11:36:47	1.21
+++ build.html	1999/08/27 16:51:56
@@ -23,17 +23,19 @@
 
 <ul>
   <li> Build host tools necessary to build the compiler such as texinfo, bison,
-  gperf.
+  gperf.</li>
 
-  <li> Build target tools for use by the compiler such as gas, gld, and
-  binutils if they have been properly unpacked into the GCC source tree.
+  <li> Build target tools for use by the compiler such as binutils (bfd,
+  binutils, gas, gprof, ld, and opcodes)<br>
+  if they have been individually linked or moved into the top level GCC source
+  tree before configuring.</li>
 
-  <li> Perform a 3-stage bootstrap of the compiler.
+  <li> Perform a 3-stage bootstrap of the compiler.</li>
 
-  <li> Perform a comparison test of the stage2 and stage3 compilers.
+  <li> Perform a comparison test of the stage2 and stage3 compilers.</li>
 
   <li> Build runtime libraries using the stage3 compiler from the previous
-  step.
+  step.</li>
 </ul>
 
 <p>If you are short on disk space you might consider `<code>make 
@@ -76,15 +78,17 @@
 following steps:
 <ul>
   <li> Build host tools necessary to build the compiler such as texinfo, bison,
-  gperf.<p>
+  gperf.</li>
 
-  <li> Build target tools for use by the compiler such as gas, gld, and
-  binutils if they have been properly unpacked into the GCC source tree.<p>
+  <li> Build target tools for use by the compiler such as binutils (bfd,
+  binutils, gas, gprof, ld, and opcodes)<br>
+  if they have been individually linked or moved into the top level GCC source
+  tree before configuring.</li>
 
-  <li> Build the compiler (single stage only).<p>
+  <li> Build the compiler (single stage only).</li>
 
   <li> Build runtime libraries using the compiler from the previous
-  step.
+  step.</li>
 </ul>
 
 <p>Note that if an error occurs in any step the make process will exit.

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