Author Topic: Taking into account C99 standard (Read 42193 times)

Pavel_47 · « **on:** October 14, 2014, 01:01:22 pm »

Hello,

While trying to use the following construction:

for (int i = 0; i < numb_of_clients; i++)

I get the folllowing message:

udp_server_v0.c 54 error: 'for' loop initial declarations are only allowed in C99 mode
udp_server_v0.c 54 note: use option -std=c99 or -std=gnu99 to compile your code

I searched for these options in Settings-->Compiler-->Compiler Settings-->Global Compiler Settings-->Compiler Flags, but didn't find them.
Then I've tried to add them into Settings-->Compiler-->Compiler Settings-->Global Compiler Settings-->Other Options.

No any effect !

Thanks in advance.

Pavel.

Quiss · « **Reply #1 on:** October 14, 2014, 02:59:35 pm »

Those will affect on new projects. For your current project, right click project name on the left pane(under Manager->Projects tab) and select Build Options.

stahta01 · « **Reply #2 on:** October 15, 2014, 03:20:52 am »

Quote from: Quiss on October 14, 2014, 02:59:35 pm

Those will affect on new projects. For your current project, right click project name on the left pane(under Manager->Projects tab) and select Build Options.

The above is NOT true in most if not all cases.

He is likely changing the wrong global compiler.
He needs to verify the project is using the same CB Compiler as the one he changed.

EDIT: As found out later in this thread or another thread he is using a Custom makefile without any understanding of what it means in CB.

Tim S.

Quiss · « **Reply #3 on:** October 15, 2014, 07:26:50 am »

I've just tried this and yes, you're right stahta01. Some years before, I don't remember exactly, I had that kind of problem but obviously it was from something else. Sorry for misinformation.

Pavel_47 · « **Reply #4 on:** October 30, 2014, 01:03:54 pm »

Hello stahta01,

I put option -std=c99 into Prebuild Steps (if I properly understood your suggestion)

Here is compilation output:
Running target pre-build steps
-std=c99
Execution of '-std=c99' in 'C:\Users\Pavel\Documents\Proj_EPFL\contiki-2.7\LoWPAN_EPFL\link_v1' failed.

Pavel_47 · « **Reply #5 on:** November 05, 2014, 02:44:28 pm »

Probable explanation - Code::Block processes .C files with "C compiler" rather than with "C++ compiler"
And C99 standard is for C++.
Correct ?

scarphin · « **Reply #6 on:** November 05, 2014, 03:45:26 pm »

Think in this way; if it was a standard for C++ then it would be named as C++99.

Pavel_47 · « **Reply #7 on:** November 05, 2014, 04:09:38 pm »

There is no flag C++99 in the available options

oBFusCATed · « **Reply #8 on:** November 05, 2014, 06:48:24 pm »

There is no C++99, this is what scarphin told you. The standards are c++98,c++03,c++11,c++14.
But if any or all of these are supported by your compiler is up to your compiler and its current version you're using.
So check its documentation.

Miguel Gimenez · « **Reply #9 on:** November 05, 2014, 09:01:36 pm »

You must put -std=c99 into Compiler settings -> Other options, not in Prebuild Steps

Pavel_47 · « **Reply #10 on:** November 17, 2014, 01:44:04 pm »

Hello Mgimenez

Here is my source code:

Code

#include "contiki.h"
#include <stdio.h> /* For printf() */

void ssi0_isr()
{
}

/*---------------------------------------------------------------------------*/
PROCESS(hello_world_process, "Hello world process");
AUTOSTART_PROCESSES(&hello_world_process);
/*---------------------------------------------------------------------------*/
PROCESS_THREAD(hello_world_process, ev, data)
{
    PROCESS_BEGIN();

    for(int i=0; i < 10; i++)
    {
        printf("Hello, world\n");
    }
    PROCESS_END();
}

Here is compiler log:

Code

||=== Build: Debug in link_v1 (compiler: GNU GCC Compiler for ARM) ===|
test_cpp_v1.c||In function 'process_thread_hello_world_process':|
test_cpp_v1.c|16|error: 'for' loop initial declarations are only allowed in C99 mode|
test_cpp_v1.c|16|note: use option -std=c99 or -std=gnu99 to compile your code|
..\..\Makefile.include|234|recipe for target 'test_cpp_v1.co' failed|
||=== Build failed: 2 error(s), 0 warning(s) (0 minute(s), 1 second(s)) ===|

Here is Compiler settings -> Other options (please see the snapshot).

Best Regards

Pavel

