> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> I am stumped. Is something wrong with the
Mo> AC_REQUIRE([AC_CONFIG_AUX_DIR_DEFAULT]) such that is no longer
Mo> includes the text from AC_CONFIG_AUX_DIR_DEFAULT?
Could you set up a small configure.in which demonstrates the problem?
> "Mark" == Mark E <[EMAIL PROTECTED]> writes:
>> | TEST_FINDS_EXE=Y
>>
>> Wow, are you telling us we no longer need to dive into `test $ac_x'
>> and things like this?
Mark> It's a solution designed so we don't have to modify configure
Mark> scripts, but it's a hack. And it's a DJGPP-only
| A unified solution is certainly desirable. But perhaps we should find
| out how urgent a solution to this problem is before you decide to take
| on this problem for the next release. DJGPP's Bash has a solution
| (TEST_FINDS_EXE as mentioned), Cygwin (I've been told) has a similiar
| solution,
| I was looking back at the ChangeLog when I noticed this:
| 2000-05-23 Akim Demaille <[EMAIL PROTECTED]>
|
| Simplify the interface: users shouldn't need to explicitly check
| for special environments.
|
| * acspecific.m4 (AC_EXEEXT, AC_OBJEXT): AU
| PROCESS_FILES="Makefile src/Makefile"
|
| AC_OUTPUT([$PROCESS_FILES])
Hm, do you really depend upon this? You're out of the Automake law.
Sure we can (should?, hm, I miss Alexandre :) re enable it, but it
seems like a bad idea.
A better idea is
if aldjaslkdj; then
AC_CONFIG_FILES(src1/Ma
Could you send the man page? Or a --help? And the config.log from
the CVS Autoconf's configure.
Thanks!
Akim
| configure:1039: /usr/absoft/bin/f77 -o conftest conftest.f >&5
| FORTRAN 77 Compiler 4.5, Copyright (c) 1987-1999, Absoft Corp.
Hm, are you telling us that your compiler is always outputting
something when it compiles?
cat >conftest.f
> "Steven" == Steven G Johnson <[EMAIL PROTECTED]> writes:
Steven> I've never heard of anyone using .fpp either, and .F is fairly
Steven> standard (as standard as things get with Fortran) for
Steven> preprocessed Fortran code.
So we do mean .f, not .F. Thanks!
Akim
> "Steven" == Steven G Johnson <[EMAIL PROTECTED]> writes:
Steven> So, there's probably some subtle error with the various evals
Steven> and redirects and pipes in the new version. Surely we have a
Steven> sh guru who can identify the problem?
Yep, that would help :)
Here is a small test c
> "Steven" == Steven G Johnson <[EMAIL PROTECTED]> writes:
Steven> Great, now that you have confirmed that it works, hopefully it
Steven> can get accepted and applied.
Given that it's a bug fix, that the solution is proposed is clearly
right, I'll apply it.
Steven> It would be nice to have
| Following the suggestions in the manual, I create a rule like
| GNUmakefile: GNUmakefile.in $(top_builddir)/config.status
| cd $(top_builddir) && CONFIG_FILES=$@ CONFIG_HEADERS= ./config.status
|
| to automatically rebuild the makefiles. The above won't work in a
| subdirectory, so how
| > + ../autoupdate -m .. -
| > c:/djgpp/tmp/au16317/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open
| > [c:/djgpp/tmp/au16317/m4.m4]: No such file or directory (ENOENT)
| > c:/djgpp/tmp/au16317/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open
|
| After playing with generated temporary files, it se
| Akim Demaille writes:
| > I think Autoconf should advocate a single approach.
|
| Yup.
|
| > Also, is `HAVE_WORKING_FOO' the right naming scheme? Is it powerful
| > enough to allow us the specify the various brokenness that this or
| > that function may have? Should
I'm tempted to say he is right. Why don't we just check for the exit
status? I couldn't find good information in the ChangeLog.
But even if we don't change the logic, the technology is dead wrong.
It should be
if ${CC-cc} -g ... 2&>1 | grep . >/dev/null; then
Akim
The test to det
| gnu m4 1.4
| autoconf 2.13
| AIX 4.3.2
|
| # autoconf
| autoconf: Undefined macros:
| ***BUG in Autoconf--please report*** AC_LOCALDIR
Arg, this is a known difference between CVS autoconf and 2.13: in the
latter there is:
if test -n "$localdir"; then
use_localdir="-I$localdir -DAC_LOCALDIR
> "Assar" == Assar Westerlund <[EMAIL PROTECTED]> writes:
Assar> Now, this `feature' is gone from the CVS version of autoconf so
Assar> that code should probably migrate to doing things some other
Assar> way, but that's probably somebody else's problem.
Right. Where can we see that package?
| > I don't get it at all. Why would you have such problems, and I
| > don't???
|
| The problem went away after the latest cvs update. I still get one failure,
| but I see nothing as of yet that would classify it as DOS-specific.
Good to know.
| =
| ./debug-9
Hi!
The current CVS version of Autoconf no longer defines AC_LOCALDIR
which you appear to be depending on in your configure.in script.
Would it be possible to see how and why you use it so that either I
may submit a patch to you, or to Autoconf? A pointer to a tarball is
just what is needed.
T
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> My questions are; are there systems where the "false" and "true"
Lars> commands don't exists, and are there other problems with
Lars> scripting things this way?
Yes, they are portable. You can use `:' instead of `true', although
less
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> Because some compilers just print a warning message and
Alexandre> proceed. GCC on HP/UX without GNU as is a good example.
>> Aaah! OK, thanks. But what can drive someone to make such a
>> decision?
Alexandre> Maybe
>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jun 13, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
>> I'm tempted to say he is right. Why don't we just check for the
>> exit status?
Alexandre>
| Maybe you could just check for stderr output, instead of checking both
| stdout and stderr? But I don't know if compilers reliably send warning
| messages of this sort to stderr, as they should. (Sigh...)
Hm, I like the idea, but don't know if it is good or not :) Anyway,
it doesn't cost to
> "Ossama" == Ossama Othman <[EMAIL PROTECTED]> writes:
Ossama> Hi Akim, On Tue, Jun 06, 2000 at 09:48:02AM +0200, Akim
Ossama> Demaille wrote:
>> > "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
>>
Mo> I am stumped. Is something wrong with the
Mo> AC_REQUIRE([AC_CONFIG_AUX_DIR_DEFAULT])
| c:/djgpp/tmp/au7944/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open
| [c:/djgpp/tmp/au7944/m4.m4]: No such file or directory (ENOENT)
| c:/djgpp/tmp/au7944/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open [../libm4.m4]: No
| such file or directory (ENOENT)
|
| and a preserved input.m4:
|
| diver
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jun 14, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>> Perhaps this is a silly idea, but why don't you just run the
>> compiler without the -g flag to make sure that it created a
>> conftest.o file, and then run with th
Thanks, Autoconf is now using Automake, and therefore is no longer
susceptible to be buggy in this area. Which does not mean that
Automake cannot :)
Akim
| c:/djgpp/tmp/au7944/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open
| [c:/djgpp/tmp/au7944/m4.m4]: No such file or directory (ENOENT)
| c:/djgpp/tmp/au7944/input.m4:44: c:/djgpp/bin/m4.exe: Cannot open [../libm4.m4]: No
| such file or directory (ENOENT)
|
| and a preserved input.m4:
|
| diver
> "Adam" == Adam J Richter <[EMAIL PROTECTED]> writes:
Adam> However, I think the correct fix would be for autoconf to have a
Adam> "grep -v warning:" in its test of output on standard error when
Adam> that is used as the test for compile failure in AC_CHECK_HEADER.
Yes, we have a serious pr
> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> That might not be a bad idea. I don't like to depend on od just to
Mo> get the size of a file. Am I just missing something? Is there an
Mo> easy way to figure out the size of a binary file in bytes?
Autoconf 2.13 says:
ac_lines=`grep -c
> "Assar" == Assar Westerlund <[EMAIL PROTECTED]> writes:
Assar> Mo DeJong <[EMAIL PROTECTED]> writes:
>> Perhaps this is a silly idea, but why don't you just run the
>> compiler without the -g flag to make sure that it created a
>> conftest.o file, and then run with the -g flag but check tha
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> I'm not even sure `wc -c' will be available everywhere :-(
I don't remember where, but I used it portably. I think for a time,
Automake what using it too somewhere (was it depcomp?). But I can't
find where.
To answer
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> GCC and Sourceware src (== Cygnus)'s top-level configure
Alexandre> always passes --build, --host and --target down to
Alexandre> sub-directories. Therefore, we must not assume that, just
Alexandre> because --host is giv
>>>>> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> I just updated and got this change to the AC_CHECK_TOOLS macro:
Mo> 2000-06-09 Akim Demaille <[EMAIL PROTECTED]>
Mo> * acgeneral.m4 (AC_CHECK_TOOLS): Rewrite.
Thanks Mo, I'll look at it.
I'm working on it at home, Monday I should bring something which
should be close to a solution + explanation :)
Akim
>>>>> "Akim" == Akim Demaille <[EMAIL PROTECTED]> writes:
Akim> I'm working on it at home, Monday I should bring something which
Akim> should be close to a solution + explanation :)
So I think the four next patches will solve your problem. Well,
Index: 0.348/ChangeLog
--- 0.348/ChangeLog Thu, 22 Jun 2000 20:53:11 +0200 akim (ace/34_ChangeLog 1.315 666)
+++ 0.348(w)/ChangeLog Sat, 24 Jun 2000 20:05:43 +0200 akim (ace/34_ChangeLog 1.315
+666)
@@ -1,3 +1,26 @@
+2000-06-24 Akim Demaille <[EMAIL PROTECTED]>
+
+ The c
Index: 0.347/ChangeLog
--- 0.347/ChangeLog Thu, 22 Jun 2000 20:50:08 +0200 akim (ace/34_ChangeLog 1.314 666)
+++ 0.347(w)/ChangeLog Thu, 22 Jun 2000 20:52:43 +0200 akim (ace/34_ChangeLog 1.314
+666)
@@ -1,3 +1,11 @@
+2000-06-22 Akim Demaille <[EMAIL PROTECTED]>
+
+ A macro which
Index: 0.349/ChangeLog
--- 0.349/ChangeLog Sat, 24 Jun 2000 20:07:50 +0200 akim (ace/34_ChangeLog 1.316 666)
+++ 0.349(w)/ChangeLog Sat, 24 Jun 2000 20:28:00 +0200 akim (ace/34_ChangeLog 1.316
+666)
@@ -1,5 +1,15 @@
2000-06-24 Akim Demaille <[EMAIL PROTECTED]>
+ Given better na
Index: 0.351/ChangeLog
--- 0.351/ChangeLog Sat, 24 Jun 2000 21:44:31 +0200 akim (ace/34_ChangeLog 1.318 666)
+++ 0.351(w)/ChangeLog Sat, 24 Jun 2000 21:44:36 +0200 akim (ace/34_ChangeLog 1.318
+666)
@@ -5,6 +5,10 @@
2000-06-24 Akim Demaille <[EMAIL PROTECTED]>
+ * doc/autocon
+666)
@@ -1,5 +1,17 @@
2000-06-24 Akim Demaille <[EMAIL PROTECTED]>
+ * acgeneral.m4 (AC_CONFIG_LINKS, AC_CONFIG_HEADERS,
+ AC_CONFIG_COMMANDS, AC_CONFIG_FILES): Use a shell variable instead
+ of an m4 variable to store what must be done, so that sh
+ conditiona
> "Mike" == Mike Castle <[EMAIL PROTECTED]> writes:
Mike> So, the non-option method of specifying the build system is no
Mike> longer supported?
It is, but only to help you during the transition, you are encouraged
not to use it.
Mike> If so, I'd have to say, this kinda sucks.
Agreed, it s
| So, here's the "fix". However, this is not very robust, and the real
| problem with the AC_REQUIRE diversions needs to be fixed.
The patch is in the queue.
| On Jun 19, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
| > I'm sorry, but I disagree. The only sane and simple definition of
| > cross-compilation is when --host is specified.
|
| It might be simple, but I'm not sure it's sane. If host and build are
| identica
| I tried using the new autoheader with gcc and got this error.
| cd ../../egcs/gcc && autoheader
| /usr/local/project/install/autotools/bin/autoheader: N: No such file or
| directory
Could you track this `N'? Running sh -x autoheader -d should help.
Thanks!
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> In 06-actions-ac-cache-val:
>> +[ifelse(regexp([AC_DEFINE], [$2]), [-1],
Alexandre> Oops, the arguments for regexp are reversed.
Arg, thanks. I'm fixing this.
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jun 26, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>> On 26 Jun 2000, Alexandre Oliva wrote:
>>> Here's a patch that implements my proposal regarding the handling
>>> of --build/--host options, assuming that Mo's patch
> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> How about another option? Why don't we just skip a 2.5 release and
Mo> call it 3.0?
Just do that, and tomorrow there are several new Autoconves here and
there :) I no longer think there will ever be a new major release.
We have to live wi
> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> % make % make install
Mo> It worked! Thanks Akim.
Hm, I must say I did not understand how the regexp stuff was related
to your problem, so it's Alexandre who is to thanked :)
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> Today, my favorite solution is still an option
>> --with-old-host-semantics or whatever the name.
Alexandre> Assuming the user would know when to use this flag. As
Alexandre> I've written before, any solution that requires new
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jun 16, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>> There is a case where the new behavior is clearly wrong. That is
>> when --build and --host are both given and they are exactly the
>> same. I have appended a patc
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> And you are rejecting the fact that you don't need to specify
>> --build, you just need --host. This is a huge step backwards!
Alexandre> We may have an `I-know-what-I'm-doing' option, such as
Alexandre> --Host, for example.
I
> "Earnie" == Earnie Boyd <[EMAIL PROTECTED]> writes:
Earnie> I have yet to do a cross-compile but hope to use Akim's and
Earnie> Mo's patches to do so when I GARTI.
Hm, Get A Ride To It? No, doesn't sound right. The dictionaries of
dict(1) don't seem to know this one.
Akim
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> Well, I was definitely referring to the Cygnus' case, because
>> that's probably the largest trees we will ever find, so that's
>> probably where it is more likely to have momentum (definitely not a
>> critic, just a statement).
> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> I just noticed that even for a native build, the change to
Mo> AC_CHECK_TOOLS will print out a bunch of ugly cached messages.
Mo> checking for g++... g++ checking for c++... (cached) g++ checking
Mo> for gpp... (cached) g++ checking for aCC
>>>>> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> On 28 Jun 2000, Akim Demaille wrote:
>> OK, I see. I was still under the impression that Cygnus was
>> wrapping the trees, I had not understood users were likely to
>> assemble tre
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> The fixed (quoted) patch. ChangeLog entry:
Lars> 2000-06-27 Lars J. Aas <[EMAIL PROTECTED]>
Lars> * acgeneral.m4: create subdirs, including parent
Lars> directories that don't exist already.
I believe you should write an AC_
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> I too fear we'll never be able to drop the old behavior,
Alexandre> since there are packages out there that haven't had update
Alexandre> releases for 5 years or more. We shouldn't expect such
Alexandre> packages to disa
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> When --host is given, we should not just assume we've got a
Alexandre> cross compiler. Instead, we test the compiler we've got,
Alexandre> and decide whether it's a cross compiler or not.
This one, I don't get it clea
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> It would be trivial to accomplish that: just remove the
Alexandre> line that sets build_alias=$host_alias from my proposed
Alexandre> patch.
Alexandre> The more I think about it, the more I think it's a good
Alexandre> i
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> Yes!
Alexandre> But note that cross_compiling=maybe is still necessary.
Gross :)
You know, frankly, I'm just trusting you, I'm dead lost.
Never before the CVS Autoconf cross_compiling revamping, had I
understood the mecha
| Since I don't actually use CVS autoconf anywhere (because of it's
| incompatibilities with automake)
What do you mean?
| and don't have it installed, please
| test this patch before applying it.
OK, I will. I approve this patch, but I will rewrite the while into a
for. I'll write a test t
> "Martin" == Martin Wilck <[EMAIL PROTECTED]> writes:
Martin> Hi there,
Hi!
Martin> The new aclang.m4 structure actually makes implementing the
Martin> f90 support much easier than it was before.
That's the whole point, and I'm happy to see it meets its requirements
:)
Martin> I'd like t
| NTP, on the other hand, appeared to be using *some* 2.14a version of
| autoconf. But it's hard to determine really as there are no periodic
| checkpoints or at least tie in something to indicate which code set things
| were built with.
Right, this is another perverse effect of the long delays
> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes:
Harlan> Since I have not found a way to tell the various people who
Harlan> work on autoconf that a particular date or tag of the autoconf
Harlan> tree is what they have to use, I simply keep a tarball around
Harlan> of the version I am u
| AC_TRY_LINK_FUNC(${ac_foo_bar}, f77_underscore=double)
|
| I have the following question: To my understanding, if linking
| "foobar" succeeds, $f77_underscore=no, and $ac_foo_bar=foo_bar_.
| Now, if linking foo_bar_ succeeds as well in the second AC_LINK_FUNC
| statement, f77_underscore wil
------
Date: 03 Jul 2000 10:41:10 +0200
From: Akim Demaille <[EMAIL PROTECTED]>
To: Martin Wilck <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Subject: Re: AC_F77_NAME_MANGLING question
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
C
| > By no way should it be the user. That's probably something easy to
| > test and set. Just set ac_ext to ac_cv_prog_f90_ac_ext in
| > AC_LANG(Fortran 90) and compute the latter in AC_PROG_F90. That
| > should be enough?
|
| The user must specify his source files with one or the other suffi
You didn't send the input, but my bet is that you have nested two here
docs with the same tags. You might not even know this since Autoconf
stupidly uses EOF at zillions of different places. I plan to change
them all into ACEOF or alike.
But then, maybe that's another issue :)
| Here is the input from configure.in.
|
| AC_CHECK_FUNC(BSDgettimeofday, AC_DEFINE(HAVE_BSDGETTIMEOFDAY),
| AC_CHECK_FUNC(gettimeofday, , AC_DEFINE(NO_GETTOD)))
| AC_MSG_CHECKING([for gettimeofday declaration])
| AC_EGREP_HEADER(gettimeofday, sys/time.h, AC_MSG_RESULT(present), [
|
> "Patrick" == Patrick Welche <[EMAIL PROTECTED]> writes:
Patrick> I'm happy to try suggestions.
Hi!
Thanks for the report. The problem is most probably that your sed is
not GNU sed. For the time being I don't know too well what to do: get
rid of this limitation (but then I know that anyw
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jul 3, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>> I think it might be a good idea to add the -pipe option to the
>> default CFLAGS if gcc is detected and the -pipe option is
>> supported. What do you think?
Alexand
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jul 4, 2000, Mo DeJong <[EMAIL PROTECTED]> wrote:
>> If it makes the build go faster for 99% of the folks out there, we
>> should use it.
Alexandre> Does it? I really don't know.
I don't know either for sure, but I'
| I want to make sure that two functions are available, and die if they're
| not.
|
|
| AC_CHECK_FUNC(seteuid, AC_DEFINE(HAVE_SETEUID, 1), AC_MSG_ERROR([This
| program re
| quires that seteuid be available]))
|
| AC_CHECK_FUNC(getpwent, AC_DEFINE(HAVE_GETPWENT, 1), AC_MSG_ERROR([This
| program
> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes:
Harlan> Is the present state of the CVS version of autoconf "stable
Harlan> enough" for production use?
Harlan> It looks like a couple of folks are getting ready to start
Harlan> cross-compile efforts for new releases of NTP, and I need
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> This is not true. Akim committed the patch without
Alexandre> updating the documentation.
Right :( Could someone try to fix that? I don't have time now, and
in addition, I feel incompetent.
> "Mo" == Mo DeJong <[EMAIL PROTECTED]> writes:
Mo> I just noticed that the more I run ./config.status --recheck the
Mo> more CFLAGS arguments show up in ./configure line that gets
Mo> rerun. (This is after two re-configures)
Mo> % make /bin/sh ./config.status --recheck running /bin/sh
Mo> /
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> There's obviously one set of ""s too much here. Should the
Lars> redundant pair be removed in the macro definition or the macro
Lars> invocations?
I'd say from the macro.
BTW, you should state in the comment of AC_SHELL_DIRNAME that
| Dear Akim,
Hi!
| My reasoning was as follows: $ac_arg is "-YP,[something]".
| Theerefore, sed -e 's%^P,%-L%" won't substitute anything, because the "P"
| is not at the beginning of the expression:
|
| echo '-YP,/usr/bogus:/usr/stuff' | sed -e 's%^P,%-L%' -e 's%:% -L%g'
| -YP,/usr/bogus -L/us
> "Bernard" == Bernard Dautrevaux <[EMAIL PROTECTED]> writes:
Bernard> I'd rather suppress them from the macro invokations; when
Bernard> reusing AC_SHELL_DIRNAME I thus has less to type :-)
Right, but I personally want to have full control over this kind of
things. And just imagine it was
> "Ralf" == Ralf Corsepius <[EMAIL PROTECTED]> writes:
Ralf> With your patch however, I would expect people to start using
Ralf> AC_SHELL_DIRNAME instead of dirname and therefore I would expect
Ralf> it to hit some time.
Personally I'd prefer that you don't make it public, it is too young.
M
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> The patch is fine
Applied.
Alexandre> I'm not 100% sure about its portability, though.
There is nothing risky, IMHO, in there.
Some more work will be needed.
src/ace/patches % cat /tmp/dirname.sh
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Akim> Almost right :)
Alexandre> Almost? Seems right to me.
Oh, yeah! I momentarily thought you were named texi2dvi, sorry :)
I'm approving and applying your patch.
How about using commas instead of %? Karl Berry pushed me several
times to `,' because it results in something more readable:
sed '/^\/*$/!s,//*$,,;s,[^/]*$,,;s,//*$,/,;/^\/$/!s,/$,,'
sed '/^\/*$/!s%//*$%%;s%[^/]*$%%;s%//*$%/%;/^\/$/!s%/$%%'
and I tend to agree with him.
> "Martin" == Martin Wilck <[EMAIL PROTECTED]> writes:
>> > al=`echo $dir | sed
>> '/^\/*$/!s%//*$%%;s%[^/]*$%%;s%//*$%/%;/^\/$/!s%/$%%'` ^^
>> ^^
Martin>
Martin> ^ I think "!" after a sed address expression is not portable -
Martin> actually, it seems to work only with GNU sed.
Hm,
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> It works with Solaris' sed, and is significant more
Alexandre> complicated because of some lossage in it.
I don't think we need this, I never heard of anything like this. And
the Solaris system I tried works fine:
Last
>>>>> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> On Thu, Jul 06, 2000 at 10:06:10AM +0200, Akim Demaille wrote: :
Lars> So until we know we have it right for sure, it should not be
Lars> public.
Lars> So what does that mean? J
Akim> undocumentedward-underscoredward compatible.
Alexandre> These words are getting Awkimward.
Lars> And you are getting awkimward compatible...
:) :) Hi'm rooling ze warld!
| I'm trying to upgrade to CVS autoconf, and I'm wondering if I need
| to upgrade automake, libtool, and m4 at the same time?
|
| The testsuite failed for instance like this:
|
| | 3. ./torture.m4:148 --- empty Thu Jul 6 14:26:47 2000
| | +++ stderr Thu Jul 6 14:27:00 2000
| |
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> IMO, we should only add those that the user explicitly set
Alexandre> in the configure command line.
Hm, why not after all.
What shall we do out of AC_ARG_VAR? The point was also to diagnose
important variables that ha
> "Bernard" == Bernard Dautrevaux <[EMAIL PROTECTED]> writes:
Bernard> If a path starts by a double '/' (that is for any UNC path,
Bernard> quite often found on DOS boxes), we will strip one of these
Bernard> leading '/'; thus the directory part of
Bernard> "//server00/home/me/myfile" (which
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> $ uname -a Linux nfs.sim.no 2.2.5-15 #11 Tue Nov 16 19:02:35 CET
Lars> 1999 i586 unknown
Lars> $ dirname src/Makefile src
Lars> $ echo "src/Makefile" | sed
Lars> '/^\/*$/!s,//*$,,;s,^/*$,,;s,//*$,/,;/^\/$/!s,/$,,' src/Makefile
Sorry,
| This may look like a medium-sized patch (requiring forms to be signed),
| but it's mostly indentation changes.
Alexandre can judge, I can't.
| What stdin/stdout support does is that it allows me to pipe config.status
| to itself so I can have a file be both of the CONFIG_FILE type and the
| C
>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jul 6, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
>> What shall we do out of AC_ARG_VAR? The point was also to diagnose
>> important variables that have change
| : Alexandre can judge, I can't.
|
| Well, what's not indentation fixes is mostly ifelse alternations without
| any "original work", so I think the patch only counts for the extra
| case/esac lines...
But I still want an alexandreward opinion anyway :)
| : | CONFIG_HEADERS= CONFIG_FILES=-:fi
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> You are so dependwards to Alexandre... You need to become more
Lars> independwards...
Hm, let's say that the idea is interesting, but not RMS compatible :)
Akim> : Actually, why do you want stdin at all, we lived so long
Akim> witho
> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
>> Do we want to keep the ability to document some variables in
>> --help?
Alexandre> I'd never seen a need for that, but I liked it when you
Alexandre> did.
Err, what does this is supposed to mean? :)
Personally, I like it. I t
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Lars> Sure. First we take Manhattan - *then* we take Berlin...
Will you rework your Manhattan?
> "Lars" == Lars J Aas <[EMAIL PROTECTED]> writes:
Akim> Will you rework your Manhattan?
Lars> Won't I have to?
Yep, I was afraid you'd let me do that, and I don't have time to.
> "Steven" == Steven G Johnson <[EMAIL PROTECTED]> writes:
Steven> I wouldn't mind submitting a patch for that.
Sold!
>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]> writes:
Alexandre> On Jul 6, 2000, Akim Demaille <[EMAIL PROTECTED]> wrote:
>>>>>>> "Alexandre" == Alexandre Oliva <[EMAIL PROTECTED]>
>>>>
401 - 500 of 1987 matches
Mail list logo
