[wwwdocs] codingconventions.html: autotools update

[wwwdocs] codingconventions.html: autotools update

[Ralf Wildenhues]

Hello,

please consider this patch to update the coding conventions web page.
FYI, I do not have commit privs.

Cheers,
Ralf

2007-08-09  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>

	* htdocs/codingconventions.html: Update libtool file list.
	configure.in is now configure.ac.

Index: htdocs/codingconventions.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
retrieving revision 1.51
diff -u -r1.51 codingconventions.html
--- htdocs/codingconventions.html	27 Jul 2007 04:50:47 -0000	1.51
+++ htdocs/codingconventions.html	9 Aug 2007 19:52:14 -0000
@@ -446,20 +446,22 @@
 meaningful and unique.  Don't install the patch, install the whole
 file.</li>
 
-<li>ltconfig, ltmain.sh, libtool.m4, ltcf-c.sh, ltcf-cxx.sh,
+<li>ltmain.sh, libtool.m4, ltoptions.m4, ltsugar.m4, ltversion.m4,
+lt~obsolete.m4, and formerly also ltconfig, ltcf-c.sh, ltcf-cxx.sh,
 ltcf-gcj.sh: The master copy of these files is the CVS repository of
 <a href="http://www.gnu.org/software/libtool/libtool.html">GNU
 libtool</a>.  Patches should be posted to <a
 href="mailto:libtool-patches@gnu.org">libtool-patches@gnu.org</a>.
 Only after the change makes it to the libtool CVS tree should the new
 files be installed in the GCC source tree.  ltconfig and ltmain.sh are
-generated files from ltconfig.in and ltmain.in, respectively, so, when
+generated files from ltconfig.in and ltmain.in, respectively, and with
+libtool 2.1, the latter is generated from ltmain.m4sh, so, when
 you post the patch, make sure you're patching the source file, not the
 generated one.  When you update these generated files in the GCC
 repository, make sure they report the same timestamp and version number,
 and note this version number in the ChangeLog.</li>
 
-<li>Top-level configure.in, configure, Makefile.in, config-ml.in,
+<li>Top-level configure.ac, configure, Makefile.in, config-ml.in,
 config.if and most other top-level shell-scripts: Please try to keep
 these files in sync with the corresponding files in the src repository
 at sourceware.org.  Some people hope to eventually merge these

Re: [wwwdocs] codingconventions.html: autotools update

[Gerald Pfeifer]

On Thu, 9 Aug 2007, Ralf Wildenhues wrote:
> please consider this patch to update the coding conventions web page.
> FYI, I do not have commit privs.

I was hoping one of our configury master would jump at this patch. ;-)

Alexandre, DJ, Paolo, would you mind having a look?  If this is fine,
just let us know and I'll commit this on behalf of Ralf.  Also, if you
request some changes, I'll be happy to make those and then commit an
update version.

Thanks,
Gerald

> 2007-08-09  Ralf Wildenhues  <Ralf.Wildenhues@gmx.de>
> 
> 	* htdocs/codingconventions.html: Update libtool file list.
> 	configure.in is now configure.ac.
> 
> Index: htdocs/codingconventions.html
> ===================================================================
> RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
> retrieving revision 1.51
> diff -u -r1.51 codingconventions.html
> --- htdocs/codingconventions.html	27 Jul 2007 04:50:47 -0000	1.51
> +++ htdocs/codingconventions.html	9 Aug 2007 19:52:14 -0000
> @@ -446,20 +446,22 @@
>  meaningful and unique.  Don't install the patch, install the whole
>  file.</li>
>  
> -<li>ltconfig, ltmain.sh, libtool.m4, ltcf-c.sh, ltcf-cxx.sh,
> +<li>ltmain.sh, libtool.m4, ltoptions.m4, ltsugar.m4, ltversion.m4,
> +lt~obsolete.m4, and formerly also ltconfig, ltcf-c.sh, ltcf-cxx.sh,
>  ltcf-gcj.sh: The master copy of these files is the CVS repository of
>  <a href="http://www.gnu.org/software/libtool/libtool.html">GNU
>  libtool</a>.  Patches should be posted to <a
>  href="mailto:libtool-patches@gnu.org">libtool-patches@gnu.org</a>.
>  Only after the change makes it to the libtool CVS tree should the new
>  files be installed in the GCC source tree.  ltconfig and ltmain.sh are
> -generated files from ltconfig.in and ltmain.in, respectively, so, when
> +generated files from ltconfig.in and ltmain.in, respectively, and with
> +libtool 2.1, the latter is generated from ltmain.m4sh, so, when
>  you post the patch, make sure you're patching the source file, not the
>  generated one.  When you update these generated files in the GCC
>  repository, make sure they report the same timestamp and version number,
>  and note this version number in the ChangeLog.</li>
>  
> -<li>Top-level configure.in, configure, Makefile.in, config-ml.in,
> +<li>Top-level configure.ac, configure, Makefile.in, config-ml.in,
>  config.if and most other top-level shell-scripts: Please try to keep
>  these files in sync with the corresponding files in the src repository
>  at sourceware.org.  Some people hope to eventually merge these
> 

