Re: [ovs-discuss] OvS 1.0.0 Compile error on fedora 13

2010-05-19 Thread Justin Pettit
Oh, sorry. I was thinking this was in the datapath, and the kernel has it defined there. Yes, this is better. --Justin On May 19, 2010, at 9:03 AM, Ben Pfaff wrote: > I'd prefer to use >#include > since it's the standard header for S_ISCHR. > > On Wed, May 19, 2010 at 08:37:31AM -0

Re: [ovs-discuss] OvS 1.0.0 Compile error on fedora 13

2010-05-19 Thread Ben Pfaff
I'd prefer to use #include since it's the standard header for S_ISCHR. On Wed, May 19, 2010 at 08:37:31AM -0700, Justin Pettit wrote: > Can you try adding "#include " to the top of dpif-linux.c > amongst all the other "#include statements? If that fixes the > problem, we'll get that c

Re: [ovs-discuss] OvS 1.0.0 Compile error on fedora 13

2010-05-19 Thread Justin Pettit
Can you try adding "#include " to the top of dpif-linux.c amongst all the other "#include statements? If that fixes the problem, we'll get that checked into the repository. Thanks! --Justin On May 19, 2010, at 6:52 AM, DarkBls wrote: > Hi. > > I just tested to compile OvS 1.0.0 on Fedora

[ovs-discuss] OvS 1.0.0 Compile error on fedora 13

2010-05-19 Thread DarkBls
Hi. I just tested to compile OvS 1.0.0 on Fedora 13 beta with no luck : [...] gcc -Wstrict-prototypes -Wall -Wno-sign-compare -Wpointer-arith -Wdeclaration-after-statement -Wformat-security -Wswitch-enum -Wunused-parameter -Wstrict-aliasing -Wbad-function-cast -Wcast-align -Wstrict-prototypes -W