From 04df4270f0ac6aec360076185363338366475166 Mon Sep 17 00:00:00 2001
From: Pavel Kirienko <pavel.kirienko@gmail.com>
Date: Wed, 7 May 2014 13:56:05 +0400
Subject: Removed the placement new workaround. It seems like we can pull <new>
 from the toolchain's standard includes with no harm.

---
 src/modules/uavcan/module.mk | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

(limited to 'src/modules/uavcan/module.mk')

diff --git a/src/modules/uavcan/module.mk b/src/modules/uavcan/module.mk
index 3966210b5..c91208342 100644
--- a/src/modules/uavcan/module.mk
+++ b/src/modules/uavcan/module.mk
@@ -51,8 +51,7 @@ SRCS += $(LIBUAVCAN_SRC)
 INCLUDE_DIRS += $(LIBUAVCAN_INC)
 EXTRADEFINES += -DUAVCAN_MEM_POOL_BLOCK_SIZE=56 \
                 -DUAVCAN_TOSTRING=0 \
-                -DUAVCAN_CPP_VERSION=UAVCAN_CPP03 \
-                -DUAVCAN_IMPLEMENT_PLACEMENT_NEW=1
+                -DUAVCAN_CPP_VERSION=UAVCAN_CPP03
 
 #
 # libuavcan drivers for STM32
-- 
cgit v1.2.3