OK, so we know
(a) it's not a cygwin thing
(b) its not a visual C thing, because we're both on the same version
(c) it works on a Windows7 box, but not a WindowsServer2008 box.
So it's probably a bug that was fixed sometime in the WindowsVista or  
Windows7 timeframe.
We could probably implement a configure check that looks like
   if $OS == WINDOWS && $OS_VERSION < Vista && length($ROOT_PATH)>XXX
      complain_loudly_and_exit()
where we know XXX is less than 36 and more than 2, because  
"C:/cygwin/home/tinderbox/libreoffice" causes it to break and "W:" does  
not.
Would you be able to figure out what the point is where it starts to  
break?
On 2012-05-10 17:15, Lubos Lunak wrote:
On Thursday 10 of May 2012, Noel Grandin wrote:
Maybe it's a cygwin thing?
I'm running a version that's about a month old (had to update because  
of
other issues). I think it's 1.7.11
If you're out of date, could you try updating and see if that fixes it?
  It was quite recent cygwin even before, but the problem persists even  
with
the most recent, 1.7.15.
On 2012-05-10 14:26, Lubos Lunak wrote:
Windows Server 2008R2 Enterprise, Service Pack 1 Visual Studio 2008
I'm not sure how to find out what exactly the culprint is or how to
possibly do anything more than document it.
Disclaimer: http://www.peralex.com/disclaimer.html
_______________________________________________
LibreOffice mailing list
LibreOffice@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice
  Privacy Policy |
  
Impressum (Legal Info) |
  
Copyright information: Unless otherwise specified, all text and images
  on this website are licensed under the
  
Creative Commons Attribution-Share Alike 3.0 License.
  This does not include the source code of LibreOffice, which is
  licensed under the Mozilla Public License (
MPLv2).
  "LibreOffice" and "The Document Foundation" are
  registered trademarks of their corresponding registered owners or are
  in actual use as trademarks in one or more countries. Their respective
  logos and icons are also subject to international copyright laws. Use
  thereof is explained in our 
trademark policy.