On Mon, Jan 26, 2015 at 7:28 AM, Lionel Elie Mamane wrote:
> On Mon, Jan 26, 2015 at 11:40:33AM +0100, Michael Stahl wrote:
>> On 26.01.2015 09:57, Miklos Vajna wrote:
>>> On Mon, Jan 26, 2015 at 05:28:29AM +0100, Lionel Elie Mamane
>>> wrote:
>
Is there some way to get the compilation resu
On Mon, Jan 26, 2015 at 11:40:33AM +0100, Michael Stahl wrote:
> On 26.01.2015 09:57, Miklos Vajna wrote:
>> On Mon, Jan 26, 2015 at 05:28:29AM +0100, Lionel Elie Mamane
>> wrote:
>>> Is there some way to get the compilation result? That could be a
>>> nice way to verify patches for a platform o
On 26.01.2015 09:57, Miklos Vajna wrote:
> On Mon, Jan 26, 2015 at 05:28:29AM +0100, Lionel Elie Mamane
> wrote:
>> Is there some way to get the compilation result? That could be a nice
>> way to verify patches for a platform one does not have a build
>> environment for, and/or to give an experim
On Mon, Jan 26, 2015 at 05:28:29AM +0100, Lionel Elie Mamane
wrote:
> Is there some way to get the compilation result? That could be a nice
> way to verify patches for a platform one does not have a build
> environment for, and/or to give an experimental version to test to a
> bug reporter.
Yes,
On Sun, Jan 11, 2015 at 11:28:02PM -0600, Norbert Thiebaud wrote:
> As you may have noticed, Jenkins is now setting 'Verify +1' on patches
> it built successfully.
> It start putting V+1 because now Jenkins do build on all 3 main
> platforms (at first it was building only Mac, then Mac and Windows
Hi,
On Wed, Jan 14, 2015 at 5:48 PM, Stephan Bergmann
wrote:
> On 01/14/2015 05:44 PM, Maarten Hoes wrote:
>
>> /home/buildslave/source/libo-core/workdir/LexTarget/unoidl/
>> source/sourceprovider-scanner.cxx:1944:17:
>> warning: ‘void yyunput(int, char*, yyscan_t)’ defined but not used
>> [-Wun
On 01/14/2015 05:44 PM, Maarten Hoes wrote:
/home/buildslave/source/libo-core/workdir/LexTarget/unoidl/source/sourceprovider-scanner.cxx:1944:17:
warning: ‘void yyunput(int, char*, yyscan_t)’ defined but not used
[-Wunused-function]
static void yyunput (int c, register char * yy_bp , yyscan
Hrm.
Please forgive me, as this is not completely relevant to the topic... but
Im trying --enable-werror, and still see warnings being treated as warnings
instead of error ?
I mean, I do :
git pull
./autogen.sh --enable-python=internal --disable-online-update
--without-system-libs --without-sys
On Wed, Jan 14, 2015 at 10:09 AM, Stephan Bergmann wrote:
> On 01/14/2015 03:36 PM, Norbert Thiebaud wrote:
>>
>> On Wed, Jan 14, 2015 at 8:25 AM, Stephan Bergmann
>> wrote:
>>>
>>> On 01/12/2015 06:28 AM, Norbert Thiebaud wrote:
FYI: the build are 'default build'. autogen.config c
On 01/14/2015 03:36 PM, Norbert Thiebaud wrote:
On Wed, Jan 14, 2015 at 8:25 AM, Stephan Bergmann wrote:
On 01/12/2015 06:28 AM, Norbert Thiebaud wrote:
FYI: the build are 'default build'. autogen.config contains pretty
much nothing beyond
--with-external-tar, --wtih-ant-home and sometimes
--
On Wed, Jan 14, 2015 at 8:25 AM, Stephan Bergmann wrote:
> On 01/12/2015 06:28 AM, Norbert Thiebaud wrote:
>>
>> FYI: the build are 'default build'. autogen.config contains pretty
>> much nothing beyond
>> --with-external-tar, --wtih-ant-home and sometimes
>> --disable-dependency-tracking
>
>
> at
On 01/12/2015 06:28 AM, Norbert Thiebaud wrote:
FYI: the build are 'default build'. autogen.config contains pretty
much nothing beyond
--with-external-tar, --wtih-ant-home and sometimes --disable-dependency-tracking
at least --enable-werror should hopefully be uncontroversial to add?
__
On Mon, Jan 12, 2015 at 3:43 AM, Christian Lohmaier
wrote:
>
> No surprise, but I certainly would prefer if they also used
> --with-distro=... switch :-)
That is problematic.
Take LibreOfficeLinux.conf:
at first glance
--without-junit
--with-help
are not something we want.. so that would requir
On Mon, Jan 12, 2015 at 4:02 AM, Miklos Vajna wrote:
> Hi Norbert,
>
> On Sun, Jan 11, 2015 at 11:28:02PM -0600, Norbert Thiebaud
> wrote:
>> FYI: the build are 'default build'. autogen.config contains pretty
>> much nothing beyond
>> --with-external-tar, --wtih-ant-home and sometimes
>> --disa
On Sun, Jan 11, 2015 at 11:28:02PM -0600, Norbert Thiebaud wrote:
> As you may have noticed, Jenkins is now setting 'Verify +1' on patches
> it built successfully.
Great!
> A build verification across all 3 platforms takes about 90 minutes...
> but at time there are a queue...
> so the time betwe
Hi Norbert,
On Sun, Jan 11, 2015 at 11:28:02PM -0600, Norbert Thiebaud
wrote:
> FYI: the build are 'default build'. autogen.config contains pretty
> much nothing beyond
> --with-external-tar, --wtih-ant-home and sometimes
> --disable-dependency-tracking
Could you please include the used autoge
Hi Norbert, *,
On Mon, Jan 12, 2015 at 6:28 AM, Norbert Thiebaud wrote:
> As you may have noticed, Jenkins is now setting 'Verify +1' on patches
> it built successfully.
Nice :-)
> FYI: the build are 'default build'. autogen.config contains pretty
> much nothing beyond
> --with-external-tar, --
As you may have noticed, Jenkins is now setting 'Verify +1' on patches
it built successfully.
It does not set -1 yet, as the failure mode are still unreliable at times...
It start putting V+1 because now Jenkins do build on all 3 main
platforms (at first it was building only Mac, then Mac and Windo
18 matches
Mail list logo
