* installation instructions; glitchlet @ 2002-12-02 3:43 Edward Welbourne 2002-12-06 15:50 ` PATCH for " Gerald Pfeifer 0 siblings, 1 reply; 6+ messages in thread From: Edward Welbourne @ 2002-12-02 3:43 UTC (permalink / raw) To: gcc http://gcc.gnu.org/install/configure.html If you have previously built ... paragraph: > ... if make distclean complains that Makefile does not exist, it > probably means that ... actually, make doesn't complain that Makefile does not exist: it complains that it has no rule for making distclean. Albeit this is *caused* by the lack of Makefile, the error message doesn't say that; the above should perhaps say ... if make complains that it has no rule for distclean, this probably means that the Makefile is absent and ... or something similar. --program-transform, --program-suffix use -3.1 as illustration; but gcc is now up to -3.2 ... --with-gnu-as: > and will result in confusion if found assembler is not actually [gas] missing word: the ^ but I'd far sooner see: ... if the assembler found is ... > (Confusion will also result if the compiler finds the GNU assembler > but has not been configured with --with-gnu-as.) ouch - really ? You didn't mean to say "but was configured with --without-gnu-as" ? So I *have to* say --with-gnu-as even though as --version makes it quite plain what assembler it is. OK, duly added to config opts. ah, but no: you subsequently say this only applies on some systems; so the uses of "will" in the two above excerpts should both be "may". --with-cpu: > currently only supported on the some ports, spurious word: the ^^^ > please check the configure script for a complete list of supported models. need instructions on how to *find* this list *within* the script. In fact, does it really live inside the script still ? I am unable to find the text arm700, for instance. Eddy. ^ permalink raw reply [flat|nested] 6+ messages in thread
* PATCH for Re: installation instructions; glitchlet 2002-12-02 3:43 installation instructions; glitchlet Edward Welbourne @ 2002-12-06 15:50 ` Gerald Pfeifer 2002-12-10 1:32 ` Edward Welbourne 0 siblings, 1 reply; 6+ messages in thread From: Gerald Pfeifer @ 2002-12-06 15:50 UTC (permalink / raw) To: Edward Welbourne; +Cc: gcc, gcc-patches On Mon, 2 Dec 2002, Edward Welbourne wrote: > http://gcc.gnu.org/install/configure.html Thanks for the feedback! I have just committed the following patch to mainline, so that it will be part of GCC 3.3 (and later). Gerald 2002-12-07 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> * doc/install.texi (Configuration): Improve description of cases where `make distclean` may fail; clarify --with-gnu-as; fix grammar. Index: doc/install.texi =================================================================== RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v retrieving revision 1.150 diff -u -3 -p -r1.150 install.texi --- doc/install.texi 13 Nov 2002 20:55:02 -0000 1.150 +++ doc/install.texi 6 Dec 2002 23:29:37 -0000 @@ -293,12 +293,12 @@ of @var{srcdir} is unsupported. If you have previously built GCC in the same directory for a different target machine, do @samp{make distclean} to delete all files -that might be invalid. One of the files this deletes is -@file{Makefile}; if @samp{make distclean} complains that @file{Makefile} -does not exist, it probably means that the directory is already suitably -clean. However, with the recommended method of building in a separate -@var{objdir}, you should simply use a different @var{objdir} for each -target. +that might be invalid. One of the files this deletes is @file{Makefile}; +if @samp{make distclean} complains that @file{Makefile} does not exist +or issues a message like ``don't know how to make distclean'' it probably +means that the directory is already suitably clean. However, with the +recommended method of building in a separate @var{objdir}, you should +simply use a different @var{objdir} for each target. Second, when configuring a native system, either @command{cc} or @command{gcc} must be in your path or you must set @env{CC} in @@ -544,8 +544,8 @@ argument, only @option{--enable-shared} @item @anchor{with-gnu-as}--with-gnu-as Specify that the compiler should assume that the assembler it finds is the GNU assembler. However, this does not modify -the rules to find an assembler and will result in confusion if found -assembler is not actually the GNU assembler. (Confusion will also +the rules to find an assembler and will result in confusion if the +assembler found is not actually the GNU assembler. (Confusion may also result if the compiler finds the GNU assembler but has not been configured with @option{--with-gnu-as}.) If you have more than one assembler installed on your system, you may want to use this option in @@ -718,7 +718,7 @@ Microsoft Win32 API thread support. @item --with-cpu=@var{cpu} Specify which cpu variant the compiler should generate code for by default. This is currently -only supported on the some ports, specifically arm, powerpc, and +only supported on some ports, specifically arm, powerpc, and SPARC@. If configure does not recognize the model name (e.g.@: arm700, 603e, or ultrasparc) you provide, please check the configure script for a complete list of supported models. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PATCH for Re: installation instructions; glitchlet 2002-12-06 15:50 ` PATCH for " Gerald Pfeifer @ 2002-12-10 1:32 ` Edward Welbourne 2002-12-27 9:33 ` Gerald Pfeifer 0 siblings, 1 reply; 6+ messages in thread From: Edward Welbourne @ 2002-12-10 1:32 UTC (permalink / raw) To: pfeifer; +Cc: gcc, gcc-patches > Thanks for the feedback! you're welcome - every little thing you fix is one less thing for me to worry about *next* time I build gcc ;^) > I have just committed the following patch to mainline, so that it > will be part of GCC 3.3 (and later). good. I note, however, that you still refer the reader back to the configure script for `a complete list of supported models', though I couldn't find such a list in the configure script; in particular, I grepped for at least one of the names given in the `e.g.' and it didn't show up. How does one find the list ? Eddy. ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PATCH for Re: installation instructions; glitchlet 2002-12-10 1:32 ` Edward Welbourne @ 2002-12-27 9:33 ` Gerald Pfeifer 2002-12-27 11:08 ` Daniel Jacobowitz 0 siblings, 1 reply; 6+ messages in thread From: Gerald Pfeifer @ 2002-12-27 9:33 UTC (permalink / raw) To: Edward Welbourne; +Cc: gcc, gcc-patches, David S. Miller, Jakub Jelinek On Tue, 10 Dec 2002, Edward Welbourne wrote: >> I have just committed the following patch to mainline, so that it >> will be part of GCC 3.3 (and later). > good. I note, however, that you still refer the reader back to the > configure script for `a complete list of supported models', though I > couldn't find such a list in the configure script; in particular, I > grepped for at least one of the names given in the `e.g.' and it > didn't show up. How does one find the list ? Sorry, I don't know (respectively, I couldn't find it). :-( David, Jakub, in gcc/doc/install.texi we have @item --with-cpu=@var{cpu} Specify which cpu variant the compiler should generate code for by default. This is currently only supported on some ports, specifically arm, powerpc, and SPARC@. If configure does not recognize the model name (e.g.@: arm700, 603e, or ultrasparc) you provide, please check the configure script for a complete list of supported models. but this doesn't seem to work; is there any possibility to find the actual cpu variant for SPARCs, for example? Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/ ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PATCH for Re: installation instructions; glitchlet 2002-12-27 9:33 ` Gerald Pfeifer @ 2002-12-27 11:08 ` Daniel Jacobowitz 2002-12-31 3:42 ` Gerald Pfeifer 0 siblings, 1 reply; 6+ messages in thread From: Daniel Jacobowitz @ 2002-12-27 11:08 UTC (permalink / raw) To: Gerald Pfeifer Cc: Edward Welbourne, gcc, gcc-patches, David S. Miller, Jakub Jelinek On Fri, Dec 27, 2002 at 04:40:33PM +0100, Gerald Pfeifer wrote: > On Tue, 10 Dec 2002, Edward Welbourne wrote: > >> I have just committed the following patch to mainline, so that it > >> will be part of GCC 3.3 (and later). > > good. I note, however, that you still refer the reader back to the > > configure script for `a complete list of supported models', though I > > couldn't find such a list in the configure script; in particular, I > > grepped for at least one of the names given in the `e.g.' and it > > didn't show up. How does one find the list ? > > Sorry, I don't know (respectively, I couldn't find it). :-( You can find it in config.gcc, It's around line 2665. However it only works for a couple of platforms. Looks like ARM, PowerPC, SPARC, and v850. For SPARC the list is: case ".$with_cpu" in .supersparc | .hypersparc | .ultrasparc | .v7 | .v8 | .v9) [My patch to use --with-cpu across all architectures was never reviewed and is now out of date again. I'll resubmit it when I feel like being ignored next.] -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer ^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: PATCH for Re: installation instructions; glitchlet 2002-12-27 11:08 ` Daniel Jacobowitz @ 2002-12-31 3:42 ` Gerald Pfeifer 0 siblings, 0 replies; 6+ messages in thread From: Gerald Pfeifer @ 2002-12-31 3:42 UTC (permalink / raw) To: Daniel Jacobowitz Cc: Edward Welbourne, gcc, gcc-patches, David S. Miller, Jakub Jelinek On Fri, 27 Dec 2002, Daniel Jacobowitz wrote: > You can find it in config.gcc, It's around line 2665. However it only > works for a couple of platforms. Looks like ARM, PowerPC, SPARC, and > v850. For SPARC the list is: > > case ".$with_cpu" in > .supersparc | .hypersparc | .ultrasparc | .v7 | .v8 | .v9) Thanks for the feedback; I just committed the patch below to mainline and the 3.3-branch. > [My patch to use --with-cpu across all architectures was never > reviewed and is now out of date again. I'll resubmit it when I feel > like being ignored next.] I would review it if I could, but it definitely sounds desirable! Gerald 2002-12-31 Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> * doc/install.texi (Configuration): Explicitly refer gcc/config.gcc for a list of cpu models. Index: doc/install.texi =================================================================== RCS file: /cvs/gcc/gcc/gcc/doc/install.texi,v retrieving revision 1.157 diff -u -3 -p -r1.157 install.texi --- doc/install.texi 30 Dec 2002 21:33:42 -0000 1.157 +++ doc/install.texi 31 Dec 2002 10:34:01 -0000 @@ -716,8 +716,8 @@ Specify which cpu variant the compiler should generate code for by default. This is currently only supported on some ports, specifically arm, powerpc, and SPARC@. If configure does not recognize the model name (e.g.@: arm700, -603e, or ultrasparc) you provide, please check the configure script -for a complete list of supported models. +603e, or ultrasparc) you provide, please check the +@command{gcc/config.gcc} script for a complete list of supported models. @item --enable-altivec Specify that the target supports AltiVec vector enhancements. This ^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2002-12-31 10:43 UTC | newest] Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2002-12-02 3:43 installation instructions; glitchlet Edward Welbourne 2002-12-06 15:50 ` PATCH for " Gerald Pfeifer 2002-12-10 1:32 ` Edward Welbourne 2002-12-27 9:33 ` Gerald Pfeifer 2002-12-27 11:08 ` Daniel Jacobowitz 2002-12-31 3:42 ` Gerald Pfeifer
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).