I disagree. Answers have to be responsible.
I got one answer, and the person said, I don't have any experience with enable-dbgutil on
windows..but I advise you not to use VS 2010. That is a responsible answer.
So tell me you don't have any experience with --enable-dbgutil on windows. And then give me some
pointers, about other issues of LibreOffice.. .
But don't answer an email.. where the intent of the msgs is that if I follow your suggestions..I
'might' get a build
-----Original Message-----
From: Norbert Thiebaud [mailto:nthiebaud@gmail.com]
Sent: Wednesday, September 17, 2014 8:19 AM
To: nicholas ferguson
Cc: Eike Rathke; libreoffice
Subject: Re: enable-dbgutil
On Wed, Sep 17, 2014 at 7:13 AM, nicholas ferguson <nicholasferguson@wingarch.com> wrote:
You obviously have never built Libreoffice under a window, using
--enable-dbgutil. So to tell me to do extra work...on your hypothesis.
Don't. I have tons of work then to prove our your hypothesis. And I
think this rule should apply to any answers you give on Libreoffice.
I expect a Redhat developer, world experts in Linux...not to have me
chase their rabbits.
What make you think you can _expect_ anything at all.
As an expert Windows dev you should know that there is no such thing as 'system icu' on windows...
In anycase, you asked a question, it has been answered graciously.. if you do not like the answer,
fine, just ignore it and fidn a better one for yourself.. but do _not_ bite the hand that nicely
tried to help you
Norbert
Context
(message not available)
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.