From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [SECURITY][PATCHv2] Bump quagga to 0.99.17
Date: Thu, 30 Sep 2010 21:16:15 +0200 [thread overview]
Message-ID: <87ocbfxcsg.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4CA4A278.6040303@zacarias.com.ar> (Gustavo Zacarias's message of "Thu, 30 Sep 2010 11:45:12 -0300")
>>>>> "Gustavo" == Gustavo Zacarias <gustavo@zacarias.com.ar> writes:
Gustavo> Bump quagga to version 0.99.17.
Gustavo> [SECURITY] Fixes remote crash in bgpd.
Gustavo> Other fixes for ospfd, ospf6d, zebra and isisd.
Gustavo> Fix conflicting options in the package, enhance help, reorder options.
Gustavo> Should fix most breakage with randpackageconfig (Peter: ring me if you
Gustavo> hit another one!).
With this I still have the same bug:
make[3]: *** No rule to make target `../ospfd/libospf.la', needed by `ospfclient
grep QUAGGA .config
BR2_PACKAGE_QUAGGA=y
# BR2_PACKAGE_QUAGGA_ZEBRA is not set
# BR2_PACKAGE_QUAGGA_BGPD is not set
# BR2_PACKAGE_QUAGGA_RIPD is not set
# BR2_PACKAGE_QUAGGA_OSPFD is not set
# BR2_PACKAGE_QUAGGA_WATCHQUAGGA is not set
# BR2_PACKAGE_QUAGGA_ISISD is not set
# BR2_PACKAGE_QUAGGA_BGP_ANNOUNCE is not set
# BR2_PACKAGE_QUAGGA_NETLINK is not set
# BR2_PACKAGE_QUAGGA_SNMP is not set
BR2_PACKAGE_QUAGGA_TCP_ZEBRA=y
BR2_PACKAGE_QUAGGA_OPAGUE_LSA=y
I also see that you removed the comment about snmp support being broken
with external toolchains. Is that resolved?
And finally, how do you create your patches? Could you please use git
format-patch for it, so I can apply them with git am?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2010-09-30 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-30 14:45 [Buildroot] [SECURITY][PATCHv2] Bump quagga to 0.99.17 Gustavo Zacarias
2010-09-30 19:16 ` Peter Korsgaard [this message]
2010-09-30 19:26 ` Gustavo Zacarias
2010-09-30 19:29 ` Gustavo Zacarias
2010-09-30 19:47 ` Peter Korsgaard
2010-09-30 21:47 ` Thomas Petazzoni
2010-10-01 8:31 ` Peter Korsgaard
2010-10-01 13:41 ` Gustavo Zacarias
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=87ocbfxcsg.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 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.