Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] open-lldp: new package
Date: Fri, 12 Jan 2018 22:04:36 +0100	[thread overview]
Message-ID: <20180112220436.677e3084@windsurf.lan> (raw)
In-Reply-To: <CAGm1_kvL9UWVX5jrzE1dhsOHvWT_LukRJKZ5z6eu8Tma0bjXdw@mail.gmail.com>

Hello,

On Fri, 12 Jan 2018 15:46:14 +0100, Yegor Yefremov wrote:

> > +# Run the bootstrap.sh command.
> > +# (from the 'lldpad Application Install' section of the README file)
> > +define OPEN_LLDP_BOOTSTRAP
> > +       (cd $(@D) && ./bootstrap.sh)
> > +endef  
> 
> m4 folder is missing. It is worth sending a patch upstream (open-lldp)
> to fix this. As long as you have this hook, you don't need
> OPEN_LLDP_AUTORECONF = YES, because boostrap.sh already invokes
> "autoreconf -i". At least thy this.

No, I disagree here. If you drop <pkg>_AUTORECONF = YES, then you loose
the dependency on host-autoconf, host-automake and host-libtool.

So instead, please keep <pkg>_AUTORECONF = YES, and if the missing m4
folder is the only problem (but I doubt it because the bootstrap.sh
script doesn't create it), then add a post-extract hook that creates
the m4 file.

> The package doesn't build:
> 
> In file included from lldpad.c:58:0:
> ./include/lldp_8021qaz.h:237:12: error: inline function
> ?ieee8021qaz_clif_cmd? declared but never defined [-Werror]
>  inline int ieee8021qaz_clif_cmd(void *data, struct sockaddr_un *from,
>             ^~~~~~~~~~~~~~~~~~~~
> ./include/lldp_8021qaz.h:222:13: error: inline function ?set_prio_map?
> declared but never defined [-Werror]
>  inline void set_prio_map(u32 *prio_map, u8 prio, int tc);
>              ^~~~~~~~~~~~
> ./include/lldp_8021qaz.h:221:12: error: inline function ?get_prio_map?
> declared but never defined [-Werror]
>  inline int get_prio_map(u32 prio_map, int tc);
>             ^~~~~~~~~~~~

Perhaps you could tell Laurent which configuration you've used to
produce this build failure, so that he can reproduce it.

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2018-01-12 21:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-12 14:01 [Buildroot] [PATCH 1/1] open-lldp: new package Laurent Charpentier
2018-01-12 14:46 ` Yegor Yefremov
2018-01-12 21:04   ` Thomas Petazzoni [this message]
2018-01-12 21:29     ` Yegor Yefremov
2018-01-12 22:38       ` Thomas Petazzoni
2018-01-15 12:50         ` Laurent Charpentier
2018-01-15 13:47           ` Thomas Petazzoni
2018-01-15 14:52           ` Yegor Yefremov
2018-01-15 15:15             ` Laurent Charpentier
2018-01-15 15:21               ` Yegor Yefremov
2018-01-15 15:40                 ` Thomas Petazzoni
2018-01-16  8:22         ` Yegor Yefremov
  -- strict thread matches above, loose matches on Subject: below --
2018-01-12 11:00 [Buildroot] [PATCH 1/1] Added lldpad (LLDP Agent Daemon) package Laurent Charpentier
2018-01-12 11:00 ` [Buildroot] [PATCH 1/1] open-lldp: new package Laurent Charpentier
2018-01-12 11:05   ` Thomas Petazzoni

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=20180112220436.677e3084@windsurf.lan \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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