> Personally, at least for the time being, we don't care about HOST: as
> said by Pavel, only specific packages will need it, and they certainly
> need it so badly that they already perform their tests. And if they
> don't, the simple fact that Autoconf supports some HOST-path-sep test
> will not
> It seems to me that falling to `:' is way enough for this case.
I agree - as long as those systems where ';' is needed are able
to grok the test, that's fine. All other systems can happily use
':' as before (regardless of why they failed the test).
Tim Van Holder wrote:
> > I can send you the offending configure.in if you like. It's the one
>
> If you mean the AC_TRY_COMMAND() in the test for the BSD VPATH issue,
> I tried using
> ...
No, that one's still working fine. I think this was related to my attempt to
rewrite AM_CONFIG_HEADERS t
On Jan 31, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
>> "Markus" == Markus F X J Oberhumer <[EMAIL PROTECTED]> writes:
Markus> After a look through the sources it seems that AS_EXECUTABLE_P
Markus> should use both "test -f" and "test -x" on systems that
Markus> support it, and "test -f"
> I can send you the offending configure.in if you like. It's the one
> that's checked into the CVS CVS (no, that wasn't a stutter. :). Of
> course, I might want to pull my customizations out of my AM first and try
> again to make sure that's not causing the problem first, but if someone
> else
> > DOES pretend to do)? DJGPP can pretend to be unixy when it comes to pathseps,
> > but ONLY inside bash (granted, that's where it will matter most, but using ':'
> > because bash can handle it would break if used inside perl/m4/whatever).
> Since the test is run by bash and not by something els
> After a look through the sources it seems that
> AS_EXECUTABLE_P should use both "test -f" and
> "test -x" on systems that support it, and "test -f"
> otherwise (DOS, Win, ...)
Yes and no. The reason we try to use 'test -x' is so that
'test -x foo' will pick up foo.exe. I had not thought of
th
Sigh.
ULTRIX V4.4 (Rev. 69) System #31: Thu Aug 10 19:42:23 GMT 1995
UWS V4.4 (Rev. 11)
No mail.
stenn@porkypine> sh
$ foo=`cd / 2>/dev/null`
illegal io
$ echo ,$foo,
,,
$ bar=`cd /foo 2>/dev/null`
/foo: bad directory
$ echo ,$bar,
,,
$ baz=`exit nonsense 2>/dev/null`
nonsense: bad number
$ echo
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> Can there be any non source files which we want to ship?
Yes, sometimes. For instance with ansi2knr support we ship the man
page. I don't know whether this impacts autoconf though.
Tom
Akim Demaille <[EMAIL PROTECTED]> wrote:
: Also, does anybody know a means to profile a shell script?
How about profiling the shell running the script? :)
Lars J
--
Innovation is one percent inspiration and ninetynine percent perspiration,
and in my case; twice that... -- Norville Barnes,
> "adl" == Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes:
Akim> Does anybody knows a shell that would provide some means to
Akim> denunciates time consumers?
adl> You may want to look at the zsh/zprof module of Zsh.
adl> Unfortunately this does profiling on shell functions, so that
adl> mi
>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> As noted by Jim, the test suite is really slow since a few days. If
Akim> someone has an idea, I'm extremely interested.
Akim> Also, does anybody know a means to profile a shell
Akim> script?
Process accounting?
(http://gcc.gnu
> "Markus" == Markus F X J Oberhumer <[EMAIL PROTECTED]> writes:
Markus> After a look through the sources it seems that AS_EXECUTABLE_P
Markus> should use both "test -f" and "test -x" on systems that
Markus> support it, and "test -f" otherwise (DOS, Win, ...)
Good call, I was going to text !
On Jan 31, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
> It seems to me that falling to `:' is way enough for this case.
I hope so.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student
On Jan 31, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>>> I'd suggest to fix the second issue :)
Alexandre> Sure, it should be fixed. But you'll probably remember I
Alexandre> have always opposed the idea of having a director
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> Hmm... It's just occurred to me that this kind of test may
Alexandre> not work in general. AFAIK, some old Unices just won't run
Alexandre> shell-scripts like that; you have to explicitly specify the
Alexandre> shell th
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> I'd suggest to fix the second issue :)
Alexandre> Sure, it should be fixed. But you'll probably remember I
Alexandre> have always opposed the idea of having a directory named
Alexandre> m4.
OK :) I, myself, prefer ac/ :)
On Jan 30, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
> if (PATH=.;`pwd`; conftest.sh); then
> # We like `;', let's use it.
> else if (PATH=.:`pwd`; conftest.sh); then
> # We like `:', let's use it.
> else
> # Get lost.
> fi
Hmm... It's just occurred to me that this kind of test may n
Akim Demaille wrote:
>
> > "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
>
> Tim> I suppose so. My main point was that there were 2 different
> Tim> issues related to path separators (build & _HOST_), which the PR
> Tim> didn't seem to take into account.
>
> Personally, at least for t
On Jan 31, 2001, Akim Demaille <[EMAIL PROTECTED]> wrote:
> ``How stupid configure is not
> to check that this executable is not a directory!''.
> I'd suggest to fix the second issue :)
Sure, it should be fixed. But you'll probably remember I have always
opposed the idea of having a directory
> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes:
Derek> Yeah, sorry. I'm trying to use AS_MKDIR_P in an unescaped
Derek> heredoc context. The reason I don't seem to be able to avoid
Derek> _that_ is that I want it to happen as part of a step before a
Derek> header gets created so I'm
On Tue, Jan 30, 2001 at 09:09:53PM -0500, Harlan Stenn wrote:
: Akim,
:
: stenn@pogo> sh
: $ foo=`cd / 2>/dev/null`
: $ echo ,$bar,
: ,,
In case noone else sees it, you assigned to $foo and output $bar, so
the result is naturally empty. You should probably try again without
mixing test 1 and 2
Akim Demaille wrote:
> | "Derek R. Price" wrote:
> | > Alexandre Oliva wrote:
> | >
> | > > On Jan 30, 2001, "Derek R. Price" <[EMAIL PROTECTED]> wrote:
> | > >
> | > > >> AS_ESCAPE(m4_quote(AS_MKDIR_P(["sdir"])), [\$`])
> | > >
> | > > The simple rule is that every macro argument should be enclo
| Akim,
| stenn@pogo> sh
| $ foo=`cd / 2>/dev/null`
| $ echo ,$bar,
| ,,
| $ baz=`exit nonsense 2>/dev/null`
| $ echo ,$baz,
| ,,
| $
Thanks, but you skipped the most important tests :)
Could you try all of these?
foo=`cd / 2>/dev/null`
echo ,$foo,
bar=`cd /foo 2>/dev/null`
echo ,$bar,
baz=`
| "Derek R. Price" wrote:
| > Alexandre Oliva wrote:
| >
| > > On Jan 30, 2001, "Derek R. Price" <[EMAIL PROTECTED]> wrote:
| > >
| > > >> AS_ESCAPE(m4_quote(AS_MKDIR_P(["sdir"])), [\$`])
| > >
| > > The simple rule is that every macro argument should be enclosed in
| > > quotes.
| >
| > So the a
"Derek R. Price" wrote:
> Alexandre Oliva wrote:
>
> > On Jan 30, 2001, "Derek R. Price" <[EMAIL PROTECTED]> wrote:
> >
> > >> AS_ESCAPE(m4_quote(AS_MKDIR_P(["sdir"])), [\$`])
> >
> > The simple rule is that every macro argument should be enclosed in
> > quotes.
>
> So the above _should_ work and
> "Tom" == Tom Tromey <[EMAIL PROTECTED]> writes:
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> 1. Does Automake need to know what are the files that can
Akim> actually be in LIBOBJ, or headers can be included?
Tom> Automake wants to know the associated headers as well.
Ca
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> autoconf 2.49c (and the current CVS) fails if '.' is in PATH - it
>> tries to execute the directory `./m4' when searching m4.
Alexandre> Yet another reason to not name the directory with m4
Alexandre> goodies `m4' :-(
Alexandre
> "Mark" == Mark E <[EMAIL PROTECTED]> writes:
>> I'd like to advise you that it would be fair not to support
>> non-UNIX path separators on the build system.
Mark> Naturally, I'll have to disagree. I don't see why Autoconf
Mark> should care which path separator is used as long as Autoconf c
> "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
Tim> I suppose so. My main point was that there were 2 different
Tim> issues related to path separators (build & _HOST_), which the PR
Tim> didn't seem to take into account.
Personally, at least for the time being, we don't care about HOS
On Wed, Jan 31, 2001 at 02:20:29AM -0200, Alexandre Oliva wrote:
> On Jan 30, 2001, "Markus F.X.J. Oberhumer" <[EMAIL PROTECTED]>
>wrote:
>
> > autoconf 2.49c (and the current CVS) fails if '.' is in PATH -
> > it tries to execute the directory `./m4' when searching m4.
I think the real problem
> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> Have you given a try to my suggestion of
Akim> if (PATH=.;`pwd`; conftest.sh); then
Arg, of course you didn't...
From: Mail Delivery System
Subject: Mail delivery failed: returning message to sender
To: akim@=
X-Sent: 5 days, 22
Alexandre Oliva wrote:
> On Jan 30, 2001, "Derek R. Price" <[EMAIL PROTECTED]> wrote:
>
> >> AS_ESCAPE(m4_quote(AS_MKDIR_P(["sdir"])), [\$`])
>
> The simple rule is that every macro argument should be enclosed in
> quotes.
So the above _should_ work and there's a bug in AS_ESCAPE?
Derek
--
Der
33 matches
Mail list logo
