From: Jim Wilson <wilson@specifix.com>
To: "Azer, William" <Bill.Azer@drs-ss.com>
Cc: linux-mips@linux-mips.org
Subject: Re: oprofile configure?
Date: Wed, 27 Sep 2006 14:49:18 -0700 [thread overview]
Message-ID: <1159393758.3181.26.camel@localhost.localdomain> (raw)
In-Reply-To: <DEB94D90ABFC8240851346CFD4ACFF149E1C7F@gamd-ex-001.ss.drs.master>
On Tue, 2006-09-26 at 10:34 -0400, Azer, William wrote:
> i have natively built oprofile for sb1 platform and i get a lot of
> warnings from the compiler. i had to use --disable-werror in order to
> build. has anyone encountered this? am i doing something wrong?
You didn't mention the oprofile version, the gcc version, or the kernel
version, which are the important bits here. I can see from the error
messages that you have gcc-3.4.3, and a montavista kernel.
>
I tried oprofile-0.9.2. I was unable to get -Werror used in the
compiler. Looking at the configure script, I see that -Werror is
disabled unless you have a snapshot from the cvs tree. Not even
--enable-werror can turn it on. I'm guessing that you are using the cvs
tree.
This looks like a bug in the gcc that you are using. I can't reproduce
it on other systems, but I can reproduce it on a similar MontaVista
system. I can't reproduce it with later FSF gcc releases on the same
MontaVista system. It isn't immediately obvious what changed to fix
this.
--
Jim Wilson, GNU Tools Support, http://www.specifix.com
next prev parent reply other threads:[~2006-09-27 21:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 14:34 oprofile configure? Azer, William
2006-09-26 14:34 ` Azer, William
2006-09-27 21:49 ` Jim Wilson [this message]
2006-09-27 22:05 ` Azer, William
2006-09-27 22:05 ` Azer, William
2006-09-27 22:15 ` Jim Wilson
2006-09-28 14:53 ` Ralf Baechle
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=1159393758.3181.26.camel@localhost.localdomain \
--to=wilson@specifix.com \
--cc=Bill.Azer@drs-ss.com \
--cc=linux-mips@linux-mips.org \
/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