Linux CIFS filesystem development
 help / color / mirror / Atom feed
From: Jorell <JorellF-97jfqw80gc7k1uMJSBkQmQ@public.gmane.org>
To: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: linux-cifs 5.4 problems...
Date: Tue, 22 May 2012 17:33:33 -0700	[thread overview]
Message-ID: <jphb90$65r$1@dough.gmane.org> (raw)
In-Reply-To: <4FBC01A5.9000605-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>


Aside from wbclient.pc missing configure still completes and there is a 
wbclient.pc with samba3. I include that path in PKG_CONFIG_PATH and the 
two warnings during configure disappear. Now I just don't understand 
these errors durning make:
mount.cifs.c:866: error: "bkupuid" may be used uninitialized in this 
function
mount.cifs.c:867: error: "bkupgid" may be used uninitialized in this 
function

Or is the wbclient.pc with samba3 that different?
Is there a wbclient in a different debian repo? which one?

  parent reply	other threads:[~2012-05-23  0:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-22 18:55 linux-cifs 5.4 problems Jorell
2012-05-22 21:14 ` Luk Claes
     [not found]   ` <4FBC01A5.9000605-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
2012-05-23  0:33     ` Jorell [this message]
2012-05-23  0:35 ` Jeff Layton

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='jphb90$65r$1@dough.gmane.org' \
    --to=jorellf-97jfqw80gc7k1umjsbkqmq@public.gmane.org \
    --cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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