Hello David,
* Dr. David Kirkby wrote on Thu, Oct 15, 2009 at 11:53:01PM CEST:
> I've got this bit of code, which checks for 'bash'. The user does
> not need to use the bash shell, but many scripts assume the back
> shell and will fail otherwise (no, I did not write them myself!)
The first questi
Dr. David Kirkby wrote:
I've got this bit of code, which checks for 'bash'. The user does not
need to use the bash shell, but many scripts assume the back shell and
will fail otherwise (no, I did not write them myself!)
What I mean is, many scripts will assume the bash shell is somewhere in
t
I've got this bit of code, which checks for 'bash'. The user does not
need to use the bash shell, but many scripts assume the back shell and
will fail otherwise (no, I did not write them myself!)
Feel free to tell me how to criticise/improve this if you can.
AC_CHECK_PROG(foobar,bash,[yes],[no
* Bob Friesenhahn wrote on Thu, Oct 15, 2009 at 08:18:58PM CEST:
> If even one warning message is evident at the end of the configure
> run, it seems likely that the user will know to scroll back to see
> the rest.
Unless, of course, that rest is so long that the user won't read it all.
There are
On Thu, 15 Oct 2009, Ralf Wildenhues wrote:
* Bob Friesenhahn wrote on Thu, Oct 15, 2009 at 07:59:18PM CEST:
It would be good if autoconf provided an official way to produce
deferred accumulated warning text displayed the end of the configure
run.
What measure would you suggest for the case
* Bob Friesenhahn wrote on Thu, Oct 15, 2009 at 07:59:18PM CEST:
>
> It would be good if autoconf provided an official way to produce
> deferred accumulated warning text displayed the end of the configure
> run.
What measure would you suggest for the case where more than a screenful
of deferred m
On Thu, 15 Oct 2009, Ben Pfaff wrote:
One way to make it more likely that a user will see your warning
is to output it at the end of the configure script, after all of
the tests have completed.
Yes, this is usually the only bit of configure output that users will
ever look at, and just becaus
"Dr. David Kirkby" writes:
> If one runs a configure script, and it needs to show a warning for
> some reason, that could be missed by someone quite easily. Is there a
> way I could insert a 10s or so pause, so it becomes more obvious, and
> they hopefully take time to read the warning?
One way
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Peter Breitenlohner on 10/14/2009 4:24 AM:
>
> here now another patch correcting the description for ac_cv_search_FUNC.
Thanks; I squashed the two fixes into one commit, added a ChangeLog, and
applied.
- --
Don't work too hard, make som
On Thursday 15 October 2009 04:35:22 Dr. David Kirkby wrote:
> If one runs a configure script, and it needs to show a warning for some
> reason, that could be missed by someone quite easily. Is there a way I
> could insert a 10s or so pause, so it becomes more obvious, and they
> hopefully take tim
If one runs a configure script, and it needs to show a warning for some
reason, that could be missed by someone quite easily. Is there a way I
could insert a 10s or so pause, so it becomes more obvious, and they
hopefully take time to read the warning?
11 matches
Mail list logo