All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: "Adrien Gallouët" <adrien@gallouet.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/bird: fix build with autoconf >= 2.70
Date: Tue, 28 Dec 2021 15:24:11 +0100	[thread overview]
Message-ID: <20211228152411.5a0519e3@windsurf> (raw)
In-Reply-To: <20211228152059.78f64362@windsurf>

On Tue, 28 Dec 2021 15:20:59 +0100
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:

> I fail to understand why adding -g would cause that build failure.
> There is already -g0 in the command line, then -g, which enables
> debugging symbols, this shouldn't cause any build failure.
> 
> Perhaps the issue is more related to the addition of -flto=4, which
> enables link-time optimization?
> 
> But even then, I don't quite understand this ac_test_CFLAGS stuff. Do
> you understand why their configure.ac script is doing:
> 
> # Store this value because ac_test_CFLAGS is overwritten by AC_PROG_CC
> if test "$ac_test_CFLAGS" != set ; then
>   bird_cflags_default=yes
> fi
> 
> in the first place?
> 
> Could you help me connect the dots here ?

Also, I thought we had already fixed this issue with
https://git.buildroot.org/buildroot/commit/package/bird?id=03c148c8dec4e8c3fa13fcde4a730b3ab97f3f10 ?

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2021-12-28 14:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05 20:12 [Buildroot] [PATCH 1/1] package/bird: fix build with autoconf >= 2.70 Fabrice Fontaine
2021-11-09 22:16 ` Arnout Vandecappelle
2021-11-09 22:30   ` Fabrice Fontaine
2021-12-28 14:20 ` Thomas Petazzoni
2021-12-28 14:24   ` Thomas Petazzoni [this message]
2022-07-25 19:28 ` Arnout Vandecappelle
2022-08-18  5:55   ` Peter Korsgaard

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=20211228152411.5a0519e3@windsurf \
    --to=thomas.petazzoni@bootlin.com \
    --cc=adrien@gallouet.fr \
    --cc=buildroot@buildroot.org \
    --cc=fontaine.fabrice@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.