From: Tobias Burnus <tobias@codesourcery.com>
To: Nick Clifton <nickc@redhat.com>,
Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
Binutils <binutils@sourceware.org>
Subject: Re: Build issues due to patch "gprofng: a new GNU profiler" – CLOCK_MONOTONIC_RAW not defined
Date: Tue, 15 Mar 2022 17:24:11 +0100 [thread overview]
Message-ID: <0d4bbabb-c123-f77e-ccf0-45a611acc4f1@codesourcery.com> (raw)
In-Reply-To: <14359283-a893-7208-c87d-c42aad214c67@redhat.com>
Hi Nick,
On 15.03.22 16:24, Nick Clifton wrote:
> To save time I have gone ahead and applied a patch myself (attached).
> Please let me know if I missed anything or made a mistake...
Thanks for the commit – but it fails for
libtool: link: x86_64-linux-gnu-g++ -Wall -pthread -Wno-switch -Wno-format-truncation
-g -O2 -static-libstdc++ -static-libgcc
-o gp-display-text gp-display-text.o ipc.o ipcio.o
-L...
./.libs/libgprofng.a .../bfd/.libs/libbfd.a -lz -liberty -ldl -pthread
with
.../bin/ld: ./.libs/libgprofng.a(gethrtime.o): in function `gethrvtime':
obj/binutils-src-mainline-0-x86_64-none-linux-gnu-x86_64-linux-gnu/gprofng/src/gethrtime.c:131: undefined reference to `clock_gettime'
.../bin/ld: ./.libs/libgprofng.a(gethrtime.o): in function `gethrtime':
obj/binutils-src-mainline-0-x86_64-none-linux-gnu-x86_64-linux-gnu/gprofng/src/gethrtime.c:162: undefined reference to `clock_gettime'
collect2: error: ld returned 1 exit status
Thus, it works for libcollector – but not for libgprofng / gp-display-text.
From the build dir:
libcollector/Makefile:CLOCK_GETTIME_LINK = -lrt
libcollector/Makefile:libgp_collector_la_LIBADD = $(CLOCK_GETTIME_LINK)
libcollector/config.log:CLOCK_GETTIME_LINK='-lrt'
libcollector/config.status:S["CLOCK_GETTIME_LINK"]="-lrt"
Thanks for looking into build issue,
Tobias
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
next prev parent reply other threads:[~2022-03-15 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 10:57 Tobias Burnus
2022-03-14 18:16 ` Vladimir Mezentsev
2022-03-15 15:24 ` Nick Clifton
2022-03-15 16:24 ` Tobias Burnus [this message]
2022-03-16 12:29 ` Nick Clifton
2022-03-16 14:55 ` Tobias Burnus
2022-03-18 15:25 ` Tobias Burnus
2022-03-18 15:47 ` Nick Clifton
2022-03-15 16:54 ` Vladimir Mezentsev
2022-03-15 16:59 ` Vladimir Mezentsev
2022-03-16 7:56 ` Tobias Burnus
2022-03-14 20:53 ` Joseph Myers
2022-03-14 21:52 ` Vladimir Mezentsev
2022-03-16 11:30 ` 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=0d4bbabb-c123-f77e-ccf0-45a611acc4f1@codesourcery.com \
--to=tobias@codesourcery.com \
--cc=binutils@sourceware.org \
--cc=nickc@redhat.com \
--cc=vladimir.mezentsev@oracle.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 read-only IMAP folder(s) and NNTP newsgroup(s).