<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>On 31/03/2020 11:56, Chris Johns wrote:<br>
</p>
<blockquote type="cite"
cite="mid:9a9b12b3-ba81-e52e-b65c-7ae619f8d2a5@rtems.org">On
2020-03-31 19:57, Moyano, Gabriel wrote:
<br>
<blockquote type="cite" style="color: #000000;">diff --git
a/testsuite/arphole/test_main.c b/testsuite/arphole/test_main.c
<br>
index 19d67b89..45a28cc0 100644
<br>
--- a/testsuite/arphole/test_main.c
<br>
+++ b/testsuite/arphole/test_main.c
<br>
@@ -54,6 +54,7 @@
<br>
#include <rtems/bsd/util.h>
<br>
#define TEST_NAME "LIBBSD ARP HOLE"
<br>
+#define TEST_STATE_USER_INPUT 1
<br>
</blockquote>
<br>
In rtems.git these test states are defined on the compiler command
line. The user input state is OK to define in the code but it gets
more difficult with the others to manage them in the code and so I
am wondering how we manage the other states in libbsd? And if we
manage those in the build system then why manage this one?
</blockquote>
<p>Why should this define move to the build system of libbsd. It is
a property of the test if it is interactive or not.</p>
<p>In RTEMS we have it in the build system since you can set tests
to expected fail or disable them per BSP. I am not sure if we need
this extra complexity for libbsd right now. We could at some point
in time use the same build system for RTEMS and libbsd.<br>
</p>
</body>
</html>