P.S. I also tried with -std=c99 ... the same result

Jenna · « **Reply #11 on:** November 17, 2014, 05:37:11 pm »

This is not the content of the "Build log"-tab, but from "Build messages".

Quote from: Pavel_47 on November 17, 2014, 01:44:04 pm

Code

..\..\Makefile.include|234|recipe for target 'test_cpp_v1.co' failed|

Is it a custom makefile project ?
If yes, the settings you make in compiler tab are ignored, because you do not use C::B's own build-system.
You have to make the needed changes inside the makefile or in the make-comamandline in the "Project -> Build options... -> Make options" (if your makefile supports this).

Pavel_47 · « **Reply #12 on:** November 17, 2014, 06:54:16 pm »

Hello Jens

Thank you for suggestions.
I've tried both (at least as I understood them)

1. Changing custom makefile ... I included "-std=c99" on the top of makefile:

Code

#DEFINES+=PROJECT_CONF_H=\"project-conf.h\"
-std=c99
all: test_cpp_v1
APPS=servreg-hack
CONTIKI=../..

UIP_CONF_IPV6=1
#SERVER_REPLY=1

CFLAGS+= -DUIP_CONF_IPV6_RPL

ifdef WITH_COMPOWER
APPS+=powertrace
CFLAGS+= -DCONTIKIMAC_CONF_COMPOWER=1 -DWITH_COMPOWER=1 -DQUEUEBUF_CONF_NUM=4
endif

ifdef SERVER_REPLY
CFLAGS+=-DSERVER_REPLY=$(SERVER_REPLY)
endif
ifdef PERIOD
CFLAGS+=-DPERIOD=$(PERIOD)
endif

include $(CONTIKI)/Makefile.include

Result: nothing changed - the build log is the same:

Code

||=== Build: Debug in link_v1 (compiler: GNU GCC Compiler for ARM) ===|
test_cpp_v1.c||In function 'process_thread_hello_world_process':|
test_cpp_v1.c|16|error: 'for' loop initial declarations are only allowed in C99 mode|
test_cpp_v1.c|16|note: use option -std=c99 or -std=gnu99 to compile your code|
..\..\Makefile.include|234|recipe for target 'test_cpp_v1.co' failed|
||=== Build failed: 2 error(s), 0 warning(s) (0 minute(s), 1 second(s)) ===|

2. Changing make-commandlinein the "Project -> Build options... -> Make options" ... instead of "$make -f $makefile" I've put "$make -std c99 -f $makefile".
After having run "Build" the "Build messages" window are rapidly filled with endless messages ... I was need to abort.

Regards

Pavel

oBFusCATed · « **Reply #13 on:** November 17, 2014, 08:21:54 pm »

Sorry but you are changing settings randomly and you're expecting it to magically work.
I have to disappoint you - it won't sooner or later you'll hit the road block.
So if you want to have any success in what you're doing - start reading on Makefiles, compilers, linkers and so on.

stahta01 · « **Reply #14 on:** November 17, 2014, 08:47:03 pm »

Quote from: oBFusCATed on November 17, 2014, 08:21:54 pm

...
So if you want to have any success in what you're doing - start reading on Makefiles, compilers, linkers and so on.

I agree with the above; I also suggest you STOP asking about how to fix the Contiki Makefile on this site!

I suggest a site that supports questions on how to write or modify makefiles or a site supporting compiling Contiki.

Edit2: You might try the C Board site http://cboard.cprogramming.com/forum.php

Tim S.

stahta01 · « **Reply #15 on:** November 17, 2014, 08:54:48 pm »

The places in CB that I believe matter to custom makefile projects.
Not sure if Execution Directory matter or not.

Project -> Properties
Tab: Project Settings
Checkbox: "This is a custom makefile"
Textbox: "Makefile:"
? Execution Directory

Project -> Properties
Tab: Build Targets

Project -> "Build Options"
Tab: "Make" commands

Settings -> Compiler
Tab: Toolchain Excutables
Textbox: "Make Program:"

Tim S.

stahta01 · « **Reply #16 on:** November 19, 2014, 06:06:34 pm »

Quote from: stahta01 on November 17, 2014, 08:54:48 pm

The places in CB that I believe matter to custom makefile projects.
Not sure if Execution Directory matter or not.

Project -> Properties
Tab: Project Settings
Checkbox: "This is a custom makefile"
Textbox: "Makefile:"
? Execution Directory

Project -> Properties
Tab: Build Targets

Project -> "Build Options"
Tab: "Make" commands

