Date: Wed, 4 May 2005 15:27:23 -0700 From: John-Mark Gurney <gurney_j@resnet.uoregon.edu> To: n0oct@sbcglobal.net Cc: freebsd-sparc64@freebsd.org Subject: Re: mount_smbfs Message-ID: <20050504222723.GY2670@funkthat.com> In-Reply-To: <20050504144532.0739592d@shirley> References: <20050504120044.358AE16A4D7@hub.freebsd.org> <20050504144532.0739592d@shirley>
next in thread | previous in thread | raw e-mail | index | archive | help
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...
> As an aside, currently running 5.4RC3 on an E250 with 2x300MHz
> processors without any noticeable problems.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050504222723.GY2670>