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

Re: [tdf-discuss] Correct Forum for Build Questions


On Thu, Sep 30, 2010 at 1:40 AM, Danishka Navin <danishka@gmail.com> wrote:
this was in the Document Foundation IRC.
Can some one add information on dependencies in 'How to Build' doc if deps
are required.

<Cypher3c> hi, I am trying to build LibreOffice on windows with MinGW, and I
was wondering what the dependencies are
<Cypher3c> i tried ./autogen.sh --with-distro=Win32, but it complained when
trying to make symbolic links from .git/hooks/commit-msg to
../../commit-msg.g
<Cypher3c> I am building on Windows 7 x64


I saw this after he left the channel


--
Danishka Navin
http://danishkanavin.blogspot.com


Um, Hi, remember me?  I'm the OP.  I'm all for discussion on
development issues, but could you please not hijack the thread?  I'd
like to see if there is someone who can answer my question.  I've
Googled the error number and it doesn't seem to come up with anything
relevant.  I'm not sure what make means by "rebuild" the modules since
I have the latest RPMs available for Fedora 13.  Should I take this
question to IRC?

Thanks.

George
-- 
To unsubscribe, send an empty e-mail to discuss+unsubscribe@documentfoundation.org
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at http://www.documentfoundation.org/lists/discuss/

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.