All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk-Jan C. Binnema <djcb.bulk@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] build: use -lrt for clock_gettime on glibc < 2.17
Date: Tue, 10 Sep 2013 10:20:32 +0300	[thread overview]
Message-ID: <87fvtdp2gv.fsf@djcbsoftware.nl> (raw)
In-Reply-To: <4A735792-B4D7-468A-A61A-488F605AAB30@holtmann.org>


marcel@holtmann.org writes:

> Hi Dirk-Jan,
>

<snip>

>
> so I fixed this upstream a lot simpler by always checking for
> clock_gettime in -lrt. Can you check if that works for you. On an
> older Debian test box it just works fine for me.

Sure, that works; but that's equivalent to the first patch I made... I
only made the more complicated one after your comment:

,----
| > +AC_SEARCH_LIBS(clock_gettime,rt)
|
| I do [not] like this since this now it links everything with -lrt even if it
| is not needed.
`----

AC_SEARCH_LIBS doesn't add -lrt if it's not needed, so I interpreted
your comment as you not wanting -lrt in parts of the code that don't
need it.

Anyway, good it works now...

Thanks,
Dirk.

-- 
Dirk-Jan C. Binnema                  Helsinki, Finland
e:djcb@djcbsoftware.nl           w:www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C

  parent reply	other threads:[~2013-09-10  7:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-06  6:43 [PATCH] build: use -lrt for clock_gettime on glibc < 2.17 Dirk-Jan C. Binnema
     [not found] ` <52E3B66B-DC7A-4225-8779-8C1E9B0FC15E@holtmann.org>
2013-09-06  8:07   ` Dirk-Jan C. Binnema
2013-09-06  8:09   ` Dirk-Jan C. Binnema
     [not found]     ` <4A735792-B4D7-468A-A61A-488F605AAB30@holtmann.org>
2013-09-10  7:20       ` Dirk-Jan C. Binnema [this message]
2013-09-10  7:55     ` Johan Hedberg

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=87fvtdp2gv.fsf@djcbsoftware.nl \
    --to=djcb.bulk@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.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 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.