Date: Fri, 6 May 2005 09:31:53 -0500 From: n0oct@sbcglobal.net To: freebsd-sparc64@freebsd.org Subject: Re: mount_smbfs Message-ID: <20050506093153.0aff1550@shirley> In-Reply-To: <20050504222723.GY2670@funkthat.com> References: <20050504120044.358AE16A4D7@hub.freebsd.org> <20050504144532.0739592d@shirley> <20050504222723.GY2670@funkthat.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 4 May 2005 15:27:23 -0700 John-Mark Gurney <gurney_j@resnet.uoregon.edu> wrote: > n0oct@sbcglobal.net wrote this message on Wed, May 04, 2005 at 14:45 -0500: > > Some time ago I asked the silly question: 'does mount_smbfs work on > > sparc64?'. The simple answer is 'no.' The 'make' fails with > > > > #error "Macros for Big-Endians are incomplete" > > > > which, to my limited knowledge, says that it ain't gonna compile on a > > system like a sparc64. > > > > However, I have been doing some digging at work, and lo and behold, Mac > > OSX has a 'mount_smbfs' command, which leads me to ask this question: > > is the Big-endian/Little-endian thing different between Mac PowerPC > > processors [G5] and sparc64? If not, is there a way I can beat on the > > Nope... big-endian is big-endian, be it sparc64, arm, powerpc or any > other... > > > code to make mount_smbfs compile for sparc64? IANAP by any stretch of > > the imagination, but if someone is willing to guide me, I can certainly > > try. Thanks. > > Very likely if the code base is the same... You probably just need to > look around the #error for the defines, and see what MacOSX has added... > > Probably just need to copy the #define lines between the #else and #endif > (or #if and #else)... > > Good luck... Thanks! I found the section in smb_lib.h on the FreeBSD machine, finding it on the Mac is another challenge. Doesn't appear to be a whole lot of source code. . . -- 72, Jim N0OCT
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050506093153.0aff1550>