Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@allinea.com>
To: patches <gdb-patches@sources.redhat.com>
Subject: [COMMIT] Obvious - compilation failure in proc-api.c
Date: Wed, 09 Mar 2005 23:37:00 -0000	[thread overview]
Message-ID: <1110411905.8084.34.camel@cpc2-oxfd5-5-0-cust103.oxfd.cable.ntl.com> (raw)

Dear all,

It's been a while since I committed something, but here's one for the
obvious fix rule.   Someone prod me if I forgot to do something ;-)  

The old version failed to compile with Sun's Forte tools on Solaris 10
for Opteron (and you should've seen the code formatting!) 

Regards
David

2005-03-09  David Lecomber  <david@lecomber.net>
 
        * proc-api.c (_initialize_proc_api): Fix invalid multi-line
        i18n text.


Index: proc-api.c
===================================================================
RCS file: /cvs/src/src/gdb/proc-api.c,v
retrieving revision 1.22
retrieving revision 1.23
diff -c -p -r1.22 -r1.23
*** proc-api.c  18 Feb 2005 15:25:27 -0000      1.22
--- proc-api.c  9 Mar 2005 23:33:52 -0000       1.23
*************** _initialize_proc_api (void)
*** 780,795 ****
  {
    struct cmd_list_element *c;
   
!   add_setshow_boolean_cmd ("procfs-trace", no_class, &procfs_trace,
_("\
! Set tracing for /proc api calls."), _("\
! Show tracing for /proc api calls."), NULL,
                           set_procfs_trace_cmd,
                           NULL, /* FIXME: i18n: */
                           &setlist, &showlist);
   
!   add_setshow_filename_cmd ("procfs-file", no_class, &procfs_filename,
_("\
! Set filename for /proc tracefile."), _("\
! Show filename for /proc tracefile."), NULL,
                            set_procfs_file_cmd,
                            NULL, /* FIXME: i18n: */
                            &setlist, &showlist);
--- 780,795 ----
  {
    struct cmd_list_element *c;
   
!   add_setshow_boolean_cmd ("procfs-trace", no_class, &procfs_trace,
!                          _("Set tracing for /proc api calls."),
!                          _("Show tracing for /proc api calls."), NULL,
                           set_procfs_trace_cmd,
                           NULL, /* FIXME: i18n: */
                           &setlist, &showlist);
   
!   add_setshow_filename_cmd ("procfs-file", no_class, &procfs_filename,
!                           _("Set filename for /proc tracefile."),
!                           _("Show filename for /proc tracefile."),
NULL,
                            set_procfs_file_cmd,
                            NULL, /* FIXME: i18n: */
                            &setlist, &showlist);

-- 
David Lecomber <david@allinea.com>


             reply	other threads:[~2005-03-09 23:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 23:37 David Lecomber [this message]
2005-03-09 23:41 ` Daniel Jacobowitz
2005-03-10  0:02   ` David Lecomber
2005-03-10  1:01     ` Daniel Jacobowitz
2005-03-10  9:17       ` Mark Kettenis

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=1110411905.8084.34.camel@cpc2-oxfd5-5-0-cust103.oxfd.cable.ntl.com \
    --to=david@allinea.com \
    --cc=gdb-patches@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