I am not certain where I got the files from. They most likely came from a
linux 64 bit build because I was not responsible for the Windows client. But,
I am not sure anymore.
Liam
On Jan 9, 2014, at 12:17 PM, Ben Shum wrote:
> One thing I'd be sure to check is that you're grabbing the build
One thing I'd be sure to check is that you're grabbing the build files from
the 64-bit Linux tarball staff client builds off your system. Using the
same files from Windows wouldn't be good, and the 32-bit ones are known to
be broken for Mac.
We've built clients since 2.3 times, so the process is
http://www.portents.ca/eg/staff_clients/Evergreen%202.4.2%20Staff%20Client.dmg
Here is a URL that works.
Liam
On Jan 9, 2014, at 11:57 AM, Suzanne Paterno wrote:
> We recently updated our system from 2.3.7 to 2.4.4. Although I had no trouble
> with any of our 2.3 releases, I am running into
I have a 2.4.2 Mac client at
http://www.portents.ca/eg/staff_clients/Evergreen%20/2.4.2%20Staff%20Client.dmg
It is from a default 2.4.2 build, so I am not sure if it is appropriate for all
instances of Evergreen.
Liam Whalen
BC Libraries Cooperative - Sitka
Systems Specialist
855-383-5761 x1022
We recently updated our system from 2.3.7 to 2.4.4. Although I had no trouble with any of our 2.3 releases, I am running into some difficulties creating a Mac client for 2.4.4. Specifically I receive the attached pop up about field mapper.AutoIDL when I try to log into the client. PC versions of t
