Skip to content

R
riscv-gcc-1
Commit 8b171e55 by Phil Edwards
Options

configure.in: Rename... 

2003-08-05  Phil Edwards  <pme@gcc.gnu.org>

	* configure.in:  Rename...
	* configure.ac:  ...to this.
	* docs/html/17_intro/porting.texi:  Update name.

	* docs/html/17_intro/porting.html:  Regenerate.
	* config.h.in, Makefile.in, include/Makefile.in, libmath/Makefile.in,
	libsupc++/Makefile.in, po/Makefile.in, src/Makefile.in,
	testsuite/Makefile.in:  Regenerate (picks up new dependancy).

From-SVN: r70194
parent b20d9f0c
Showing with 73 additions and 54 deletions
libstdc++-v3/ChangeLog
2003-08-05 Phil Edwards <pme@gcc.gnu.org> 2003-08-05 Phil Edwards <pme@gcc.gnu.org>
* configure.in: Rename...
* configure.ac: ...to this.
* docs/html/17_intro/porting.texi: Update name.
* docs/html/17_intro/porting.html: Regenerate.
* config.h.in, Makefile.in, include/Makefile.in, libmath/Makefile.in,
libsupc++/Makefile.in, po/Makefile.in, src/Makefile.in,
testsuite/Makefile.in: Regenerate (picks up new dependancy).
2003-08-05 Phil Edwards <pme@gcc.gnu.org>
* acinclude.m4 (GLIBCXX_ENABLE_SJLJ_EXCEPTIONS): Put down the crack * acinclude.m4 (GLIBCXX_ENABLE_SJLJ_EXCEPTIONS): Put down the crack
pipe, open the window to let out the fumes, redo the option-handling pipe, open the window to let out the fumes, redo the option-handling
logic to properly execute the detection test. logic to properly execute the detection test.
......
libstdc++-v3/Makefile.in
...@@ -287,7 +287,7 @@ DIST_COMMON = README ../ABOUT-NLS ../COPYING ../COPYING.LIB \ ...@@ -287,7 +287,7 @@ DIST_COMMON = README ../ABOUT-NLS ../COPYING ../COPYING.LIB \
../ltcf-c.sh ../ltcf-cxx.sh ../ltcf-gcj.sh ../ltconfig \ ../ltcf-c.sh ../ltcf-cxx.sh ../ltcf-gcj.sh ../ltconfig \
../ltmain.sh ../missing ../mkinstalldirs ../ylwrap ChangeLog \ ../ltmain.sh ../missing ../mkinstalldirs ../ylwrap ChangeLog \
Makefile.am Makefile.in acconfig.h acinclude.m4 aclocal.m4 \ Makefile.am Makefile.in acconfig.h acinclude.m4 aclocal.m4 \
config.h.in configure configure.in config.h.in configure configure.ac
DIST_SUBDIRS = $(SUBDIRS) DIST_SUBDIRS = $(SUBDIRS)
all: config.h all: config.h
$(MAKE) $(AM_MAKEFLAGS) all-recursive $(MAKE) $(AM_MAKEFLAGS) all-recursive
...@@ -296,7 +296,7 @@ all: config.h ...@@ -296,7 +296,7 @@ all: config.h
am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \ am__CONFIG_DISTCLEAN_FILES = config.status config.cache config.log \
configure.lineno configure.lineno
$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.in $(ACLOCAL_M4) $(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.ac $(ACLOCAL_M4)
cd $(top_srcdir) && \ cd $(top_srcdir) && \
$(AUTOMAKE) --foreign Makefile $(AUTOMAKE) --foreign Makefile
Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status
...@@ -304,10 +304,10 @@ Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.s ...@@ -304,10 +304,10 @@ Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.s
$(top_builddir)/config.status: $(srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES) $(top_builddir)/config.status: $(srcdir)/configure $(CONFIG_STATUS_DEPENDENCIES)
$(SHELL) ./config.status --recheck $(SHELL) ./config.status --recheck
$(srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(srcdir)/configure.in $(ACLOCAL_M4) $(CONFIGURE_DEPENDENCIES) $(srcdir)/configure: @MAINTAINER_MODE_TRUE@ $(srcdir)/configure.ac $(ACLOCAL_M4) $(CONFIGURE_DEPENDENCIES)
cd $(srcdir) && $(AUTOCONF) cd $(srcdir) && $(AUTOCONF)
$(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ configure.in acinclude.m4 $(ACLOCAL_M4): @MAINTAINER_MODE_TRUE@ configure.ac acinclude.m4
cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS) cd $(srcdir) && $(ACLOCAL) $(ACLOCAL_AMFLAGS)
config.h: stamp-h1 config.h: stamp-h1
...@@ -320,7 +320,7 @@ stamp-h1: $(srcdir)/config.h.in $(top_builddir)/config.status ...@@ -320,7 +320,7 @@ stamp-h1: $(srcdir)/config.h.in $(top_builddir)/config.status
@rm -f stamp-h1 @rm -f stamp-h1
cd $(top_builddir) && $(SHELL) ./config.status config.h cd $(top_builddir) && $(SHELL) ./config.status config.h
$(srcdir)/config.h.in: @MAINTAINER_MODE_TRUE@ $(top_srcdir)/configure.in $(ACLOCAL_M4) $(top_srcdir)/acconfig.h $(srcdir)/config.h.in: @MAINTAINER_MODE_TRUE@ $(top_srcdir)/configure.ac $(ACLOCAL_M4) $(top_srcdir)/acconfig.h
cd $(top_srcdir) && $(AUTOHEADER) cd $(top_srcdir) && $(AUTOHEADER)
touch $(srcdir)/config.h.in touch $(srcdir)/config.h.in
......
libstdc++-v3/config.h.in
/* config.h.in. Generated from configure.in by autoheader. */ /* config.h.in. Generated from configure.ac by autoheader. */
// acconfig.h symbols and macros for libstdc++ v3 -*- C++ -*- // acconfig.h symbols and macros for libstdc++ v3 -*- C++ -*-
// Defines libstdc++ version. // Defines libstdc++ version.
......
libstdc++-v3/docs/html/17_intro/porting.html
...@@ -3,8 +3,7 @@ ...@@ -3,8 +3,7 @@
<title>Porting libstdc++-v3</title> <title>Porting libstdc++-v3</title>
<meta http-equiv="Content-Type" content="text/html"> <meta http-equiv="Content-Type" content="text/html">
<meta name="description" content="Porting libstdc++-v3"> <meta name="description" content="Porting libstdc++-v3">
<meta name="generator" content="makeinfo 4.3"> <meta name="generator" content="makeinfo 4.6">
<link href="http://www.gnu.org/software/texinfo/" rel="generator-home">
<!-- <!--
Copyright &copy; 2000, 2001, 2002, 2003 Free Software Foundation, Inc. Copyright &copy; 2000, 2001, 2002, 2003 Free Software Foundation, Inc.
...@@ -25,20 +24,29 @@ texts being (a) (see below), and with the Back-Cover Texts being (b) ...@@ -25,20 +24,29 @@ texts being (a) (see below), and with the Back-Cover Texts being (b)
<p>You have freedom to copy and modify this GNU Manual, like GNU <p>You have freedom to copy and modify this GNU Manual, like GNU
software. Copies published by the Free Software Foundation raise software. Copies published by the Free Software Foundation raise
funds for GNU development.--> funds for GNU development.-->
<meta http-equiv="Content-Style-Type" content="text/css">
<style type="text/css"><!--
pre.display { font-family:inherit }
pre.format { font-family:inherit }
pre.smalldisplay { font-family:inherit; font-size:smaller }
pre.smallformat { font-family:inherit; font-size:smaller }
pre.smallexample { font-size:smaller }
pre.smalllisp { font-size:smaller }
--></style>
</head> </head>
<body> <body>
<h1 class="settitle">Porting libstdc++-v3</h1> <h1 class="settitle">Porting libstdc++-v3</h1>
<div class="node"> <div class="node">
<p><hr> <p><hr>
Node:<a name="Top">Top</a>, Node:&nbsp;<a name="Top">Top</a>,
Next:<a rel="next" accesskey="n" href="#Operating%20system">Operating system</a>, Next:&nbsp;<a rel="next" accesskey="n" href="#Operating%20system">Operating system</a>,
Up:<a rel="up" accesskey="u" href="#dir">(dir)</a> Up:&nbsp;<a rel="up" accesskey="u" href="#dir">(dir)</a>
<br> <br>
</div> </div>
<h2 class="unnumbered">Porting libstdc++-v3</h2> <h2 class="unnumbered">Porting libstdc++-v3</h2>
<p>This document explains how to port libstdc++-v3 (the GNU C++ library) to <p>This document explains how to port libstdc++-v3 (the GNU C++ library) to
a new target. a new target.
<p>In order to make the GNU C++ library (libstdc++-v3) work with a new <p>In order to make the GNU C++ library (libstdc++-v3) work with a new
...@@ -57,7 +65,7 @@ works. It is difficult to test the C++ compiler without a working ...@@ -57,7 +65,7 @@ works. It is difficult to test the C++ compiler without a working
library, but you should at least try some minimal test cases. library, but you should at least try some minimal test cases.
<p>(Note that what we think of as a "target," the library refers to as <p>(Note that what we think of as a "target," the library refers to as
a "host." The comment at the top of <code>configure.in</code> explains why.) a "host." The comment at the top of <code>configure.ac</code> explains why.)
<p>Here are the primary steps required to port the library: <p>Here are the primary steps required to port the library:
...@@ -73,16 +81,16 @@ a "host." The comment at the top of <code>configure.in</code> explains why.) ...@@ -73,16 +81,16 @@ a "host." The comment at the top of <code>configure.in</code> explains why.)
<div class="node"> <div class="node">
<p><hr> <p><hr>
Node:<a name="Operating%20system">Operating system</a>, Node:&nbsp;<a name="Operating%20system">Operating system</a>,
Next:<a rel="next" accesskey="n" href="#CPU">CPU</a>, Next:&nbsp;<a rel="next" accesskey="n" href="#CPU">CPU</a>,
Previous:<a rel="previous" accesskey="p" href="#Top">Top</a>, Previous:&nbsp;<a rel="previous" accesskey="p" href="#Top">Top</a>,
Up:<a rel="up" accesskey="u" href="#Top">Top</a> Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br> <br>
</div> </div>
<h2 class="chapter">Operating system</h2> <h2 class="chapter">Operating system</h2>
<p>If you are porting to a new operating system (as opposed to a new chip <p>If you are porting to a new operating system (as opposed to a new chip
using an existing operating system), you will need to create a new using an existing operating system), you will need to create a new
directory in the <code>config/os</code> hierarchy. For example, the IRIX directory in the <code>config/os</code> hierarchy. For example, the IRIX
configuration files are all in <code>config/os/irix</code>. There is no set configuration files are all in <code>config/os/irix</code>. There is no set
...@@ -191,16 +199,16 @@ starting point. ...@@ -191,16 +199,16 @@ starting point.
<div class="node"> <div class="node">
<p><hr> <p><hr>
Node:<a name="CPU">CPU</a>, Node:&nbsp;<a name="CPU">CPU</a>,
Next:<a rel="next" accesskey="n" href="#Character%20types">Character types</a>, Next:&nbsp;<a rel="next" accesskey="n" href="#Character%20types">Character types</a>,
Previous:<a rel="previous" accesskey="p" href="#Operating%20system">Operating system</a>, Previous:&nbsp;<a rel="previous" accesskey="p" href="#Operating%20system">Operating system</a>,
Up:<a rel="up" accesskey="u" href="#Top">Top</a> Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br> <br>
</div> </div>
<h2 class="chapter">CPU</h2> <h2 class="chapter">CPU</h2>
<p>If you are porting to a new chip (as opposed to a new operating system <p>If you are porting to a new chip (as opposed to a new operating system
running on an existing chip), you will need to create a new directory in the running on an existing chip), you will need to create a new directory in the
<code>config/cpu</code> hierarchy. Much like the <a href="#Operating%20system">Operating system</a> setup, <code>config/cpu</code> hierarchy. Much like the <a href="#Operating%20system">Operating system</a> setup,
there are no strict rules on how to organize the CPU configuration there are no strict rules on how to organize the CPU configuration
...@@ -224,16 +232,16 @@ appropriate for your chip. ...@@ -224,16 +232,16 @@ appropriate for your chip.
<div class="node"> <div class="node">
<p><hr> <p><hr>
Node:<a name="Character%20types">Character types</a>, Node:&nbsp;<a name="Character%20types">Character types</a>,
Next:<a rel="next" accesskey="n" href="#Thread%20safety">Thread safety</a>, Next:&nbsp;<a rel="next" accesskey="n" href="#Thread%20safety">Thread safety</a>,
Previous:<a rel="previous" accesskey="p" href="#CPU">CPU</a>, Previous:&nbsp;<a rel="previous" accesskey="p" href="#CPU">CPU</a>,
Up:<a rel="up" accesskey="u" href="#Top">Top</a> Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br> <br>
</div> </div>
<h2 class="chapter">Character types</h2> <h2 class="chapter">Character types</h2>
<p>The library requires that you provide three header files to implement <p>The library requires that you provide three header files to implement
character classification, analogous to that provided by the C libraries character classification, analogous to that provided by the C libraries
<code>&lt;ctype.h&gt;</code> header. You can model these on the files provided in <code>&lt;ctype.h&gt;</code> header. You can model these on the files provided in
<code>config/os/generic</code>. However, these files will almost <code>config/os/generic</code>. However, these files will almost
...@@ -421,16 +429,16 @@ from <code>__low</code> up until <code>__high</code> into the vector given by ...@@ -421,16 +429,16 @@ from <code>__low</code> up until <code>__high</code> into the vector given by
<div class="node"> <div class="node">
<p><hr> <p><hr>
Node:<a name="Thread%20safety">Thread safety</a>, Node:&nbsp;<a name="Thread%20safety">Thread safety</a>,
Next:<a rel="next" accesskey="n" href="#Numeric%20limits">Numeric limits</a>, Next:&nbsp;<a rel="next" accesskey="n" href="#Numeric%20limits">Numeric limits</a>,
Previous:<a rel="previous" accesskey="p" href="#Character%20types">Character types</a>, Previous:&nbsp;<a rel="previous" accesskey="p" href="#Character%20types">Character types</a>,
Up:<a rel="up" accesskey="u" href="#Top">Top</a> Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br> <br>
</div> </div>
<h2 class="chapter">Thread safety</h2> <h2 class="chapter">Thread safety</h2>
<p>The C++ library string functionality requires a couple of atomic <p>The C++ library string functionality requires a couple of atomic
operations to provide thread-safety. If you don't take any special operations to provide thread-safety. If you don't take any special
action, the library will use stub versions of these functions that are action, the library will use stub versions of these functions that are
not thread-safe. They will work fine, unless your applications are not thread-safe. They will work fine, unless your applications are
...@@ -498,16 +506,16 @@ must be equivalent to those provided here, but using atomic operations: ...@@ -498,16 +506,16 @@ must be equivalent to those provided here, but using atomic operations:
<div class="node"> <div class="node">
<p><hr> <p><hr>
Node:<a name="Numeric%20limits">Numeric limits</a>, Node:&nbsp;<a name="Numeric%20limits">Numeric limits</a>,
Next:<a rel="next" accesskey="n" href="#Libtool">Libtool</a>, Next:&nbsp;<a rel="next" accesskey="n" href="#Libtool">Libtool</a>,
Previous:<a rel="previous" accesskey="p" href="#Thread%20safety">Thread safety</a>, Previous:&nbsp;<a rel="previous" accesskey="p" href="#Thread%20safety">Thread safety</a>,
Up:<a rel="up" accesskey="u" href="#Top">Top</a> Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br> <br>
</div> </div>
<h2 class="chapter">Numeric limits</h2> <h2 class="chapter">Numeric limits</h2>
<p>The C++ library requires information about the fundamental data types, <p>The C++ library requires information about the fundamental data types,
such as the minimum and maximum representable values of each type. such as the minimum and maximum representable values of each type.
You can define each of these values individually, but it is usually You can define each of these values individually, but it is usually
easiest just to indicate how many bits are used in each of the data easiest just to indicate how many bits are used in each of the data
...@@ -523,16 +531,16 @@ your CPU configuration directory (see <a href="#CPU">CPU</a>). ...@@ -523,16 +531,16 @@ your CPU configuration directory (see <a href="#CPU">CPU</a>).
<div class="node"> <div class="node">
<p><hr> <p><hr>
Node:<a name="Libtool">Libtool</a>, Node:&nbsp;<a name="Libtool">Libtool</a>,
Next:<a rel="next" accesskey="n" href="#GNU%20Free%20Documentation%20License">GNU Free Documentation License</a>, Next:&nbsp;<a rel="next" accesskey="n" href="#GNU%20Free%20Documentation%20License">GNU Free Documentation License</a>,
Previous:<a rel="previous" accesskey="p" href="#Numeric%20limits">Numeric limits</a>, Previous:&nbsp;<a rel="previous" accesskey="p" href="#Numeric%20limits">Numeric limits</a>,
Up:<a rel="up" accesskey="u" href="#Top">Top</a> Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br> <br>
</div> </div>
<h2 class="chapter">Libtool</h2> <h2 class="chapter">Libtool</h2>
<p>The C++ library is compiled, archived and linked with libtool. <p>The C++ library is compiled, archived and linked with libtool.
Explaining the full workings of libtool is beyond the scope of this Explaining the full workings of libtool is beyond the scope of this
document, but there are a few, particular bits that are necessary for document, but there are a few, particular bits that are necessary for
porting. porting.
...@@ -561,9 +569,9 @@ operating system. ...@@ -561,9 +569,9 @@ operating system.
<div class="node"> <div class="node">
<p><hr> <p><hr>
Node:<a name="GNU%20Free%20Documentation%20License">GNU Free Documentation License</a>, Node:&nbsp;<a name="GNU%20Free%20Documentation%20License">GNU Free Documentation License</a>,
Previous:<a rel="previous" accesskey="p" href="#Libtool">Libtool</a>, Previous:&nbsp;<a rel="previous" accesskey="p" href="#Libtool">Libtool</a>,
Up:<a rel="up" accesskey="u" href="#Top">Top</a> Up:&nbsp;<a rel="up" accesskey="u" href="#Top">Top</a>
<br> <br>
</div> </div>
...@@ -947,7 +955,7 @@ as a draft) by the Free Software Foundation. ...@@ -947,7 +955,7 @@ as a draft) by the Free Software Foundation.
<h3 class="unnumberedsec">ADDENDUM: How to use this License for your documents</h3> <h3 class="unnumberedsec">ADDENDUM: How to use this License for your documents</h3>
<p>To use this License in a document you have written, include a copy of <p>To use this License in a document you have written, include a copy of
the License in the document and put the following copyright and the License in the document and put the following copyright and
license notices just after the title page: license notices just after the title page:
......
libstdc++-v3/docs/html/17_intro/porting.texi
...@@ -75,7 +75,7 @@ works. It is difficult to test the C++ compiler without a working ...@@ -75,7 +75,7 @@ works. It is difficult to test the C++ compiler without a working
library, but you should at least try some minimal test cases. library, but you should at least try some minimal test cases.
(Note that what we think of as a ``target,'' the library refers to as (Note that what we think of as a ``target,'' the library refers to as
a ``host.'' The comment at the top of @file{configure.in} explains why.) a ``host.'' The comment at the top of @file{configure.ac} explains why.)
Here are the primary steps required to port the library: Here are the primary steps required to port the library:
......
libstdc++-v3/include/Makefile.in
...@@ -576,7 +576,7 @@ DIST_COMMON = Makefile.am Makefile.in ...@@ -576,7 +576,7 @@ DIST_COMMON = Makefile.am Makefile.in
all: all-am all: all-am
.SUFFIXES: .SUFFIXES:
$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.in $(ACLOCAL_M4) $(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.ac $(ACLOCAL_M4)
cd $(top_srcdir) && \ cd $(top_srcdir) && \
$(AUTOMAKE) --foreign include/Makefile $(AUTOMAKE) --foreign include/Makefile
Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status
......
libstdc++-v3/libmath/Makefile.in
...@@ -248,7 +248,7 @@ all: all-am ...@@ -248,7 +248,7 @@ all: all-am
.SUFFIXES: .SUFFIXES:
.SUFFIXES: .c .lo .o .obj .SUFFIXES: .c .lo .o .obj
$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.in $(ACLOCAL_M4) $(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.ac $(ACLOCAL_M4)
cd $(top_srcdir) && \ cd $(top_srcdir) && \
$(AUTOMAKE) --foreign libmath/Makefile $(AUTOMAKE) --foreign libmath/Makefile
Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status
......
libstdc++-v3/libsupc++/Makefile.in
...@@ -372,7 +372,7 @@ all: all-am ...@@ -372,7 +372,7 @@ all: all-am
.SUFFIXES: .SUFFIXES:
.SUFFIXES: .cc .lo .o .obj .SUFFIXES: .cc .lo .o .obj
$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.in $(ACLOCAL_M4) $(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.ac $(ACLOCAL_M4)
cd $(top_srcdir) && \ cd $(top_srcdir) && \
$(AUTOMAKE) --foreign libsupc++/Makefile $(AUTOMAKE) --foreign libsupc++/Makefile
Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status
......
libstdc++-v3/po/Makefile.in
...@@ -237,7 +237,7 @@ all: all-am ...@@ -237,7 +237,7 @@ all: all-am
.SUFFIXES: .SUFFIXES:
.SUFFIXES: .po .mo .SUFFIXES: .po .mo
$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.in $(ACLOCAL_M4) $(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.ac $(ACLOCAL_M4)
cd $(top_srcdir) && \ cd $(top_srcdir) && \
$(AUTOMAKE) --foreign po/Makefile $(AUTOMAKE) --foreign po/Makefile
Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status
......
libstdc++-v3/src/Makefile.in
...@@ -391,7 +391,7 @@ all: all-am ...@@ -391,7 +391,7 @@ all: all-am
.SUFFIXES: .SUFFIXES:
.SUFFIXES: .cc .lo .o .obj .SUFFIXES: .cc .lo .o .obj
$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.in $(ACLOCAL_M4) $(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.ac $(ACLOCAL_M4)
cd $(top_srcdir) && \ cd $(top_srcdir) && \
$(AUTOMAKE) --foreign src/Makefile $(AUTOMAKE) --foreign src/Makefile
Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status
......
libstdc++-v3/testsuite/Makefile.in
...@@ -297,7 +297,7 @@ all: all-am ...@@ -297,7 +297,7 @@ all: all-am
.SUFFIXES: .SUFFIXES:
.SUFFIXES: .cc .lo .o .obj .SUFFIXES: .cc .lo .o .obj
$(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.in $(ACLOCAL_M4) $(srcdir)/Makefile.in: @MAINTAINER_MODE_TRUE@ Makefile.am $(top_srcdir)/configure.ac $(ACLOCAL_M4)
cd $(top_srcdir) && \ cd $(top_srcdir) && \
$(AUTOMAKE) --foreign testsuite/Makefile $(AUTOMAKE) --foreign testsuite/Makefile
Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status Makefile: @MAINTAINER_MODE_TRUE@ $(srcdir)/Makefile.in $(top_builddir)/config.status
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment