public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Tobias Burnus <tobias@codesourcery.com>
To: Vladimir Mezentsev <vladimir.mezentsev@oracle.com>,
	Nick Clifton <nickc@redhat.com>,
	Binutils <binutils@sourceware.org>
Subject: Re: Build issues due to patch "gprofng: a new GNU profiler" – CLOCK_MONOTONIC_RAW not defined
Date: Wed, 16 Mar 2022 08:56:04 +0100	[thread overview]
Message-ID: <6273bc3c-10df-b2e0-66e0-f002f448eb99@codesourcery.com> (raw)
In-Reply-To: <dd6d002d-278b-f2a6-060d-d81ef21bc95e@oracle.com>

Hi Nick & Vladimir, hello all,

I still get the following, which I think I missed before because it
first already failed in gprofng/libcollector/ – and my last build was
on a slightly newer system which still required -lrt but did provide
CLOCK_MONOTONIC_RAW:

.../gprofng/src/gethrtime.c: In function 'gethrtime':
.../gprofng/src/gethrtime.c:162:26: error: 'CLOCK_MONOTONIC_RAW' undeclared (first use in this fun
ction); did you mean 'CLOCK_MONOTONIC'?
    int r = clock_gettime (CLOCK_MONOTONIC_RAW, &tp);
                           ^~~~~~~~~~~~~~~~~~~

Thanks - and I am sure we have almost fixed everything :-)

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

  parent reply	other threads:[~2022-03-16  7:56 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
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 [this message]
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=6273bc3c-10df-b2e0-66e0-f002f448eb99@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).