netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ido Schimmel <idosch@idosch.org>
To: David Ahern <dsahern@kernel.org>
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: [PATCH iproute2-next] configure: Allow command line override of toolchain
Date: Tue, 8 Mar 2022 18:41:56 +0200	[thread overview]
Message-ID: <YieHVALfKnVbqYru@shredder> (raw)
In-Reply-To: <8882d949-35bb-8fad-c047-92fb5091c33b@kernel.org>

On Tue, Mar 08, 2022 at 09:26:49AM -0700, David Ahern wrote:
> On 3/7/22 8:09 AM, Ido Schimmel wrote:
> > 
> > I realize it was already merged (wasn't asking for academic purposes),
> > but rather wanted you to verify that the patch is not needed on your end
> > so that I could revert it. I can build with gcc/clang even without the
> > patch. With the patch, the build is broken on Fedora as "yacc" is not a
> > build dependency [1]. Verified this with a clean install of Fedora 35:
> > Can't build iproute with this patch after running "dnf builddep
> > iproute". Builds fine without it.
> > 
> > [1] https://src.fedoraproject.org/rpms/iproute/blob/rawhide/f/iproute.spec#_22
> 
> I booted a Fedora 35 VM and see what you mean. I can not find the
> difference as to why Ubuntu 20.04 is ok and Fedora 35 is not, so I
> reverted the patch.

I tested with Ubuntu 21.10 yesterday and it worked for me as well.
There 'yacc' eventually points to '/usr/bin/bison.yacc'.

Anyway, thanks for taking care of that

      reply	other threads:[~2022-03-08 16:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  1:54 [PATCH iproute2-next] configure: Allow command line override of toolchain David Ahern
2022-02-28 17:11 ` Stephen Hemminger
2022-02-28 17:50 ` patchwork-bot+netdevbpf
2022-03-02 13:56 ` Ido Schimmel
2022-03-05 18:11   ` David Ahern
2022-03-05 19:32     ` Stephen Hemminger
2022-03-07 15:09     ` Ido Schimmel
2022-03-08 16:26       ` David Ahern
2022-03-08 16:41         ` Ido Schimmel [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=YieHVALfKnVbqYru@shredder \
    --to=idosch@idosch.org \
    --cc=dsahern@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /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;
as well as URLs for NNTP newsgroup(s).