public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>
To: Binutils <binutils@sourceware.org>
Subject: Re: [TCWG CI] Regression caused by binutils: gprofng: a new GNU profiler
Date: Tue, 15 Mar 2022 11:17:06 -0700	[thread overview]
Message-ID: <f9726299-c2f3-ccc4-1542-641eb59c17c1@oracle.com> (raw)
In-Reply-To: <912418957.1151.1647354660199@jenkins.jenkins>



On 3/15/22 07:30, ci_notify@linaro.org wrote:
> [TCWG CI] Regression caused by binutils: gprofng: a new GNU profiler:
> commit bb368aad297fe3ad40cf397e6fc85aa471429a28
> Author: Vladimir Mezentsev<vladimir.mezentsev@oracle.com>
>
>      gprofng: a new GNU profiler
>
> Results regressed to
> # reset_artifacts:
> -10
> # true:
> 0
> # First few build errors in logs:
> # 00:00:21 configure: error: Cannot set --enable-shared for gprofng/libcollector.
> # 00:00:21 configure: error: /home/tcwg-buildslave/workspace/tcwg_gnu_7/abe/snapshots/binutils.git~master/gprofng/libcollector/configure failed for libcollector
> # 00:00:21 checking for getpagesize... make[1]: *** [Makefile:7723: configure-gprofng] Error 1
> # 00:00:32 make: *** [Makefile:1001: all] Error 2

In gprofng/libcollector, we need to generate the shared libraries:
% cat -n gprofng/libcollector/configure.ac
...
     35    LT_INIT
     36    AC_ENABLE_SHARED
     37    AC_DISABLE_STATIC
     38
     39    if test "$enable_shared" != "yes"; then
     40      AC_MSG_ERROR([Cannot set --enable-shared for 
gprofng/libcollector.])
     41    fi
     42
...


But it is so late to turn off the gprofng build.

Is there an easy way to find out if shared libraries are not supported ?
I want to know this in gprofng/configure.ac


Thank you,
-Vladimir


       reply	other threads:[~2022-03-15 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <912418957.1151.1647354660199@jenkins.jenkins>
2022-03-15 18:17 ` Vladimir Mezentsev [this message]
2022-03-21 14:41   ` Nick Alcock

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=f9726299-c2f3-ccc4-1542-641eb59c17c1@oracle.com \
    --to=vladimir.mezentsev@oracle.com \
    --cc=binutils@sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).