From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] hugemmap01 warnings with -i [was Re: LTP compilation broken with -fno-common]
Date: Wed, 15 Apr 2020 12:19:55 +0200 [thread overview]
Message-ID: <20200415101955.GA21676@dell5510> (raw)
In-Reply-To: <CAEemH2fo2HOsgrS7q8s3gr5-BdLfO530f0WGszDDWmpw_V=KOg@mail.gmail.com>
Hi Li,
> After building LTP with CFLAGS="-fno-common" locally, I just find more
> places that need to do the same improvement.
> ltp/testcases/kernel/controllers/libcontrollers/libcontrollers.h:56:
> multiple definition of `num_line'
> ltp/lib/../include/tst_hugepage.h:16: multiple definition of `Hopt'
> Sorry for involving the definition in tst_hugetlb.h without 'extern' issue
> many hours ago. It'd be appreciated if you can fix them together in your
> coming patch.
BTW that's a fix 156f91396 ("hugetlb: move nr_opt to tst_hugepage.h")
I haven't checked whether -i worked without warning before, but not it
produces it:
./hugemmap01 -s 2 -i 2
tst_hugepage.c:48: INFO: 2 hugepage(s) reserved
tst_test.c:1244: INFO: Timeout per run is 0h 05m 00s
hugemmap01.c:61: PASS: call succeeded
hugemmap01.c:61: PASS: call succeeded
hugemmap01.c:69: WARN: Number of HUGEPAGES_FREE stayed the same. Okay if multiple copies running due to test collision.
Kind regards,
Petr
next prev parent reply other threads:[~2020-04-15 10:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 8:32 [LTP] LTP compilation broken with -fno-common Petr Vorel
2020-04-01 9:16 ` Richard Palethorpe
2020-04-01 9:39 ` Cyril Hrubis
2020-04-01 9:55 ` Martin Doucha
2020-04-01 9:58 ` Cyril Hrubis
2020-04-01 10:04 ` Martin Doucha
2020-04-01 10:15 ` Petr Vorel
2020-04-01 10:50 ` Cyril Hrubis
2020-04-01 11:42 ` Martin Doucha
2020-04-01 12:01 ` Cyril Hrubis
2020-04-01 10:14 ` Petr Vorel
2020-04-09 7:45 ` Petr Vorel
2020-04-09 9:18 ` Cyril Hrubis
2020-04-09 10:06 ` Li Wang
2020-04-15 7:00 ` Petr Vorel
2020-04-15 10:19 ` Petr Vorel [this message]
2020-04-16 9:13 ` [LTP] hugemmap01 warnings with -i [was Re: LTP compilation broken with -fno-common] Li Wang
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=20200415101955.GA21676@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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.