Tom Tromey wrote:
> Is an AC_BEFORE violation really just a warning?
yes.
> I think it is an error.
That's what Akim and I fight about all day long. Akim sees it as a
`convenience' and doesn't think something more severe is needed. I think that
it should be an error, because I
Donn Terry <[EMAIL PROTECTED]>:
> I don't follow. The inner echo outputs the value of the
> CC macro, and munges it for the "stage" change. The outer
> echo makes it a string (as opposed to a command to be
> executed) to pass it to the second sed to do .. insertion.
sorry, that makes no sense t
Comments below.
(Remember, I didn't invent this mess, so I don't really
have all that much control over it. It's just that
I'm one of the relatively few who need it to work.)
If it's to be totally overhauled, it needs to be done
by (or with the active support of) a maintainer, so
it doesn't lang
%% Phil Edwards <[EMAIL PROTECTED]> writes:
>> I haven't looked closely at this, but I will note right off that this:
dt> "CC=$$(echo $$(case '$(CC)' in (stage*) echo '$(CC)' | sed -e
>> is very non-portable.
pe> I have looked at this even less closely than you; perhaps I have
pe> mi
Donn Terry <[EMAIL PROTECTED]>:
> SUBDIR_FLAGS_TO_PASS = $(ORDINARY_FLAGS_TO_PASS) \
> "CC=$$(echo @cc_set_by_configure@ |
> $(PREPEND_DOTDOT_TO_RELATIVE_PATHS) )"
oh, I see. you didn't mention @cc_set_by_configure@ in your
original example. ok. hmm...
this is ugly, but seems to work,
%% Donn Terry <[EMAIL PROTECTED]> writes:
I haven't looked closely at this, but I will note right off that this:
dt> "CC=$$(echo $$(case '$(CC)' in (stage*) echo '$(CC)' | sed -e
is very non-portable. /bin/sh on Solaris (2.5.1 and 2.6 at least)
can't handle either of these constructs
Please take a look at the Makefile in that area; the
current code is using nested `` to create further command
lines (not data files). I'll admit I haven't tried, but
I'm not at all sure it can be done because the *creation*
of the string occurs in a different directory than the
*use* of it, and
On May 10, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> But it seems hard to me to cope with the various uses of autoheader.
It's absolutely essential that autoconf keeps working with
multi-header projects. GCC needs it badly to separate build
properties from host properties from target pro
> "dv" == Didier Verna <[EMAIL PROTECTED]> writes:
dv> Well, that's good news. Given your point of view on
dv> AC_REQUIRE [1], and the fact that the doc says "_suggested_
dv> ordering" about AC_BEFORE,
The doc is accurate until we fix this.
dv> [1] as expressed earlier in this threa
Hi,
I will shortly commit a patch which changes the signature of the three
macros above (they are new and were never released).
We no longer rely on parens for the m4 list, rather we rely on the
quotation:
For instance:
-AC_CHECK_DECLS((strlen))
-AC_CHECK_DECLS((malloc, realloc, calloc, free)
Donn Terry <[EMAIL PROTECTED]>:
> That would be nice... in fact configure HAS done a meta
> build to presumably fix as much as it can. However, CC can
> be passed in on the make command line, and thus needs to be
> munged at make time, so the munging needs to be in the makefile.
or you can use a
[EMAIL PROTECTED] (Paul D. Smith):
> I'm a little concerned that the & token isn't supported by all versions
> of sed, either, but I couldn't find any examples... anyone have thoughts
> on the portability of that?
s//&/ has been in ed forever, so it should be in all
versions of sed too.
--
> "dv" == Didier Verna <[EMAIL PROTECTED]> writes:
dv> Tom Tromey wrote:
>> Is an AC_BEFORE violation really just a warning?
dv> yes.
>> I think it is an error.
dv> That's what Akim and I fight about all day long. Akim sees
dv> it as a `convenience' and doesn't think someth
On the issue of Solaris: I checked with Don Cragun
(one of Sun's standards guys). I can provide chapter
and verse, but in short he says that all Solaris 2.0
and later releases have both /usr/bin/sh and /usr/bin/ksh,
with ksh being the posix shell. Here's an excerpt:
> I believe all Solari
Akim> Nevertheless, currently it is not because Autoconf itself has
Akim> somewhere a circular dependency.
Then that's the bug.
Akim> In addition, that would be a real incompatible change, since I
Akim> know there are such broken scripts outside. BUt I would
Akim> certainly not mind `breaking'
--
--
Michael Bletzinger Software Developer, Alliance Computational
[EMAIL PROTECTED] Environment & Security
217 265 5137NCSA
Hi There,
I'm using the CVS autoconf updated yesterday (from the right repository
thi
%% Donn Terry <[EMAIL PROTECTED]> writes:
dt> Please take a look at the Makefile in that area; the
dt> current code is using nested `` to create further command
dt> lines (not data files). I'll admit I haven't tried, but
dt> I'm not at all sure it can be done because the *creation*
dt>
> "R" == R Leigh <[EMAIL PROTECTED]> writes:
>> It seems to me that you don't know yet the changes undergone in CVS
>> Autoconf :(
R> Yes, sorry about that. The Solaris system that gives me internet
R> access does not have pserver available.
If you're extremely patient, you might want to tr
> "R" == R Leigh <[EMAIL PROTECTED]> writes:
Hi!
It seems to me that you don't know yet the changes undergone in CVS
Autoconf :(
R> 1. To scan configure.in intelligently for all definitions.
This is what autoheader does.
R> 2. To create config.h.in (by default) with the definitions.
On May 10, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
> Hm, we do debate about various things related to this, but I certainly
> do agree it should be an error.
> In addition, that would be a real incompatible change, since I know
> there are such broken scripts outside.
How about reporting
I see where we're miscommunicating here.
Details below.
> Donn Terry <[EMAIL PROTECTED]>:
> > I don't follow. The inner echo outputs the value of the
> > CC macro, and munges it for the "stage" change. The outer
> > echo makes it a string (as opposed to a command to be
> > executed) to pass it
%% Phil Edwards <[EMAIL PROTECTED]> writes:
Rats, the last one got away from me. Please ignore it.
>> I haven't looked closely at this, but I will note right off that this:
dt> "CC=$$(echo $$(case '$(CC)' in (stage*) echo '$(CC)' | sed -e
>> is very non-portable.
pe> I have looked at
Oops... pressed the wrong reply button (I miss mh!).
The idea of $(BACKQUOTE) would allow it to also be null,
so substitution marks would only be present when needed.
(That wasn't clear... sorry.) (It would also help with
the plethora of \\ sequences in configure.)
That does have nested
Donn Terry <[EMAIL PROTECTED]>:
> PREPEND_DOTDOT_TO_RELATIVE_PATHS = sed \
> -e 's|^ *[^ /][^ /]*/|%&|' \
> -e 's| -B| -B%|g' \
> -e 's|% *[^- /]|%&|g' \
> -e 's|%% *|../|g' \
> -e 's|%||g'
> SUBDIR_FLAGS_TO_PASS = $(ORDINARY_FLAGS_TO_PASS) \
> "CC=$
> "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Gary> Hmm. I'm pretty sure autoconf 2.13 set target to "NONE".
Akim> Yes, it did, definitely.
Gary> Nup. No problem with the change here.
Alexandre> I think I've alread
Akim Demaille wrote:
> dv> That's what Akim and I fight about all day long. Akim sees
> dv> it as a `convenience' and doesn't think something more severe is
> dv> needed. I think that it should be an error, because I haven't seen
> dv> a case where an AC_BEFORE warning is issued, and the
> > Just for the record and to provide more kindling, the XPG4/POSIX sh in
> > question is, in fact, the basic Korn shell (wrapped for viewing):
[snip]
> > And /bin/ksh is always present (SUNWcsu == core Solaris).
[snip]
>
> The next interesting question would be if ksh alters its behavior if
> i
I'm using that as an unambiguous representation of the current text
which is full of `` and unbalanced ) so that it's very difficult to
get right. That's what I said (not quite so explicitly) in my
prior message. (Start, as I said in prior mail, with
@quoted_cc_set_by_configure@ in the non-syml
On Wed, May 10, 2000 at 01:36:04PM +0200, Akim Demaille wrote:
> > "R" == R Leigh <[EMAIL PROTECTED]> writes:
>
> Hi!
>
> It seems to me that you don't know yet the changes undergone in CVS
> Autoconf :(
Yes, sorry about that. The Solaris system that gives me internet access
does not have p
On Wed, May 10, 2000 at 10:48:30AM +0200, Akim Demaille wrote:
> > "Gary" == Gary V Vaughan <[EMAIL PROTECTED]> writes:
> > "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>
> Gary> Hmm. I'm pretty sure autoconf 2.13 set target to "NONE".
>
> Akim> Yes, it did, definitely.
>
> I haven't looked closely at this, but I will note right off that this:
>
> dt> "CC=$$(echo $$(case '$(CC)' in (stage*) echo '$(CC)' | sed -e
>
> is very non-portable. /bin/sh on Solaris (2.5.1 and 2.6 at least)
> can't handle either of these constructs (either $() or () in case match
31 matches
Mail list logo
