strange ERROR
I get this error while compiling in gCC
Code:error: expected â:â, â,â, â;â, â}â or â__attribute__â before â=â token the error occurs at below line CH_FREQ_MAP CH_HZ_ID_MAP[]= { {1, 2412}, {2, 2417}, {3, 2422}, {4, 2427}, {5, 2432}, {6, 2437}, {7, 2442}, {8, 2447}, {9, 2452}, {10, 2457}, {11, 2462}, {12, 2467}, {13, 2472}, {14, 2484}, };
I could be wrong here, but try removing the final , after
Code:{14, 2484}, //TRY REMOVING THIS COMMA,
I suggest that you also post the code before the snippet of code that you posted.Originally Posted by leo2008
The trailing comma should be fine in this case.
Look up a C++ Reference and learn How To Ask Questions The Smart Way
I tried it still gives the same error.
You already have a thread on the same thing and you have been told repeatedly nobody can help you without complete code. Yet, you continue to post extracts of ambiguous error messages followed by what "YOU THINK" is where the problem is.
1. Get rid of gets(). Never ever ever use it again. Replace it with fgets() and use that instead.
2. Get rid of void main and replace it with int main(void) and return 0 at the end of the function.
3. Get rid of conio.h and other antiquated DOS crap headers.
4. Don't cast the return value of malloc, even if you always always always make sure that stdlib.h is included.
Well having looked at your IP address, I'm rather of the opinion that you've just started work at a new company (possibly your first job) and you're hopelessly out of your depth.
Looking at your post history here (from years ago), I see
One post on Win32 gui for win32 c++ programming
One post on GUI in Linux GUI using C in LINUX
And a handful of C# threads.
None of this would in any way prepare you for Linux kernel driver hacking.
fxr.watson.org: linux-2.6 sys/drivers/staging/rt3090/common/rt_channel.c
Now whilst you may eventually stumble towards making it compile, you can be pretty sure that you will have broken something along the way.
Now if you think getting a driver to compile was hard, just wait until you try to debug the damn thing!
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
ouch!
