On 17/11/15 05:10 AM, johannes hanika wrote:
On Tue, Nov 17, 2015 at 8:03 AM, Alexandre Prokoudine
...
Still fails to build on a 32bit system with
...
right, it's probably a good thing to fail early on 32-bit.. the new
caching backend (while being much faster and less memory hungry for
RSS) will use up the virtual address space of 32-bit machines very
quickly and make it not a lot of fun indeed to work with darktable. i
guess we should make cmake fail over with an error message even
earlier.
(unless someone has different experiences they'd like to share. the
above error isn't hard to fix at all)
I'm in favour of *not* building for 32bit at all. It's my experience
with running dt on Solaris that I very quickly get to memory usage
well above the 32bit application limit.
Is there any reason to bother building for 32bit any more?
James
(McBofh)
--
Solaris kernel software engineer, system admin and troubleshooter
https://www.jmcpdotcom.com/blog
Find me on LinkedIn @ http://www.linkedin.com/in/jamescmcpherson
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
