Bug 471 - failing to build test from app/test
Summary: failing to build test from app/test
Status: RESOLVED DUPLICATE of bug 465
Alias: None
Product: DPDK
Classification: Unclassified
Component: other (show other bugs)
Version: 20.05
Hardware: x86 Linux
: Normal critical
Target Milestone: ---
Assignee: dev
URL:
Depends on:
Blocks:
 
Reported: 2020-05-13 10:24 CEST by Vipin Varghese
Modified: 2020-05-13 10:43 CEST (History)
1 user (show)



Attachments

Description Vipin Varghese 2020-05-13 10:24:16 CEST
DPDK:20.05-rc2
Linux:4.15.0-99-generic 
GCC: Ubuntu 7.5.0-3ubuntu1~18.04
Distribution: Ubuntu 18.04.4 LTS

Steps:
1. fetch from git the right version of DPDK.
2. default build for `x86_64-native-linuxapp-gcc`
3. move to the directory `$RTE_SDK/app/test`
4. execute make

Error Log:
```
t# make
  CC commands.o
commands.c: In function ‘cmd_dump_parsed’:
commands.c:137:3: error: ‘rte_malloc_dump_heaps’ is deprecated: Symbol is not yet part of stable ABI [-Werror=deprecated-declarations]
   rte_malloc_dump_heaps(stdout);
   ^~~~~~~~~~~~~~~~~~~~~
In file included from commands.c:31:0:
/home/saesrv02/Downloads/dpdksrc/dpdk/x86_64-native-linuxapp-gcc/include/rte_malloc.h:524:1: note: declared here
 rte_malloc_dump_heaps(FILE *f);
 ^~~~~~~~~~~~~~~~~~~~~
commands.c: At top level:
cc1: error: unrecognized command line option ‘-Wno-address-of-packed-member’ [-Werror]
cc1: all warnings being treated as errors
/home/saesrv02/Downloads/dpdksrc/dpdk/mk/internal/rte.compile-pre.mk:114: recipe for target 'commands.o' failed
make: *** [commands.o] Error 1

```
Comment 1 David Marchand 2020-05-13 10:27:16 CEST
Please, do not jump in app/test directory, prefer the make app/test_sub from the dpdk root directory.

*** This bug has been marked as a duplicate of bug 465 ***
Comment 2 Vipin Varghese 2020-05-13 10:33:05 CEST
If I run from the target folder `make test`

```
# make test
/home/saesrv02/Downloads/dpdksrc/dpdk/x86_64-native-linuxapp-gcc/app/test -c f
Running tests with 4 workers

Test name                     Test result                     Test    Total
================================================================================
Skipped autotests:
dump_physmem:                 Skipped [Not compiled]       [00m 00s]
dump_memzone:                 Skipped [Not compiled]       [00m 00s]
dump_struct_sizes:            Skipped [Not compiled]       [00m 00s]
dump_mempool:                 Skipped [Not compiled]       [00m 00s]
dump_malloc_stats:            Skipped [Not compiled]       [00m 00s]
dump_devargs:                 Skipped [Not compiled]       [00m 00s]
dump_log_types:               Skipped [Not compiled]       [00m 00s]
dump_ring:                    Skipped [Not compiled]       [00m 00s]

Cycles autotest:              Fail                         [00m 01s][00m 02s]
EAL flags autotest:           Fail                         [00m 02s][00m 05s]
Read/write lock autotest:     Fail [Timeout]               [00m 10s][00m 13s]
Alarm autotest:               Fail                         [00m 00s][00m 37s]
PMD ring autotest:            Fail                         [00m 00s][00m 55s]
Link bonding autotest:        Fail                         [00m 00s][01m 11s]
Link bonding mode4 autotest:  Fail                         [00m 00s][01m 12s]
Link bonding rssconf autotest:Fail                         [00m 00s][01m 12s]

```

1. should not for Link-Bond test either use `vdev` or `Skip` rather than failing if the desired number of ports is not available?

2. why would `EAL, Alarm, Lock` fail as it is the library and not PMD?
Comment 3 Vipin Varghese 2020-05-13 10:33:35 CEST
Hi David,

In my enviroment, it fails for EAL, Alarms and Link Bonding
Comment 4 David Marchand 2020-05-13 10:36:48 CEST
"make app/test_sub"
You might have to set your build directory with O=
"make app/test_sub O=x86_64-native-linuxapp-gcc"

The errors on make test are something else.
Comment 5 Vipin Varghese 2020-05-13 10:40:42 CEST
is the test cases (shared below) expected to fail

```
Cycles autotest:              Fail                         [00m 01s][00m 02s]
EAL flags autotest:           Fail                         [00m 02s][00m 05s]
Read/write lock autotest:     Fail [Timeout]               [00m 10s][00m 13s]
Alarm autotest:               Fail                         [00m 00s][00m 37s]
PMD ring autotest:            Fail                         [00m 00s][00m 55s]
Link bonding autotest:        Fail                         [00m 00s][01m 11s]
Link bonding mode4 autotest:  Fail                         [00m 00s][01m 12s]
Link bonding rssconf autotest:Fail                         [00m 00s][01m 12s]
```

I have 2 interfaces for DPDK
```
pci@0000:08:00.0              network        Ethernet Controller X710 for 10GbE SFP+
pci@0000:08:00.1              network        Ethernet Controller X710 for 10GbE SFP+
```

Is there documentation in sample application or getting started which calls out what to ignore safely?
Comment 6 David Marchand 2020-05-13 10:41:54 CEST
This has nothing to do with the problem reported earlier.
Please open a new bug if you think it is necessary or use the mailing list.
Thanks.

*** This bug has been marked as a duplicate of bug 465 ***
Comment 7 Vipin Varghese 2020-05-13 10:43:07 CEST
ok thanks I will

Note You need to log in before you can comment on or make changes to this bug.