mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [RFC PATCH 0/1] ppp: version bump 2.4.7 -> 2.4.9
Date: Wed, 16 Jun 2021 15:53:02 +0200	[thread overview]
Message-ID: <YMoCPsE2z92o/79z@ada-deb-carambola.ifak-system.com> (raw)
In-Reply-To: <20210616130031.GK22020@pengutronix.de>

Hi,

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.

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.

Greets
Alex


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


  reply	other threads:[~2021-06-16 13:53 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 [this message]
2021-06-17  6:39         ` Michael Olbrich

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=YMoCPsE2z92o/79z@ada-deb-carambola.ifak-system.com \
    --to=ada@thorsis.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