Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 109] New: Make pppd package avoid bsd err
Date: Tue, 17 Feb 2009 11:26:06 +0000 (UTC)	[thread overview]
Message-ID: <bug-109-163@https.bugs.busybox.net/> (raw)

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

              Host: i686-linux
            Target: arm-softfloat-linux-uclibcgnueabi
           Summary: Make pppd package avoid bsd err
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P5
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: gustavo at zacarias.com.ar
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=67)
 --> (https://bugs.busybox.net/attachment.cgi?id=67)
Nuke bsd err usage in pppd and PPPD_CAT in mk file

The pppd package uses bsd err (which is an option in uclibc) in just two lines
of code in the pppoe plugin.
The rest of the package uses syslog, so avoid bsd err since the plugin silently
fails to build and get installed if uclibc is built without bsd err support.
Also why does pppd.mk use PPPD_CAT instead of ZCAT? The patch nukes that
duplication too (maybe there's a reason but it seems unlikely).


-- 
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:[~2009-02-17 11:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17 11:26 bugzilla at busybox.net [this message]
2009-02-19 12:09 ` [Buildroot] [Bug 109] Make pppd package avoid bsd err 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-109-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox