From: Jason R Thorpe <thorpej@wasabisystems.com>
To: binutils@sources.redhat.com
Subject: [PATCH] Missed file in gmon_io commit
Date: Thu, 31 Jan 2002 12:22:00 -0000 [thread overview]
Message-ID: <20020131112042.J21777@dr-evil.shagadelic.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
Nick missed this when he committed my gprof gmon_io patch (gconfig.in
needs to be regenerated by running `autoheader'). ChangeLog entry
omitted, since it's already listed in the ChangeLog entry for my gprof
patch.
Committed as obvious.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
[-- Attachment #2: gconfig.in-patch --]
[-- Type: text/plain, Size: 562 bytes --]
Index: gconfig.in
===================================================================
RCS file: /cvs/src/src/gprof/gconfig.in,v
retrieving revision 1.6
diff -c -r1.6 gconfig.in
*** gconfig.in 2001/03/14 03:14:56 1.6
--- gconfig.in 2002/01/31 19:17:16
***************
*** 40,48 ****
/* Define if you have the ANSI C header files. */
#undef STDC_HEADERS
- /* Define as the size of a pointer in the target profile file format. */
- #undef GMON_PTR_SIZE
-
/* Define if you have the __argz_count function. */
#undef HAVE___ARGZ_COUNT
--- 40,45 ----
reply other threads:[~2002-01-31 19:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020131112042.J21777@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=binutils@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).