mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC PATCH 0/1] ppp: version bump 2.4.7 -> 2.4.9
Date: Thu, 17 Jun 2021 08:39:37 +0200	[thread overview]
Message-ID: <20210617063936.GP839947@pengutronix.de> (raw)
In-Reply-To: <YMoCPsE2z92o/79z@ada-deb-carambola.ifak-system.com>

On Wed, Jun 16, 2021 at 03:53:02PM +0200, Alexander Dahl wrote:
> Am Wed, Jun 16, 2021 at 03:00:31PM +0200 schrieb Michael Olbrich:
> > On Wed, Jun 16, 2021 at 02:22:01PM +0200, Alexander Dahl wrote:
> > > What I need is something containing the CFLAGS already set by ptxdist
> > > through various variables (like platform hardening options) to pass it
> > > on to the handcrafted ./configure which does not consider the CFLAGS
> > > environment variable.
> > 
> > Why do you need to pass those to the configure script? All CFLAGS will be
> > automatically added when the compiler is called. Or is there some code in
> > the configure script that scans the CFLAGS manually?
> 
> Oh okay. So the compiler wrapper handles this? That was a lack of
> knowledge on my site then.

Yes, any CFLAGS from PTXdist will seem like compiler defaults to the
configure script etc.

> I was just confused, because if you build ppp by yourself without
> ptxdist, you have to call `./configure --cflags="WHATEVERCFLAGS"` to
> have ppp's configure do the right thing.

There are a lot of packages out there with various ways to specify the
CFLAGS and sometimes surprising side effects. To avoid all this we have the
wrappers and add all the flags there.

Michael


-- 
Pengutronix e.K.                           |                             |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de


      reply	other threads:[~2021-06-17  6:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 14:47 Alexander Dahl
2021-06-14 14:47 ` [ptxdist] [RFC PATCH 1/1] " Alexander Dahl
2021-06-15  9:26 ` [ptxdist] [RFC PATCH 0/1] " Alexander Dahl
2021-06-16 11:53 ` Michael Olbrich
2021-06-16 12:22   ` Alexander Dahl
2021-06-16 13:00     ` Michael Olbrich
2021-06-16 13:53       ` Alexander Dahl
2021-06-17  6:39         ` Michael Olbrich [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=20210617063936.GP839947@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --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