OpenE2K
/
gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

acinclude.m4 (enable_cshadow_headers): Change CSHADOWFLAGS to _GNU_SOURCE instead of _ISOC9X_SOURCE... 

2000-06-13  Benjamin Kosnik  <bkoz@redhat.com>

       	* acinclude.m4 (enable_cshadow_headers): Change CSHADOWFLAGS to
	_GNU_SOURCE instead of _ISOC9X_SOURCE, as _GNU_SOURCE is the
	superset, and already defined at top level.
        * aclocal.m4: Regenerate.
        * configure: Regenerate.

	* docs/17_intro/contribute.html: Plead with people to use -cp.

From-SVN: r34538
This commit is contained in:
Benjamin Kosnik 2000-06-14 00:12:42 +00:00
parent e95706d5d2
commit cc12edec9b
2 changed files with 34 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
libstdc++-v3/ChangeLog
View File

@ -1,3 +1,19 @@
2000-06-13 Steven King <sxking@uswest.net>
* acinclude.m4: Fixup some of the builtin math tests and add tests for
__builtin_fmod* and test libm for fmodf, fmodl or _fmodf, _fmodl.
* acconfig.h: Add entries for fmod*.
2000-06-13 Benjamin Kosnik <bkoz@redhat.com>
* acinclude.m4 (enable_cshadow_headers): Change CSHADOWFLAGS to
_GNU_SOURCE instead of _ISOC9X_SOURCE, as _GNU_SOURCE is the
superset, and already defined at top level.
* aclocal.m4: Regenerate.
* configure: Regenerate.
* docs/17_intro/contribute.html: Plead with people to use -cp.
2000-06-13 Anthony Williams <anthony@anthonyw.cjb.net>
* testsuite/23_containers/bitset_ctor.cc: Qualify reverse wth std::.

23
libstdc++-v3/docs/17_intro/contribute.html
View File

@ -62,11 +62,24 @@ properly evaluated. Ideally (and to ensure the fastest possible
response from the maintainers) it would have all of these pieces:
<p>
<ul>
<li> A description of the bug and how your patch fixes this bug. For new features a description of the feature and your implementation.
<li> A ChangeLog entry as plaintext; see the various ChangeLog files for format and content. If using you are using emacs as your editor, simply position the insertion point at the beginning of your change and hit CX-4a to bring up the appropriate ChangeLog entry. See--magic! Similar functionality also exists for vi.
<li> A testsuite submission or sample program that will easily and simply show the existing error or test new functionality.
<li> The patch itself. If you are accessing the CVS repository at Cygnus, use "cvs update; cvs diff -c3p NEW"; else, use
"diff -c3p OLD NEW" or "diff -up OLD NEW". If your version of diff does not support these options, then get the latest version of GNU diff.
<li> A description of the bug and how your patch fixes this bug. For
new features a description of the feature and your implementation.
<li> A ChangeLog entry as plaintext; see the various ChangeLog files
for format and content. If using you are using emacs as your editor,
simply position the insertion point at the beginning of your change
and hit CX-4a to bring up the appropriate ChangeLog
entry. See--magic! Similar functionality also exists for vi.
<li> A testsuite submission or sample program that will easily and
simply show the existing error or test new functionality.
<li> The patch itself. If you are accessing the CVS repository at
Cygnus, use "cvs update; cvs diff -c3p NEW"; else, use "diff -c3p OLD
NEW" ... If your version of diff does not support these options, then
get the latest version of GNU diff.
<li> When you have all these pieces, bundle them up in a mail message
and send it to libstdc++@sourceware.cygnus.com. All patches and related
discussion should be sent to the libstdc++ mailinglist.