All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Thomas Huth <thuth@redhat.com>,
	Laurent Vivier <laurent@vivier.eu>,
	Wainer dos Santos Moschetta <wainersm@redhat.com>
Subject: Re: [PATCH] gitlab-ci: Test building linux-user targets on CentOS 7
Date: Thu, 21 Jan 2021 14:14:08 +0100	[thread overview]
Message-ID: <59ac8f67-4e8b-f308-1308-497df09a1363@amsat.org> (raw)
In-Reply-To: <20210121121505.1523156-1-f4bug@amsat.org>

On 1/21/21 1:15 PM, Philippe Mathieu-Daudé wrote:
> Add a configuration tested by Peter Maydell (see [1] and [2])
> but not covered in our CI [3]:
> 
>   [705/2910] Compiling C object libqemu-arm-linux-user.fa.p/linux-user_strace.c.o
>   FAILED: libqemu-arm-linux-user.fa.p/linux-user_strace.c.o
>   ../linux-user/strace.c: In function 'do_print_sockopt':
>   ../linux-user/strace.c:2831:14: error: 'IPV6_ADDR_PREFERENCES' undeclared (first use in this function)
>            case IPV6_ADDR_PREFERENCES:
>                 ^
> 
> [1] https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg05086.html
> [2] https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg05379.html
> [3] https://gitlab.com/philmd/qemu/-/jobs/977408284:
> 
> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> ---
>  .gitlab-ci.yml | 7 +++++++
>  1 file changed, 7 insertions(+)

> +build-user-centos7:
> +  <<: *native_build_job_definition
> +  variables:
> +    IMAGE: centos7
> +    CONFIGURE_ARGS: --disable-system --disable-tools --disable-docs
> +    MAKE_CHECK_ARGS: check-tcg

check-tcg calls build-tcg which fails:

  BUILD   TCG tests for x86_64-softmmu
  BUILD   x86_64-softmmu guest-tests with cc
/usr/bin/ld: hello: warning: allocated section `.notes' not in segment
/usr/bin/ld: memory: warning: allocated section `.notes' not in segment
  BUILD   TCG tests for x86_64-linux-user
  BUILD   x86_64-linux-user guest-tests with cc
/usr/bin/ld: cannot find -lpthread
/usr/bin/ld: cannot find -lc
collect2: error: ld returned 1 exit status
make[2]: *** [threadcount] Error 1
make[1]: *** [cross-build-guest-tests] Error 2
make: *** [build-tcg-tests-x86_64-linux-user] Error 2

Apparently this is due to the -static flag:

$ gcc  -Wall -Werror -O0 -g -fno-strict-aliasing -m64
tests/tcg/multiarch/threadcount.c -o threadcount  -static -lpthread
/usr/bin/ld: cannot find -lpthread
/usr/bin/ld: cannot find -lc
collect2: error: ld returned 1 exit status

Do we need to install these packages?

glibc-static.i686 : C library static libraries for -static linking.
glibc-static.x86_64 : C library static libraries for -static linking.

Or simply ignore testing?

Thanks,

Phil.


  parent reply	other threads:[~2021-01-21 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 12:15 [PATCH] gitlab-ci: Test building linux-user targets on CentOS 7 Philippe Mathieu-Daudé
2021-01-21 12:18 ` Daniel P. Berrangé
2021-01-21 13:14 ` Philippe Mathieu-Daudé [this message]
2021-01-21 14:01   ` Thomas Huth
2021-01-21 18:24     ` Philippe Mathieu-Daudé

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=59ac8f67-4e8b-f308-1308-497df09a1363@amsat.org \
    --to=f4bug@amsat.org \
    --cc=alex.bennee@linaro.org \
    --cc=laurent@vivier.eu \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wainersm@redhat.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 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.