Quantcast

No clue for thsi....

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

No clue for thsi....

Kees Schoenmakers
Hi All,

I have a software project that builds fine met mspgcc (4.7.0)

I installed the toolkit via the T.I. site, modified the Makefile to
reflect this compiler and support files, Trying to build gives a long
list of messages, Here I snipped from the top.

=========================================
/opt/ti/gcc/bin/msp430-elf-gcc -c Harttimers.c -g
-I/opt/ti/support/include -Wstrict-prototypes -Wunused  -fno-inline
-fno-builtin-memset  -fno-builtin-memcpy -Wextra -fms-extensions
-mmcu=msp430f449 -O2 -Wall -Wno-old-style-declaration  -std=c99
In file included from /opt/ti/support/include/msp430f449.h:70:0,
                 from /opt/ti/support/include/msp430.h:367,
                 from Mainapp.h:23,
                 from Harttimers.c:17:
/opt/ti/support/include/iomacros.h:49:53: error: expected '=', ',',
';', 'asm' or '__attribute__' before 'asm'
 #define sfrb_(x,x_) extern volatile unsigned char x asm(#x_)
                                                     ^
/opt/ti/support/include/iomacros.h:57:20: note: in expansion of macro 'sfrb_'
 #define sfrb(x,x_) sfrb_(x,x_)
                    ^
/opt/ti/support/include/msp430f449.h:147:1: note: in expansion of macro 'sfrb'
 sfrb(IE1, IE1_);
 ^
/opt/ti/support/include/iomacros.h:49:53: error: expected '=', ',',
';', 'asm' or '__attribute__' before 'asm'
 #define sfrb_(x,x_) extern volatile unsigned char x asm(#x_)
                                                     ^
/opt/ti/support/include/iomacros.h:57:20: note: in expansion of macro 'sfrb_'
 #define sfrb(x,x_) sfrb_(x,x_)
                    ^
/opt/ti/support/include/msp430f449.h:157:1: note: in expansion of macro 'sfrb'
 sfrb(IFG1, IFG1_);
 ^
/opt/ti/support/include/iomacros.h:49:53: error: expected '=', ',',
';', 'asm' or '__attribute__' before 'asm'
 #define sfrb_(x,x_) extern volatile unsigned char x asm(#x_)
                                                     ^
/opt/ti/support/include/iomacros.h:57:20: note: in expansion of macro 'sfrb_'
 #define sfrb(x,x_) sfrb_(x,x_)
                    ^
/opt/ti/support/include/msp430f449.h:166:1: note: in expansion of macro 'sfrb'
 sfrb(ME1, ME1_);
 ^
==============================

Which wise soul can enlighten me here.

Kees

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No clue for thsi....

DJ Delorie

> -mmcu=msp430f449 -O2 -Wall -Wno-old-style-declaration  -std=c99

By specifying "-std=c99" you have disabled all the GNU extensions, including "asm".

Try --std=gnuc99 instead, or replace "asm" with "__asm__" in those headers.

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No clue for thsi....

Kees Schoenmakers
On 9/15/14, DJ Delorie <[hidden email]> wrote:
>
>> -mmcu=msp430f449 -O2 -Wall -Wno-old-style-declaration  -std=c99
>
> By specifying "-std=c99" you have disabled all the GNU extensions, including
> "asm".
>
> Try --std=gnuc99 instead, or replace "asm" with "__asm__" in those headers.
>
Thank you, I'll try.

Kees

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: No clue for thsi....

Peter Bigot-4
In reply to this post by DJ Delorie
On Mon, Sep 15, 2014 at 1:57 AM, DJ Delorie <[hidden email]> wrote:
>
>> -mmcu=msp430f449 -O2 -Wall -Wno-old-style-declaration  -std=c99
>
> By specifying "-std=c99" you have disabled all the GNU extensions, including "asm".
>
> Try --std=gnuc99 instead, or replace "asm" with "__asm__" in those headers.

DJ is entirely correct here.  To make it more clear, the file in which
these bare asm occur is the iomacros.h from TI's header distribution.
mspgcc's version of that file used the __asm__ syntax.

TI would need to fix this or it'll break again on the next update.

Peter

------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Mspgcc-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
Loading...