-- 
Gerald (Jerry) Pfeifer   gerald@pfeifer.com   http://www.pfeifer.com/gerald/

Re: [wwwdocs] codingconventions.html: autotools update

[Paolo Bonzini]

Gerald Pfeifer wrote:
> On Thu, 9 Aug 2007, Ralf Wildenhues wrote:
>> please consider this patch to update the coding conventions web page.
>> FYI, I do not have commit privs.
> 
> I was hoping one of our configury master would jump at this patch. ;-)
> 
> Alexandre, DJ, Paolo, would you mind having a look?  If this is fine,
> just let us know and I'll commit this on behalf of Ralf.  Also, if you
> request some changes, I'll be happy to make those and then commit an
> update version.

Good.  I'd add a note that ltgcc.m4 is *not* imported from upstream.

Paolo

Re: [wwwdocs] codingconventions.html: autotools update

[Gerald Pfeifer]

On Mon, 10 Sep 2007, Paolo Bonzini wrote:
> Good.  I'd add a note that ltgcc.m4 is *not* imported from upstream.

Good catch!  I added such a note and committed the revised patch
below.  Thanks for the review (and especially thanks to Ralf)!

Gerald

Index: codingconventions.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/codingconventions.html,v
retrieving revision 1.51
diff -u -3 -p -r1.51 codingconventions.html
--- codingconventions.html	27 Jul 2007 04:50:47 -0000	1.51
+++ codingconventions.html	10 Sep 2007 18:39:54 -0000
@@ -446,20 +446,24 @@ installed in the GCC source tree, so tha
 meaningful and unique.  Don't install the patch, install the whole
 file.</li>
 
-<li>ltconfig, ltmain.sh, libtool.m4, ltcf-c.sh, ltcf-cxx.sh,
+<li>ltmain.sh, libtool.m4, ltoptions.m4, ltsugar.m4, ltversion.m4,
+lt~obsolete.m4, and formerly also ltconfig, ltcf-c.sh, ltcf-cxx.sh,
 ltcf-gcj.sh: The master copy of these files is the CVS repository of
 <a href="http://www.gnu.org/software/libtool/libtool.html">GNU
 libtool</a>.  Patches should be posted to <a
 href="mailto:libtool-patches@gnu.org">libtool-patches@gnu.org</a>.
 Only after the change makes it to the libtool CVS tree should the new
-files be installed in the GCC source tree.  ltconfig and ltmain.sh are
-generated files from ltconfig.in and ltmain.in, respectively, so, when
-you post the patch, make sure you're patching the source file, not the
-generated one.  When you update these generated files in the GCC
-repository, make sure they report the same timestamp and version number,
-and note this version number in the ChangeLog.</li>
+files be installed in the GCC source tree.<br />
+ltgcc.m4 is not imported from upstream.<br />
+ltconfig and ltmain.sh are generated files from ltconfig.in and
+ltmain.in, respectively, and with libtool 2.1, the latter is generated
+from ltmain.m4sh, so, when you post the patch, make sure you're
+patching the source file, not the generated one.  When you update
+these generated files in the GCC repository, make sure they report the
+same timestamp and version number, and note this version number in the
+ChangeLog.</li>
 
-<li>Top-level configure.in, configure, Makefile.in, config-ml.in,
+<li>Top-level configure.ac, configure, Makefile.in, config-ml.in,
 config.if and most other top-level shell-scripts: Please try to keep
 these files in sync with the corresponding files in the src repository
 at sourceware.org.  Some people hope to eventually merge these