From: "wcohen at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/3037] FC6: Including config.h is deprecated.
Date: Mon, 14 Aug 2006 14:45:00 -0000 [thread overview]
Message-ID: <20060814144455.24012.qmail@sourceware.org> (raw)
In-Reply-To: <20060811202851.3037.wcohen@redhat.com>
------- Additional Comments From wcohen at redhat dot com 2006-08-14 14:44 -------
Did not see anything being used from linux/configh.h. Removed the "#include
<linux/config.h>" from print.c and string.c.
Running to verify that this eliminates the problem on fc6 and does not cause
problems on rhel4 or fc5.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
Summary| FC6: Including config.h is |FC6: Including config.h is
|deprecated. |deprecated.
http://sourceware.org/bugzilla/show_bug.cgi?id=3037
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2006-08-14 14:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 20:29 [Bug runtime/3037] New: " wcohen at redhat dot com
2006-08-14 14:45 ` wcohen at redhat dot com [this message]
2007-05-08 18:55 ` [Bug runtime/3037] " fche at redhat dot com
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=20060814144455.24012.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).