2007-11-26 15:33:47     BF561-EZKIT and samba mount

Document created by Aaronwu Employee on Aug 5, 2013
Version 1Show Document
  • View in full screen mode

2007-11-26 15:33:47     BF561-EZKIT and samba mount

Bill Fassler (UNITED STATES)

Message: 47526    I just built a default image for the BF561-EZKIT on the trunk and tried to add samba mounting

and received this error:

 

mcpu=bf561-0.3  -c -o smbmount.o smbmount.c

cc1: warning: bf561 support is incomplete yet.

cc1: warning: bf561 support is incomplete yet.

smbmount.c: In function ‘parse_args’:

smbmount.c:106: error: ‘struct smb_mount_data’ has no member named ‘addr’

smbmount.c:109: error: ‘struct smb_mount_data’ has no member named ‘server_name’

smbmount.c:116: error: ‘struct smb_mount_data’ has no member named ‘server_name’

smbmount.c:119: error: ‘struct smb_mount_data’ has no member named ‘client_name’

smbmount.c:125: error: ‘struct smb_mount_data’ has no member named ‘client_name’

smbmount.c:128: error: ‘struct smb_mount_data’ has no member named ‘username’

smbmount.c:134: error: ‘struct smb_mount_data’ has no member named ‘username’

smbmount.c:144: error: ‘struct smb_mount_data’ has no member named ‘domain’

smbmount.c:150: error: ‘struct smb_mount_data’ has no member named ‘domain’

smbmount.c:194: error: ‘struct smb_mount_data’ has no member named ‘max_xmit’

smbmount.c:197: error: ‘struct smb_mount_data’ has no member named ‘password’

smbmount.c:202: error: ‘struct smb_mount_data’ has no member named ‘password’

smbmount.c: In function ‘fullpath’:

smbmount.c:333: warning: unused variable ‘path’

smbmount.c: In function ‘main’:

smbmount.c:538: error: ‘struct smb_mount_data’ has no member named ‘service’

smbmount.c:539: error: ‘struct smb_mount_data’ has no member named ‘service’

smbmount.c:541: error: ‘struct smb_mount_data’ has no member named ‘root_path’

smbmount.c:544: error: ‘struct smb_mount_data’ has no member named ‘username’

smbmount.c:545: error: ‘struct smb_mount_data’ has no member named ‘username’

smbmount.c:548: error: ‘struct smb_mount_data’ has no member named ‘username’

smbmount.c:550: error: ‘struct smb_mount_data’ has no member named ‘username’

smbmount.c:551: error: ‘struct smb_mount_data’ has no member named ‘username’

smbmount.c:554: error: ‘struct smb_mount_data’ has no member named ‘max_xmit’

smbmount.c:561: error: ‘struct smb_mount_data’ has no member named ‘addr’

smbmount.c:562: error: ‘struct smb_mount_data’ has no member named ‘addr’

smbmount.c:562: error: ‘SMB_PORT’ undeclared (first use in this function)

smbmount.c:562: error: (Each undeclared identifier is reported only once

smbmount.c:562: error: for each function it appears in.)

smbmount.c:564: error: ‘struct smb_mount_data’ has no member named ‘domain’

smbmount.c:580: error: ‘struct smb_mount_data’ has no member named ‘addr’

smbmount.c:584: warning: implicit declaration of function ‘inet_aton’

smbmount.c:584: error: ‘struct smb_mount_data’ has no member named ‘addr’

smbmount.c:589: error: ‘struct smb_mount_data’ has no member named ‘addr’

smbmount.c:595: error: ‘struct smb_mount_data’ has no member named ‘fd’

smbmount.c:596: error: ‘struct smb_mount_data’ has no member named ‘fd’

smbmount.c:629: error: ‘struct smb_mount_data’ has no member named ‘password’

smbmount.c:632: error: ‘struct smb_mount_data’ has no member named ‘server_name’

smbmount.c:634: error: ‘struct smb_mount_data’ has no member named ‘server_name’

smbmount.c:641: error: ‘struct smb_mount_data’ has no member named ‘server_name’

smbmount.c:642: error: ‘struct smb_mount_data’ has no member named ‘server_name’

smbmount.c:646: error: ‘struct smb_mount_data’ has no member named ‘client_name’

smbmount.c:648: error: ‘struct smb_mount_data’ has no member named ‘client_name’

smbmount.c:655: error: ‘struct smb_mount_data’ has no member named ‘client_name’

smbmount.c:656: error: ‘struct smb_mount_data’ has no member named ‘client_name’

smbmount.c:664: error: ‘struct smb_mount_data’ has no member named ‘fd’

smbmount.c:670: error: ‘struct smb_mount_data’ has no member named ‘fd’

smbmount.c:469: warning: unused variable ‘mtab’

smbmount.c:451: warning: unused variable ‘fd’

make[3]: *** [smbmount.o] Error 1

make[3]: Leaving directory `/home/vocal/project/blackfin-svn-trunk/uClinux-dist/user/smbmount'

make[2]: *** [smbmount] Error 2

make[2]: Leaving directory `/home/vocal/project/blackfin-svn-trunk/uClinux-dist/user'

make[1]: *** [all] Error 2

