-
Notifications
You must be signed in to change notification settings - Fork 119
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pktgen-port-cfg.c involves a formatting issue in a printf-like output statement. #261
Comments
On my Ubuntu 24.04 LTS and Pktgen I do not see this error. I am compiling for x86_64 machine what is the OS used and the type of machine building pktgen? |
This error is present in Ubuntu 22.04 LTS. I made it work by modifying the formatting, exactly according to the error. |
My OS is: Ubuntu 22.04.3 LTS and the machine type is x86_64 Now,I have another question,I need to cross-compile for aarch64 machine ,How can I do it? The following are the operation steps:
pktgen 24.05.4 User defined options Found ninja-1.10.1 at /usr/bin/ninja |
Not going to be much help here as I only compile for x86_64. It appears |
The problem pktgen-port-cfg.c regarding a formatting problem in a printf-like output statement has not been resolved yet .
Environment:
Pktgen-DPDK$ cat VERSION
24.05.4
../app/pktgen-port-cfg.c:168:34: error: format ‘%ld’ expects argument of type ‘long int’, but argument 3 has type ‘int’ [-Werror=format=] 168 | pktgen_log_panic("Unable to allocate %ld pkt_seq_t headers", NUM_TOTAL_PKTS); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~ | | | int ../app/pktgen-port-cfg.c:168:17: note: in expansion of macro ‘pktgen_log_panic’ 168 | pktgen_log_panic("Unable to allocate %ld pkt_seq_t headers", NUM_TOTAL_PKTS); | ^~~~~~~~~~~~~~~~ ../app/pktgen-port-cfg.c:168:56: note: format string is defined here 168 | pktgen_log_panic("Unable to allocate %ld pkt_seq_t headers", NUM_TOTAL_PKTS); | ~~^ | | | long int | %d cc1: all warnings being treated as errors [4/5] Compiling C object app/pktgen.p/pktgen.c.o
The text was updated successfully, but these errors were encountered: