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 285] New: compilation of samba fails if IPV6 support is missing
Date: Fri, 17 Apr 2009 17:43:19 +0000 (UTC)	[thread overview]
Message-ID: <bug-285-163@https.bugs.busybox.net/> (raw)

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

           Summary: compilation of samba fails if IPV6 support is missing
           Product: buildroot
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Other
        AssignedTo: unassigned at buildroot.uclibc.org
        ReportedBy: s.neumann at phase-zero.de
                CC: buildroot at uclibc.org
   Estimated Hours: 0.0


Created an attachment (id=243)
 --> (https://bugs.busybox.net/attachment.cgi?id=243)
patch to fix samba compilation

Compilation of Samba breaks if IPV6 support is missing on the target but is
available on the host.

The attached patch fixes this. It also introduces a new configure option that
allows to keep the libsmbclient library installed. This will be needed for the
gvfs package that I am about to add to buildroot.


-- 
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-04-17 17:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17 17:43 bugzilla at busybox.net [this message]
2009-04-20 10:25 ` [Buildroot] [Bug 285] compilation of samba fails if IPV6 support is missing bugzilla at busybox.net
2009-04-26 21:43 ` 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-285-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