From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Yong Huang <yong.huang@smartx.com>,
Fabiano Rosas <farosas@suse.de>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3 0/5] Guestperf: miscellaneous refinement and enrichment
Date: Tue, 3 Dec 2024 08:10:51 +0000 [thread overview]
Message-ID: <Z06866qR0z9n2BgP@redhat.com> (raw)
In-Reply-To: <Z04PTe4kCVWEQbPL@x1n>
On Mon, Dec 02, 2024 at 02:49:33PM -0500, Peter Xu wrote:
> On Sat, Nov 30, 2024 at 10:01:43PM +0800, Yong Huang wrote:
> > On Fri, Nov 29, 2024 at 9:44 PM Fabiano Rosas <farosas@suse.de> wrote:
> For the stress.c warnings/error, I saw another one warning with gcc when
> built it locally, then I found Fabiano's CI run also has it:
>
> https://gitlab.com/farosas/qemu/-/jobs/8504697347
>
> Which has:
>
> [3381/3611] Linking target tests/migration/stress
> /usr/bin/ld: /usr/lib64/libglib-2.0.a(gutils.c.o): in function `g_get_user_database_entry':
> (.text+0xeb): warning: Using 'getpwnam_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linkign
> /usr/bin/ld: (.text+0x2be): warning: Using 'getpwuid' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
> /usr/bin/ld: (.text+0x134): warning: Using 'getpwuid_r' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
>
> Feel free to look at it too if you like. Nothing should be relevant to your
> changes, so I think it could be there for a while when compilers upgrade.
Those messages are mostly harmless, especially in the stress scenario, and
can't practically be eliminated:
https://gitlab.gnome.org/GNOME/glib/-/issues/2019
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-12-03 8:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 2:14 [PATCH v3 0/5] Guestperf: miscellaneous refinement and enrichment yong.huang
2024-10-22 2:14 ` [PATCH v3 1/5] tests/migration: Move the guestperf tool to scripts directory yong.huang
2024-10-22 6:04 ` Prasad Pandit
2024-10-22 2:14 ` [PATCH v3 2/5] tests/migration: Make initrd-stress.img built by default yong.huang
2024-10-22 2:14 ` [PATCH v3 3/5] guestperf: Support deferred migration for multifd yong.huang
2024-10-22 2:14 ` [PATCH v3 4/5] guestperf: Nitpick the inconsistent parameters yong.huang
2024-10-22 2:14 ` [PATCH v3 5/5] guestperf: Introduce multifd compression option yong.huang
2024-10-23 15:05 ` [PATCH v3 0/5] Guestperf: miscellaneous refinement and enrichment Fabiano Rosas
2024-10-24 2:06 ` Yong Huang
2024-10-24 12:28 ` Peter Xu
2024-11-29 10:08 ` Yong Huang
2024-11-29 12:27 ` Fabiano Rosas
2024-11-29 13:44 ` Fabiano Rosas
2024-11-30 14:01 ` Yong Huang
2024-12-02 19:49 ` Peter Xu
2024-12-03 8:10 ` Daniel P. Berrangé [this message]
2024-12-03 12:20 ` Fabiano Rosas
2024-12-03 12:30 ` Daniel P. Berrangé
2024-12-03 13:15 ` Fabiano Rosas
2024-12-03 17:40 ` Peter Xu
2024-12-09 2:50 ` Yong Huang
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=Z06866qR0z9n2BgP@redhat.com \
--to=berrange@redhat.com \
--cc=farosas@suse.de \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yong.huang@smartx.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).