Eric Blake wrote:
According to Ivan Levashew on 2/12/2009 11:59 AM:
Generally, I'd like build system and compiler to be as humble as
possible. Don't run tests on my platform, don't look for libraries and
headers in my /usr directory. If something is not specified by means of
command line or env
Steffen Dettmer wrote:
I'm not sure how it looks in your context, but I think usually
autoconf expects to be able to create a binary which usually
requires at least some libc.
Or are you compiling a libc itself?
No, not libc.
How should the knowledge base (I assume it would be some
deliver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Ivan Levashew on 2/12/2009 11:59 AM:
> Generally, I'd like build system and compiler to be as humble as
> possible. Don't run tests on my platform, don't look for libraries and
> headers in my /usr directory. If something is not specified
On Thu, Feb 12, 2009 at 7:59 PM, Ivan Levashew
wrote:
> Generally, I'd like build system and compiler to be as humble
> as possible. Don't run tests on my platform, don't look for
> libraries and headers in my /usr directory. If something is not
> specified by means of command line or environment
Ivan Levashew wrote:
> Autotools are by default in an user friendly mode (I don't know how to
> name it better).
>
> User friendly mode assumes that an user compiles and installs a software
> just for himself.
I think I would call that developer mode. If you are compiling
software then you ar
Autotools are by default in an user friendly mode (I don't know how to
name it better).
User friendly mode assumes that an user compiles and installs a software
just for himself.
As a rule of thumb, what's friendly to end users, is fatal to
maintainers. Or, better say, friendliness doesn't s
