From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Correct way to check for clock_gettime()
Date: Mon, 2 Aug 2010 17:14:01 +0200 [thread overview]
Message-ID: <20100802171401.7b9809de@surf> (raw)
In-Reply-To: <20100802051736.GC30548@gmx.de>
Hello Ralf,
Thanks a lot for your feedback!
On Mon, 2 Aug 2010 07:17:36 +0200
Ralf Wildenhues <Ralf.Wildenhues@gmx.de> wrote:
> * Thomas Petazzoni wrote on Mon, Aug 02, 2010 at 03:33:53AM CEST:
> > So the ability of sharing the cache between execution of
> > different configure scripts is a documented feature. Is it just
> > that in reality it doesn't work that well ?
>
> You should be able to modify both configure scripts in a way so that
> it works again; and in this particular example it should be done.
> Getting this approach to scale can be a lot of work though.
Is this approach "officially" supported by autoconf ? If I fix one of
the configure.{in,ac} script and try to get the change merged upstream,
it's an important argument to know if the change is done to comply with
a general rule of configure.{in,ac} and not a specific hack.
Moreover, as Steffen asked later in the thread, in the particular case
I've presented in the original mail of this thread, what would be the
correct fix ?
I have also other cases of configure cache misuse by two independent
packages. I'm often able to track down the cause of the problem, but
I'm not autoconf-ed enough to know which is the correct fix. May I
present those other cases to the list ?
Thanks again for your inputs,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-08-02 15:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 11:51 [Buildroot] Correct way to check for clock_gettime() Thomas Petazzoni
[not found] ` <AANLkTi=7t2kQXj96nktqEd=T3zDOvBXQDrjXW+u7FpG0@mail.gmail.com>
2010-08-02 1:33 ` Thomas Petazzoni
[not found] ` <20100802051736.GC30548@gmx.de>
2010-08-02 15:14 ` Thomas Petazzoni [this message]
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=20100802171401.7b9809de@surf \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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