> > Currently working workaround: Add --enable-long-long=no configure option. > > BTW, I should note that this might be considered the solution to some, > and not a mere workaround. I believe the proper way of spelling this is --disable-long-long. Regards, Martin