mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
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 11:00:32 +0000	[thread overview]
Message-ID: <916A03CCEB30DF44AD98D4CFDC7448D0577FADCD@nooslzsmx1.zenitelcss.com> (raw)
In-Reply-To: <20150720093624.GM26620@pengutronix.de>

All clear now, thanks for the explanation Michael.
 
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: ptxdist [mailto:ptxdist-bounces@pengutronix.de] On Behalf Of Olbrich Michael
Sent: Monday, July 20, 2015 11:36 AM
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Building root-debug without any optimisation

Hi,

On Mon, Jul 20, 2015 at 10:52:11AM +0200, Juergen Borleis wrote:
> On Monday 20 July 2015 10:25:03 Alan Martinović wrote:
> > 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".
> 
> Hmm, Michael should know the answer... :)

I can only tell you why this doesn't work. The "Extra CFLAGS" are _not_ used to set the CFLAGS environment variable. We use wrapper scripts for the compiler and basically fake different defaults. The configure script will never see the options you set here. Anything else doesn't work reliably.
Some packages ignore the specified CFLAGS, other always add '-g -O2' etc.

There is currently no way to force a different optimization level globally.
We have it for debugging (PTXCONF_TARGET_DEBUG_*). You'll need to hack ptxdist to do the same for optimization.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

--
ptxdist mailing list
ptxdist@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

      reply	other threads:[~2015-07-20  9:01 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ć
2015-07-20  8:52       ` Juergen Borleis
2015-07-20  9:36         ` Olbrich Michael
2015-07-20 11:00           ` Alan Martinović [this message]

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=916A03CCEB30DF44AD98D4CFDC7448D0577FADCD@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