Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Thank you to you both for looking at this. I had seen the warnings on the lode guide page, but I 
had perhaps been too optimistic in assuming the there would not be a problem on my system. However, 
clearly the spaces are a problem and I will now follow the earlier instructions to eliminate these 
and reattempt the build. Also, I will more closely next time adhere to guidelines and warnings, 
such as those on the lode guide page.

Best regards

Jason

Sent from my Windows Phone
________________________________
From: Jan Iversen<mailto:jani@documentfoundation.org>
Sent: ‎27/‎11/‎2016 18:04
To: Norbert Thiebaud<mailto:nthiebaud@gmail.com>
Cc: Jason Marshall<mailto:j_k_marshall_2004@live.com>; 
libreoffice@lists.freedesktop.org<mailto:libreoffice@lists.freedesktop.org>
Subject: Re: Lode Build Problem



and I'm pretty sure that confused the heck out of git to have spaces there

I can confirm that there are several problems having spaces in the directory, which is why we write
"A couple of warning, based on experience from earlier installations:

  *   Do not use a network drive, it will not work. There can also be problems with some older USB 
drives
  *   Do not use names longer than 8 char
  *   Only use a-z and 0-9 in the name, NO spaces or other special characters"

on the lode page:

https://wiki.documentfoundation.org/Development/lode


rgds
jan I.


Context


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.