Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] autoconf caching
Date: Thu, 5 Jun 2014 20:57:46 +0200	[thread overview]
Message-ID: <20140605185746.GC3553@free.fr> (raw)
In-Reply-To: <CAE9DZURFSJhZ5+1PGYTyLwtCRkaYOWU_nNbkti6SDjdJ1-LuDQ@mail.gmail.com>

Dallas, All,

On 2014-06-05 12:39 -0500, Dallas Clement spake thusly:
> Maybe there is hope if the
> autotools people can figure out a way to provide a unique namespace for
> each package and variables.

That's not really the responsibility of the autotools folks.

Say I write a pacakge that uses ac_cv_has_gstreamer which for my pckage
means "gst-inspect is present".

Now you have no knowledge of my package, and you write your own package
that uses ac_cv_has_gstreamer which would mean "libgstreamer.so.0 is
present and usable".

There is no reconciliation possible betwen your package and mine. That's
not the fault of the autotools. Maybe we could say that it's the fault
of gstreamer to not provide the adequate macros, but even if that was
the case, that would not prevent two packages to use the same variable
to represent two different things (think optinal behaviour depending on
the environment for a package, while another would use it to represent
a user-selectable --enable/disable option).

There's no way out of this mess...

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2014-06-05 18:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 16:34 [Buildroot] autoconf caching Dallas Clement
2014-06-05 17:05 ` Baruch Siach
2014-06-05 17:34 ` Yann E. MORIN
2014-06-05 17:39   ` Dallas Clement
2014-06-05 18:57     ` Yann E. MORIN [this message]
2014-06-05 20:42 ` Thomas Petazzoni
2014-06-05 22:06   ` Dallas Clement
2014-06-06  6:13     ` Thomas Petazzoni
2014-06-06  7:15     ` Thomas Petazzoni
2014-06-06 16:14       ` Dallas Clement
2014-06-06 16:31         ` Mike Zick
2014-06-06 16:45           ` Dallas Clement
2014-06-10  9:32             ` Fabio Porcedda
2014-06-11 17:41               ` Dallas Clement
2014-06-13  9:23                 ` Fabio Porcedda
2014-06-14  0:52                   ` Dallas Clement
2014-06-14  7:57                     ` Thomas Petazzoni
2014-06-18 12:37                     ` Fabio Porcedda
2014-06-07  9:04         ` Thomas Petazzoni
2014-06-08  8:19           ` [Buildroot] [UNSURE]Re: " François Perrad
2014-06-09 20:10             ` Dallas Clement
2014-06-10  7:25             ` Thomas Petazzoni
2014-06-06  5:20 ` [Buildroot] " Waldemar Brodkorb

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=20140605185746.GC3553@free.fr \
    --to=yann.morin.1998@free.fr \
    --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