From: David Lecomber <david@allinea.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: patches <gdb-patches@sources.redhat.com>
Subject: Re: [COMMIT] Obvious - compilation failure in proc-api.c
Date: Thu, 10 Mar 2005 00:02:00 -0000 [thread overview]
Message-ID: <1110413377.8084.40.camel@cpc2-oxfd5-5-0-cust103.oxfd.cable.ntl.com> (raw)
In-Reply-To: <20050309234126.GA5799@nevyn.them.org>
On Wed, 2005-03-09 at 18:41 -0500, Daniel Jacobowitz wrote:
> On Wed, Mar 09, 2005 at 11:45:05PM +0000, David Lecomber wrote:
> > 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!)
>
> What was the error? The style appears to be the same as the one Andrew
> used all across GDB when he mass-converted.
>
> (Yes, I think it's ugly.)
Well, it's only been that file that has complained, but the error was
pretty straight forward:
/opt/SUNWspro/bin/cc -c -xtarget=opteron -xarch=amd64 -I. -I.././gdb
-I.././gdb/config -DLOCALEDIR="\"/usr/local/share/locale\""
-DHAVE_CONFIG_H -I.././gdb/../include/opcode -I.././gdb/../readline/..
-I../bfd -I.././gdb/../bfd -I.././gdb/../include -I../intl
-I.././gdb/../intl -DMI_OUT=1 proc-api.c
"proc-api.c", line 783: newline in string literal
"proc-api.c", line 786: syntax error before or at: set_procfs_trace_cmd
"proc-api.c", line 796: cannot recover from previous errors
cc: acomp failed for proc-api.c
make[1]: *** [proc-api.o] Error 2
make[1]: Leaving directory
`/home/david/Sun/64bit/gdb-6.3.50.20050304/gdb'
make: *** [all-gdb] Error 2
d.
--
David Lecomber <david@allinea.com>
next prev parent reply other threads:[~2005-03-10 0:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 23:37 David Lecomber
2005-03-09 23:41 ` Daniel Jacobowitz
2005-03-10 0:02 ` David Lecomber [this message]
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=1110413377.8084.40.camel@cpc2-oxfd5-5-0-cust103.oxfd.cable.ntl.com \
--to=david@allinea.com \
--cc=drow@false.org \
--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