Evan Hisey wrote:
> I don't know if this will help, but over on th openmosix lists, the
> recommendation is upgrading 4.1.1 to 4.1.2 do to issues in the
> compiler, that can cause it to complian compling perfectly good kernel
> code, ie. code that compiled on 4.1.0 and 4.1.2.
The warning is reas
I don't know if this will help, but over on th openmosix lists, the
recommendation is upgrading 4.1.1 to 4.1.2 do to issues in the
compiler, that can cause it to complian compling perfectly good kernel
code, ie. code that compiled on 4.1.0 and 4.1.2.
Evan
On 11/1/06, Duncan Webb <[EMAIL PROTECT
Jason Tackaberry wrote:
> On Wed, 2006-11-01 at 09:40 -0500, Jason Tackaberry wrote:
>> Hmm, what is the error/warning line gcc gives you? I don't see a
>> problem with gcc 4.1.1 on FC5.
>
> (I know that int f(void) is correct, and I don't have any objection to
> your patch, but I want to know wh
On Wed, 2006-11-01 at 09:40 -0500, Jason Tackaberry wrote:
> Hmm, what is the error/warning line gcc gives you? I don't see a
> problem with gcc 4.1.1 on FC5.
(I know that int f(void) is correct, and I don't have any objection to
your patch, but I want to know why you're having problems.)
-
On Wed, 2006-11-01 at 08:16 +0100, Duncan Webb wrote:
> gcc 4.1.1 is a bit fussy over function prototypes, it complains about
> int f() so this patch changes the two calls to int f(void).
Hmm, what is the error/warning line gcc gives you? I don't see a
problem with gcc 4.1.1 on FC5.
---
Dirk Meyer wrote:
> Duncan Webb wrote:
>> gcc 4.1.1 is a bit fussy over function prototypes, it complains about
>> int f() so this patch changes the two calls to int f(void).
>
> Fixed. Feel free to check in patches youself in the future, you have
> full svn access and the 1.6.0 release shows tha
Duncan Webb wrote:
> gcc 4.1.1 is a bit fussy over function prototypes, it complains about
> int f() so this patch changes the two calls to int f(void).
Fixed. Feel free to check in patches youself in the future, you have
full svn access and the 1.6.0 release shows that you know what you are
doin
gcc 4.1.1 is a bit fussy over function prototypes, it complains about
int f() so this patch changes the two calls to int f(void).
Duncan
Index: base/src/extensions/objectrow.c
===
--- base/src/extensions/objectrow.c (revision 1952
