On 08/30/2012 09:16, Dimitry Andric wrote:
> [Note that linking GPL-contaminated code into your
> kernel proper is, shall we say, "ideologically impure" ;-) But that is
> not the issue here.]
Can you keep this kind of stuff to -chat please? The more we deal with
the technical aspects the better o
-- Eir Nym
On 1 September 2012 03:12, Dimitry Andric wrote:
> On 2012-08-30 18:43, Eir Nym wrote:
>>
>> On 30 August 2012 20:16, Dimitry Andric wrote:
>
> ...
>
>>> It seems the WERROR= in the xfs module Makefile was right there from the
>>> start, but it was never removed. I have compiled it
On 2012-08-30 18:43, Eir Nym wrote:
On 30 August 2012 20:16, Dimitry Andric wrote:
...
It seems the WERROR= in the xfs module Makefile was right there from the
start, but it was never removed. I have compiled it using gcc, and
there are actually no warnings from gcc at all. With clang, there
-- Eir Nym
On 30 August 2012 20:16, Dimitry Andric wrote:
> On 2012-08-29 10:41, Eir Nym wrote:
> ...
>
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: error: variable
'fbno' is used uninitialized whenever 'if' condition is false
[-Werror,-Wsometimes-uninitialized]
On 2012-08-29 10:41, Eir Nym wrote:
...
/usr/head/src/sys/gnu/fs/xfs/xfs_alloc.c:1449:11: error: variable
'fbno' is used uninitialized whenever 'if' condition is false
[-Werror,-Wsometimes-uninitialized]
else if (args->minlen == 1 && args->alignment == 1 && !args->isfl
&&
^
-- Eir Nym
On 29 August 2012 12:41, Eir Nym wrote:
> -- Eir Nym
>
>
> On 29 August 2012 01:19, Dimitry Andric wrote:
>> On 2012-08-28 23:05, Eir Nym wrote:
>> ...
>>
>>> This one for example:
>>> cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall
>>> -Wredundant-decls -Wnested-externs -Wstri
-- Eir Nym
On 29 August 2012 01:19, Dimitry Andric wrote:
> On 2012-08-28 23:05, Eir Nym wrote:
> ...
>
>> This one for example:
>> cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall
>> -Wredundant-decls -Wnested-externs -Wstrict-prototypes
>> -Wmissing-prototypes -Wpointer-arith -Winline -Wc
On 2012-08-28 23:05, Eir Nym wrote:
...
This one for example:
cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall
-Wredundant-decls -Wnested-externs -Wstrict-prototypes
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef
-Wno-pointer-sign -fformat-extensions -Wmissing-include-di
-- Eir Nym
On 29 August 2012 00:28, Dimitry Andric wrote:
> On 2012-08-28 21:51, Eir Nym wrote:
>>
>> On 28 August 2012 22:49, Dimitry Andric wrote:
>>>
>>> On 2012-08-28 18:31, Eir Nym wrote:
>>> What is the error you were getting on amd64?
>>
>> i386 never failed, amd64 — always
>
>
> Please
On 2012-08-28 21:51, Eir Nym wrote:
On 28 August 2012 22:49, Dimitry Andric wrote:
On 2012-08-28 18:31, Eir Nym wrote:
What is the error you were getting on amd64?
i386 never failed, amd64 — always
Please post the *exact* error message, otherwise I will not be able to
help you.
-- Eir Nym
On 28 August 2012 23:51, Eir Nym wrote:
> -- Eir Nym
>
>
> On 28 August 2012 22:49, Dimitry Andric wrote:
>> On 2012-08-28 18:31, Eir Nym wrote:
>>>
>>> I can't build FreeBSD (GENERIC & custom kernel) with clang. Build
>>> finishes for i386 and fails for amd64 for same kernels
>>
>>
-- Eir Nym
On 28 August 2012 22:49, Dimitry Andric wrote:
> On 2012-08-28 18:31, Eir Nym wrote:
>>
>> I can't build FreeBSD (GENERIC & custom kernel) with clang. Build
>> finishes for i386 and fails for amd64 for same kernels
>
>
> What is the error you were getting on amd64?
>
>
i386 never fail
On 2012-08-28 18:31, Eir Nym wrote:
I can't build FreeBSD (GENERIC & custom kernel) with clang. Build
finishes for i386 and fails for amd64 for same kernels
What is the error you were getting on amd64?
I have bsd box with following clang version:
FreeBSD clang version 3.0 (branches/release_
I can't build FreeBSD (GENERIC & custom kernel) with clang. Build
finishes for i386 and fails for amd64 for same kernels
I have bsd box with following clang version:
> FreeBSD clang version 3.0 (branches/release_30 142614) 20111021
> Target: x86_64-unknown-freebsd10.0
> Thread model: posix
I try
14 matches
Mail list logo
