From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [DPDK/examples Bug 1530] examples/vm_power_manager fails to build on aarch64 with gcc14
Date: Fri, 30 Aug 2024 07:45:06 +0000 [thread overview]
Message-ID: <bug-1530-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1530
Bug ID: 1530
Summary: examples/vm_power_manager fails to build on aarch64
with gcc14
Product: DPDK
Version: 22.11
Hardware: ARM
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: examples
Assignee: dev@dpdk.org
Reporter: guillaume.gardet@arm.com
Target Milestone: ---
examples/vm_power_manager fails to build with gcc14 on openSUSE Tubmleweed
aarch64.
Compiler version:
gcc (SUSE Linux) 14.2.0
Build error:
../examples/vm_power_manager/guest_cli/vm_power_cli_guest.c: In function
‘cmd_query_freq_list_parsed’:
../examples/vm_power_manager/guest_cli/vm_power_cli_guest.c:207:42: error:
implicit declaration of function ‘strtol’; did you mean ‘strtok’?
[-Wimplicit-function-declaration]
207 | lcore_id = (unsigned int)strtol(res->cpu_num, &ep,
10);
| ^~~~~~
| strtok
Adding the missing stdlib.h header fixes the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 3176 bytes --]
reply other threads:[~2024-08-30 7:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-1530-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.