Settings -> Compiler
Tab: Toolchain Excutables
Textbox: "Make Program:"

Tim S.

FYI: I just tried using Code::Blocks and Cygwin to build Contiki Hello world it built OK

Link to my Project is here https://github.com/stahta01/contiki/blob/master/examples/hello-world/hello_world-cygwin.cbp

Edit: Links to second project and readme for CB file:
https://github.com/stahta01/contiki/blob/master/platform/win32/platform_win32-cygwin.cbp
https://github.com/stahta01/contiki/blob/master/README-CodeBlocks.txt

Tim S.

Pavel_47 · « **Reply #17 on:** January 22, 2015, 04:39:55 pm »

Hello Tim,

I've tried without custom make.
Here is buil log of hello_world:
"hello_world MinGW - Makefile": The compiler's setup is invalid, so Code::Blocks cannot find/run the compiler.
Probably the toolchain path within the compiler options is not setup correctly?! (Do you have a compiler installed?)
Goto "Settings->Compiler...->Global compiler settings->unknown->Toolchain executables" and fix the compiler's setup.
Skipping...
Nothing to be done (all items are up-to-date).

Here is my compiler settings. All executables does exist in specified location.

[attachment deleted by admin]

Pavel_47 · « **Reply #18 on:** January 22, 2015, 06:23:51 pm »

In the "make commands" tab there is target that I want to modify
But edit fields aren't editable.
How to change target ?

stahta01 · « **Reply #19 on:** January 22, 2015, 06:44:24 pm »

Do you have the make.exe in the bin folder for your compiler?
Does the C compiler exe exist in the bin folder for your compiler?

Tim S.

stahta01 · « **Reply #20 on:** January 22, 2015, 06:46:19 pm »

Attach the zipped CB project or at least post the full build log.

Tim S.

stahta01 · « **Reply #21 on:** January 22, 2015, 06:49:30 pm »

Quote from: Pavel_47 on January 22, 2015, 06:23:51 pm

In the "make commands" tab there is target that I want to modify
But edit fields aren't editable.
How to change target ?

IS IT A CUSTOM MAKE CB PROJECT OR IS IT NOT!!!!

Tim S.

Pavel_47 · « **Reply #22 on:** January 22, 2015, 07:36:34 pm »

Not !
The "this is the custom Makefile" is unchecked.
Doing some manipulations with project (removing your platform and adding cc2538dk) I've discovered in some moment that make commands became "editable",
so I changed the TARGET value for CC2538dk.
Then I've tried to compile ... compilation failed (for some other reasons).
But then, when I came back to make commands tab, it became "passive" once more.

Mystery ...

Answering to your previous question concerning make.exe, it isn't inside compiler directory, but in another place, for which I've specified the path (please, see the image below)

Pavel_47 · « **Reply #23 on:** January 22, 2015, 09:11:08 pm »

Well, working with Code::Blocks requires a lot of attention and also ... habit.
Indeed, modifying of TARGET is possible only if option "this is the custom Makefile" is desactivated.
But after modifying of any option one must confirm by Ok in the the "Project/Target" window, and it seems also save the project, otherwise it's total confusion.

So in abscence of custom makefile, the TARGET is defined only by platform directories, attached to project - i.e. there is no any option in the project settings, allowing to define TARGET, isn't it ?

If this is a case, there are still problems: the compiler "doesn't see" a .h file, that is attached to project (please see the picture).

Where is a problem ?

Thanks in advance.

Sincerely ...

[attachment deleted by admin]

BlueHazzard · « **Reply #24 on:** January 22, 2015, 10:07:26 pm »

h files are not passed to the compiler over parameter. You have to set the path to your include files over Project->Build Options-> Search directories->Compiler. Don forget to select on the left site the right target (or the project name if you want apply this setting project wide)

BlueHazzard · « **Reply #25 on:** January 22, 2015, 10:18:23 pm »

I think you have to understand what c::b (code::blocks) and make is. You are confusing thing up like hell...
So i will try to explain a bit:
Code blocks is a IDE. Basically a editor which helps you compile c and c++ programs, but it is not a compiler.
Make files are the "old", but probably most used way to manage the build process.

If you are using custom make files in c::b you use c::b as pure editor. The whole compiler options tabs and so on are not forwarded to make. Only the make file, and the target name.

If you are using c::b as build manager you can use targets and the compiler options tabs...

i hope this makes things more clear. I would suggest you to read a bit about compiler and make or c::b, because at a certain point you will need to know what you are doing, and right now i think you have no plan about the whole build process...

