On Mon, 2013-06-03 at 00:41 +0200, Martin Liška wrote:
I send you in attachment build log and install log file.
Do you have any ideas why calc build failed?
For anyone looking at this, please bear in mind that Martin is
attempting to use LTO. Martin can you verify that a parallel
I built libreoffice with disabled LTO and parallel build was successfull :)
That means LTO optimization really corrupted some of libreoffice
libraries and as a result tests are failing?
Thank you,
Martin
On 3 June 2013 10:34, Michael Meeks michael.me...@suse.com wrote:
On Mon, 2013-06-03 at
Hello guys,
as again there is new series of lo it means more tests were added to
the list of those that are run during the make phase (where normal
software do only build).
For developers it helps to identify issues quickly because your build
crashes if you try to compile your changes but for
On 12/15/2011 10:58 AM, Tomáš Chvátal wrote:
So unless you can look at one of those traces and tell me that the
build should be stopped because it is obvious error in the code (not
in the test, the app code) that needs to be fixed I would want you
Hard to tell without a backtrace.
guys to
2011/12/15 Stephan Bergmann sberg...@redhat.com:
On 12/15/2011 10:58 AM, Tomáš Chvátal wrote:
So unless you can look at one of those traces and tell me that the
build should be stopped because it is obvious error in the code (not
in the test, the app code) that needs to be fixed I would want
On Thu, Dec 15, 2011 at 12:49:41PM +0100, Tomáš Chvátal wrote:
IIUC, make build will omit the checks (and make unitcheck will execute
them).
(for gbuildified modules, build.pl modules will still run tests)
Stephan
That would be awesome to see implemented.
It is (unless I broke it with
2011/12/15 Bjoern Michaelsen bjoern.michael...@canonical.com:
It is (unless I broke it with the last major gbuild -- it should be easy to
fix
then). That said, I really have a bad feeling about letting end users compile
distro builds without running these tests -- the last thing we need is
Hello all,
I have been trying to add support for assigning to named ranges in
VBA. There are a couple of ways VBA does this but for now I'm focusing
on something like:
Range(A1:H8).Name = TestRange
Currently the Name property on [X/ScVba]Range is readonly. I've
attached a patch which is my
