lwip-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-users] compiling LWIP 1.3.2 on IAR EWARM 6.0


From: Carol Lai
Subject: [lwip-users] compiling LWIP 1.3.2 on IAR EWARM 6.0
Date: Tue, 6 Mar 2012 10:10:21 -0600

Hi,

 

I’m compiling LWIP 1.3.2 as C++ language in IAR.  But I’m getting the following error message.

 

 

Error[Pe135]: class "tcp_pcb" has no member "lwip_recv" C:\Projects\Plastic\LWIP_Problem\platform\StellarisWare\third_party\lwip-1.3.2\src\core\tcp.c 837

Error[Pe135]: class "tcp_pcb" has no member "lwip_recv" C:\Projects\Plastic\LWIP_Problem\platform\StellarisWare\third_party\lwip-1.3.2\src\core\tcp_in.c 279

Error[Pe135]: class "tcp_pcb" has no member "lwip_recv" C:\Projects\Plastic\LWIP_Problem\platform\StellarisWare\third_party\lwip-1.3.2\src\core\tcp_in.c 324

Error[Pe135]: class "tcp_pcb" has no member "lwip_recv" C:\Projects\Plastic\LWIP_Problem\platform\StellarisWare\third_party\lwip-1.3.2\src\core\tcp_in.c 336

Error[Pe135]: class "tcp_pcb" has no member "lwip_accept" C:\Projects\Plastic\LWIP_Problem\platform\StellarisWare\third_party\lwip-1.3.2\src\core\tcp_in.c 639

Error[Pe055]: too many arguments in invocation of macro "recv" C:\Projects\Plastic\LWIP_Problem\platform\StellarisWare\third_party\lwip-1.3.2\src\core\udp.c 290

Error[Pe135]: class "udp_pcb" has no member "lwip_recv" C:\Projects\Plastic\LWIP_Problem\platform\StellarisWare\third_party\lwip-1.3.2\src\core\udp.c 290

Error while running C/C++ Compiler

 

 

It appears that IAR is not replacing the macro correctly.  Does anyone know how to set them up correctly for IAR compiler?

Thanks,

 

Carol


“This message and any attachments may contain FW Murphy information that is highly confidential, privileged, and exempt from disclosure. Any recipient other than the intended recipient is advised that dissemination, distribution, copying, or other use of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately, plus delete the message and any backups.”

reply via email to

[Prev in Thread] Current Thread [Next in Thread]