All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 1489] New: radvd update to 1.6
Date: Sun,  4 Apr 2010 19:26:55 +0000 (UTC)	[thread overview]
Message-ID: <bug-1489-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=1489

           Summary: radvd update to 1.6
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: alex at digriz.org.uk
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=1477)
 --> (https://bugs.busybox.net/attachment.cgi?id=1477)
update radvd package information

As well as updating the version of radvd that is pulled down (from 1.5 to 1.6)
I also removed the unneeded cruft from radvd.mk (just reflects the defaults)
and since version 1.5 radvd is fixed for parallel building so $(MAKE1) is no
longer needed.

I also updated Config.in to also reflect it's dependency on
BR2_PACKAGE_FLEX_LIBFL (similarly to how gob2/ipsec-tools does).


-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

             reply	other threads:[~2010-04-04 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 19:26 bugzilla at busybox.net [this message]
2010-04-06  5:44 ` [Buildroot] [Bug 1489] radvd update to 1.6 bugzilla at busybox.net

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=bug-1489-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --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.