On 02/11/2007 05:59 PM, Gerald Pfeifer wrote:
On Sun, 11 Feb 2007, Larry Evans wrote:
[snip]
I can't comment on the contents, but that HTML file is generated from
our texinfo documentation; the master source for that is
gcc/doc/install.texi
in our SVN repository.
Gerald
THanks Gerald. C
On Sun, 11 Feb 2007, Larry Evans wrote:
[snip]
I tried downloading and editying
http://gcc.gnu.org/install/configure.html; however, I soon ran into problems.
Attached is a diff between the original .html and the
modifications I tried. It shows that even the comments in config.in
are confusing :(
On 02/11/2007 04:28 PM, Larry Evans wrote:
[snip]
I think a patch adding descriptions to the docs would be an improvement.
Would you like to submit one?
Thanks,
--Kaveh
I could, but the only thing I would do would be something like:
The meaning of these flags can be inferred
On 02/11/2007 02:16 PM, Kaveh R. GHAZI wrote:
On Fri, 9 Feb 2007, Larry Evans wrote:
[snip]
describe what the flags mean. Could someone do that or provide
a link to the descriptions.
The --enable-checking values are described briefly in gcc/config.in,
here's a link for quick access:
http://
On Fri, 9 Feb 2007, Larry Evans wrote:
> The doc on --enable-checking at:
>
>http://gcc.gnu.org/install/configure.html
>
> contains:
>
>--enable-checking=list
>
> and implies that list may either be a category (yes,all,release,no) or a
> sequence of flags (e.g. fold,gcac,gc,valgrind); howe
On 02/09/2007 12:18 PM, Larry Evans wrote:
[snip]
compiler. When just using --enable-checking=yes, I was able to
use gdb to find that the value of __FILE__ was corrupted:
(gdb) up
#1 0x0809e6eb in tsubst (t=0x4034f8a0, args=0x40351ca8, complain=3,
in_decl=0x4032eea0) at ../../gcc-4.1.1/gcc
The doc on --enable-checking at:
http://gcc.gnu.org/install/configure.html
contains:
--enable-checking=list
and implies that list may either be a category (yes,all,release,no) or a
sequence of flags (e.g. fold,gcac,gc,valgrind); however, it doesn't
describe what the flags mean. Could so