greetins

Pavel_47 · « **Reply #26 on:** January 23, 2015, 12:13:56 pm »

Quote from: BlueHazzard on January 22, 2015, 10:07:26 pm

h files are not passed to the compiler over parameter. You have to set the path to your include files over Project->Build Options-> Search directories->Compiler. Don forget to select on the left site the right target (or the project name if you want apply this setting project wide)

Thank you BlueHazzard

It's more clear now. I followed your suggestions and now compilation seems to proceed in right way.
Nevertheless errors occurs ... this time caused by code. I've already posted them on gcc forum, but also repeat it here hoping that someone already faced such cases (please, see the Build log on the image below).
From the core of error message it follows that processor selection is wrong, but I didn't specify any processor in compiler settings.
I founded the code that caused the problem. It's located inside of startup-gcc.c file (the last name in compiler command). Here is this code (extract):

Code

  /* Zero-fill the bss segment. */
  __asm("    ldr     r0, =_bss\n"
        "    ldr     r1, =_ebss\n"
        "    mov     r2, #0\n"
        "    .thumb_func\n"
        "zero_loop:\n"
        "        cmp     r0, r1\n"
        "        it      lt\n"
        "        strlt   r2, [r0], #4\n" "        blt     zero_loop");

  /* call the application's entry point. */

Besides the compiler problem I've another question (I didn't find answer in Code::Block manual) - is there a possibility to "integrate" in some way the code from Makefile.include file, that configure all necessary option for compiler depending on TARGET. The reference on this file is included in all custom contiki project. Such thing would grately simplify project making with Code::Blocks (you can see this file in attachement).

Thanks in advance

BlueHazzard · « **Reply #27 on:** January 23, 2015, 12:42:11 pm »

Have you read my post?
If you are using a custom make file, you use c::b only as ide, without the whole build management system...

Quote from: Pavel_47 on January 23, 2015, 12:13:56 pm

It's more clear now. I followed your suggestions and now compilation seems to proceed in right way.
Nevertheless errors occurs ... this time caused by code. I've already posted them on gcc forum, but also repeat it here hoping that someone already faced such cases (please, see the Build log on the image below).
From the core of error message it follows that processor selection is wrong, but I didn't specify any processor in compiler settings.
I founded the code that caused the problem. It's located inside of startup-gcc.c file (the last name in compiler command). Here is this code (extract):

They will have fun on the gcc forum, when you come with this questions. I think your project is clearly miss configured to build smooth, so this is no code error but your configuration error. It seems that contiki is a large project, and that they are using makefiles to build theirs code. So i recommend you (unless you are really willing to go deep in their build system and port it to the c::b build system) to use their build system...

You are in better hands if you go to the contiki forum/mailing list/ chat, and ask how their build system work, and what minimal files you need to use it, and then you can come back and ask us, how you apply this settings in a c::b project...

Quote from: Pavel_47 on January 23, 2015, 12:13:56 pm

Besides the compiler problem I've another question (I didn't find answer in Code::Block manual) - is there a possibility to "integrate" in some way the code from Makefile.include file, that configure all necessary option for compiler depending on TARGET. The reference on this file is included in all custom contiki project. Such thing would grately simplify project making with Code::Blocks (you can see this file in attachement).

I don't think that it is possible to use a make configuration file in the build system of c::b unless you use only make (and so you use c::b ONLY as editor). This two systems are completely different... (maybe you can miss use the pre and post build steps, to set the correct global variables that gcc uses, but i think this is complex, and you really need a deep understanding of the build process, and the code structure of contiki)

As conclusion: I recommend you to use the build system contiki provides you. With this you will be on a fast track of success. If you know more details about the build process you can start to port this to c::b. Anyway this could be great fun, but also great work...

greetings

Pavel_47 · « **Reply #28 on:** January 23, 2015, 01:39:10 pm »

Quote from: BlueHazzard on January 23, 2015, 12:42:11 pm

Have you read my post?

As conclusion: I recommend you to use the build system contiki provides you. With this you will be on a fast track of success. If you know more details about the build process you can start to port this to c::b. Anyway this could be great fun, but also great work...

1. Sure, I've red your post with attention.
2. ... use the build system contiki provides you ... there were exactly the fashion I proceed unless I've tried to make my code more compact ... matches c99 standard, use containers like <vector>, dictionary, etc...
Implementation of these features caused compilation errors. So I addressed to this forum for help.
During followed discussions some experts suggested me to resign custom makefiles if I hope to have assistance on this forum.
That's what I did afterwards ... and faced difficulties.
So here I reform my original question: is it possible to use custom makefile and add some compiler options via Code::Block interface ?
After all some options in Code::Block UI remains active even if I specify custom makefile. Isn't it ?
Othewise how compilation is made if compiler executables aren't specified in the custom makefile ?

To be more close to problem, the compilation of the following code causes error:

Code

    for(int i=0; i < 10; i++)
    {
        printf("Hello, world\n");
    }

Here is built output:

Code

hello-world.c: In function 'process_thread_hello_world_process':
hello-world.c:53:5: error: 'for' loop initial declarations are only allowed in C99 or C11 mode
     for(int i=0; i < 10; i++)
     ^
hello-world.c:53:5: note: use option -std=c99, -std=gnu99, -std=c11 or -std=gnu11 to compile your code
make: *** [hello-world.co] Error 1
../../Makefile.include:234: recipe for target 'hello-world.co' failed
rm obj_cc2538dk/startup-gcc.o
Process terminated with status 2 (0 minute(s), 2 second(s))
2 error(s), 0 warning(s) (0 minute(s), 2 second(s))

Then I've tried to add the suggested option in the following location Compiler settings->Other options (following to some suggestion)
-std=gnu99

Without any effect ...

Thanks in advance

BlueHazzard · « **Reply #29 on:** January 23, 2015, 01:45:45 pm »

can you post your current project file?

Pavel_47 · « **Reply #30 on:** January 23, 2015, 01:57:53 pm »

Thanks a lot BlueHazzard

Here is project file (with custom makefile)

BlueHazzard · « **Reply #31 on:** January 23, 2015, 02:12:11 pm »

With this project you are clearly using a "custom makefile" so you can't use any compiler and build stuff from within c::b.
As far as i know all changes regarding the build process (like adding libraries, or files, add defines) have to be made in the make file. Even the source tree is not take into account (so if you add a .cpp file to the project you have also to add it manually in the make file so it can be build). You have to make ALL on your own in the makefile.

With this process i can't help you. If you go with the custom makefile this is also the wrong forum to ask. You will get more help on the contiki forum. (You have to say that you are using make files, and not the c::b build process, because else they send you back to us

)

As far as i can tell the command line to the make process is called correct, as you specified, so this is no c::b bug, but how you write the TARGET variable. ( i have no idea how you have to specify it that it is right, and i also have not the time to look into it, but i can tell you that the cmd line to make is called as you write it in Project->Build Options->Make Commands)

greetings

stahta01 · « **Reply #32 on:** January 25, 2015, 06:34:54 pm »

Quote from: BlueHazzard on January 23, 2015, 02:12:11 pm

With this project you are clearly using a "custom makefile" so you can't use any compiler and build stuff from within c::b.
As far as i know all changes regarding the build process (like adding libraries, or files, add defines) have to be made in the make file. Even the source tree is not take into account (so if you add a .cpp file to the project you have also to add it manually in the make file so it can be build). You have to make ALL on your own in the makefile.

With this process i can't help you. If you go with the custom makefile this is also the wrong forum to ask. You will get more help on the contiki forum. (You have to say that you are using make files, and not the c::b build process, because else they send you back to us )

As far as i can tell the command line to the make process is called correct, as you specified, so this is no c::b bug, but how you write the TARGET variable. ( i have no idea how you have to specify it that it is right, and i also have not the time to look into it, but i can tell you that the cmd line to make is called as you write it in Project->Build Options->Make Commands)

greetings

I gave that info in the other thread and he decided in that thread to NOT use a custom make file project.

In a few weeks, I might try to see if there is a real problem doing this; but, I do NOT have the time to try it now for someone who seems to be NOT worth the effort to help. Since, I am likely one of the few people who uses custom make file projects on a regular basis and also a longtime CB poster.

Tim S.

Pavel_47 · « **Reply #33 on:** January 25, 2015, 07:05:56 pm »

Quote from: stahta01 on January 25, 2015, 06:34:54 pm

... but, I do NOT have the time to try it now for someone who seems to be NOT worth the effort to help. Since, I am likely one of the few people who uses custom make file projects on a regular basis and also a longtime CB poster.

Tim S.

The GREATEST in the WORLD EXPERT in Code::Blocks, custom makefiles, ets. !!!
Sorry for having troubled you. Thanks a lot for your inestimable support.
Henceworth don't trouble yourself to answer to my questions !!!

News:

Author Topic: Taking into account C99 standard (Read 42193 times)