make[1]: Leaving directory `/home/vocal/project/blackfin-svn-trunk/uClinux-dist/user'

make: *** [subdirs] Error 1

 

 

Granted I have not updated my trunk in weeks, but was this broken?

 

Bill

QuoteReplyEditDelete

 

 

2007-11-26 15:59:18     Re: BF561-EZKIT and samba mount

Bill Fassler (UNITED STATES)

Message: 47527    I've updated my svn checkout for the trunk and still get this error.

We've done a lot of proprietary development for the BF561 and custom

boards are arriving soon.  This is critical for us.  Why won't samba build

for BF561?

QuoteReplyEditDelete

 

 

2007-11-26 22:39:27     Re: BF561-EZKIT and samba mount

Sonic Zhang (CHINA)

Message: 47533   

 

Did you find the same building issue on bf537/533?

QuoteReplyEditDelete

 

 

2007-11-27 09:55:28     Re: BF561-EZKIT and samba mount

Bill Fassler (UNITED STATES)

Message: 47632    Yes.  The problem also exists on the BF537-STAMP.  When I perform a default build for either BF537-STAMP or BF561-EZKIT, basic SAMBA file system support is configured and built without problems.

 

*************************************************************

These are selected in the default build and compiles OK (both BF561-EZKIT & BF537-STAMP)

*************************************************************

<M> NFS file system support

  [*]   Provide NFSv3 client support     

  [ ]     Provide client support for the NFSv3 ACL protocol extension

  [ ]   Provide NFSv4 client support (EXPERIMENTAL)

  [ ]   Allow direct I/O on NFS files

< > NFS server support

  [ ] Support for rpcbind versions 3 & 4 (EXPERIMENTAL)

< > Secure RPC: Kerberos V mechanism (EXPERIMENTAL)

< > Secure RPC: SPKM3 mechanism (EXPERIMENTAL) 

<M> SMB file system support (to mount Windows shares etc.)

  [ ]   Use a default NLS

< > CIFS support (advanced network filesystem for Samba, Window and other CIFS compliant servers)

< > NCP file system support (to mount NetWare volumes)

< > Coda file system support (advanced network fs)

< > Andrew File System support (AFS) (EXPERIMENTAL)

< > Plan 9 Resource Sharing Support (9P2000) (Experimental)

 

*****************************************************************************

When I check these in filesystem applications, then I get that faiulure and

I can't seem to use (mount/unmount) SAMBA without these settings:

I find it odd that SAMBA support is built by default, but the application(s)

that allow you to use it easily are not.

*******************************************************************************

--- SAMBA

[ ] samba

--- SMBFS

[*] smbmount

[*] smbumount    

QuoteReplyEditDelete

 

 

2007-11-27 13:58:40     Re: BF561-EZKIT and samba mount

Robin Getz (UNITED STATES)

Message: 47648    Bill:

 

We will look at it, and get it fixed. Complaining about it on multiple places only makes things go slower, since we need to read every message, rather than actually working on the problem.

 

The bottom line - this is the joys of working on trunk - some things are untested. We make sure that samba works on releases, but for most things - in day to day operation no one uses it. As trunk is getting closer to a release, we do our release testing on it, and will find (as you did) the kernel upgrade broke samba - so we need to go upgrade samba.

 

If you don't like this - the only other option is to stick with the older release.

 

-Robin

QuoteReplyEditDelete

 

 

2007-11-27 14:31:30     Re: BF561-EZKIT and samba mount

Bill Fassler (UNITED STATES)

Message: 47650    Sorry Robin, I thought the CIFS was different (although related).  The proprietary development

was done on the release and I was instructed to backport all my work on device driver development and open source multi-media apps to the release.  After a few days, I began to think that just wasn't feasible and it looks like I convinced everyone that migrating the proprietary work to the trunk would be much less painless than me trying to backport everything else. After winning the argument I guess I was in a small panic when something that was needed was broken.

 

SAMBA is only needed in the interim, NFS times out for some reason and we can't seem to run our real time video.  Once our custom boards get in and things move forward the proprietary application(s) should fit on flash and SAMBA won't be needed.

 

I am under the gun and feelin' the stress. 60 hours weeks and still not progressing fast enough to appease.  Needless to say, I am not always thinking straight.

 

My apologies,

Bill

QuoteReplyEditDelete

 

 

2007-11-27 17:32:56     Re: BF561-EZKIT and samba mount

Robin Getz (UNITED STATES)

Message: 47655    Bill:

 

> NFS times out for some reason

 

That doesn't sound right either - we/I use nfs all the time. Can you describe what you are doing? The only time I have had issues is when not setting the read/write size properly.

 

-Robin

QuoteReplyEditDelete

 

 

2007-11-28 01:25:10     Re: BF561-EZKIT and samba mount

Mike Frysinger (UNITED STATES)

Message: 47689    you've selected the wrong thing ... use the stuff under "SAMBA", not the stuff under "SMBFS" ... i feel like you've asked this before in the past ?

QuoteReplyEditDelete

 

 

2007-11-28 17:01:57     Re: BF561-EZKIT and samba mount

Mike Frysinger (UNITED STATES)

Message: 47787    this is already documented fully here:

http://docs.blackfin.uclinux.org/doku.php?id=uclinux-dist:smb

QuoteReplyEditDelete

 

 

2008-01-25 10:22:45     Re: BF561-EZKIT and samba mount

Bill Fassler (UNITED STATES)

Message: 50148    Robin et al -

 

I finally figured out why I occasionally experienced problems with NFS mounts timing out.  When this happened I realize now it was at times that I had forgot the "-o nolock" switch/argument.

 

Its not always easy to admit my dumb errors, but I want anyone else who experiences this to know why it happened for me.

 

Bill

Attachments

    Outcomes