From: "Alan Martinović" <Alan.Martinovic@zenitel.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] Building root-debug without any optimisation
Date: Mon, 20 Jul 2015 08:25:03 +0000 [thread overview]
Message-ID: <916A03CCEB30DF44AD98D4CFDC7448D0577FAD77@nooslzsmx1.zenitelcss.com> (raw)
In-Reply-To: <201507201006.03127.jbe@pengutronix.de>
Hey Juergen,
thanks for the warning, I'll keep that in mind.
I seem to be doing something wrong.
In platformconfig->architecture->extra toolchain options I've set:
debugging (enabled (full) )
(-g) Extra CPPFLAGS (cpp)
(-g) Extra CFLAGS (c)
(-g) Extra CXXFLAGS (c++)
After which I did a clean and targetinstall for the desired package.
However, the compilation is still run with "-g -02".
ALAN MARTINOVIC
DEVELOPMENT ENGINEER
ZENITEL NORWAY AS
Tel: +385 97 746 6662
alan.martinovic@zenitel.com
ZENITEL MARINE MED. OFFICE
PERMANI 28, HR-HR-51213 Jurdani, Croatia
Switchboard: +385 97 746 6662, Fax: +385 51 292 555
www.zenitel.com
-----Original Message-----
From: Juergen Borleis [mailto:jbe@pengutronix.de]
Sent: Monday, July 20, 2015 10:06 AM
To: ptxdist@pengutronix.de
Cc: Alan Martinović
Subject: Re: [ptxdist] Building root-debug without any optimisation
Hi Alan,
On Monday 20 July 2015 09:49:32 myself wrote:
> On Monday 20 July 2015 09:37:00 Alan Martinović wrote:
> > I've noticed that the open source apps built with automake have
> > default compile flags "-g -O2". I would like to get a optimization
> > free root-debug build with debug symbols. I can replace all
> > occurrences of "-g -O2" with "-g" in configure files but would like
> > to hear comments if there is a better way of doing this. For example.
> > Passing a global CFLAGS="-g" to all ./configure scripts?
>
> Yes, passing CFLAGS to all configure scripts will disable the
> automatic addition of the "-O2". You could also try to add "-g -O0",
> but sometimes packages tend to fail to build with the "O0" setting.
> And for best debugging you should disable builtins and inlining as well.
Ahh, one additional thing: CFLAGS will also be effective in the non-debug root filesystem...
Regards,
Juergen
--
Pengutronix e.K. | Juergen Borleis | Industrial Linux Solutions | http://www.pengutronix.de/ |
DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-07-20 8:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 7:37 Alan Martinović
2015-07-20 7:49 ` Juergen Borleis
2015-07-20 8:06 ` Juergen Borleis
2015-07-20 8:25 ` Alan Martinović [this message]
2015-07-20 8:52 ` Juergen Borleis
2015-07-20 9:36 ` Olbrich Michael
2015-07-20 11:00 ` Alan Martinović
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=916A03CCEB30DF44AD98D4CFDC7448D0577FAD77@nooslzsmx1.zenitelcss.com \
--to=alan.martinovic@zenitel.com \
--cc=ptxdist@pengutronix.de \
/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