Harlan Stenn wrote:
> /bin/sh: : not found
> WARNING: `:' is needed, and you do not seem to have it handy on your
> system. You might have modified some files without having the
> proper tools for further handling them. Check the `README' file,
> it often tells you
Akim Demaille wrote:
> > "Ganesan" == Ganesan Rajagopal <[EMAIL PROTECTED]> writes:
>
> Ganesan> I am curious which versions of automake actually remove
> Ganesan> VPATH.
>
> s/make/conf/.
>
> Well all the known versions, under some conditions only.
# Any assignment to VPATH causes Sun make
Harlan Stenn wrote:
> Folks have recently discussed things like "egcs_update" and other
> related scripts that attempt to check out/update certain "master" files
> before doing a checkout of "derived" files.
> Before saying something stupid on the CVS list, I thought I'd try my
> idea out here!
Autoconf folks, the comment on 'mv' in the Portable Shell section of the new
manual might not be appropriate:
`mv'
The only portable options are `-f' and `-i'.
Moving individual files between file systems is portable (it was
in V6), but it is not always atomic: when doing `mv ne
Raja R Harinath wrote:
> There's no 'setgid' bit on the /tmp directory. Does BSD still exhibit
> 'setgid' behaviour?
To back up what Eric Siegerman said, I believe setgid behavior is the
(unavoidable?) default on BSD systems, but I just started playing with them so
don't ask me to start quoting
Alexandre Oliva wrote:
> On Jan 19, 2001, "Derek R. Price" <[EMAIL PROTECTED]> wrote:
>
> > Harlan Stenn wrote:
>
> >> - on checkin, check the files in with the timestamp on the "local" file
> >>
> >> - on checkout/update, get
Akim Demaille wrote:
> So, I think I'm slowly starting to understand this VPATH stuff:
> configure wants to remove it only when useless, right? I.e., when
> VPATH is just set to srcdir? So then, I'm in favor of Derek's patch
> which seems finer that the current one, and updating the Autoconf
>
"Derek R. Price" wrote:
> Akim Demaille wrote:
>
> > VPATH is just set to srcdir? So then, I'm in favor of Derek's patch
> > which seems finer that the current one, and updating the Autoconf
> > documentation to explain exactly what happens.
>
>
Why can't I use AS_* macros from configure.in?
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
Were we directed from Washington when to sow and when to reap, we would soon
want bread.
"Derek R. Price" wrote:
> Why can't I use AS_* macros from configure.in?
Oh. I can't call them from Automake macros... anyone know why that doesn't
work? It generates the following error:
[dprice@empress ccvs-automake]$ autoconf
configure:6517: error: undefi
"Derek R. Price" wrote:
> > Why can't I use AS_* macros from configure.in?
>
> Oh. I can't call them from Automake macros... anyone know why that doesn't
> work? It generates the following error:
>
> [dprice@empress ccvs-automake]$ autoconf
> c
Akim Demaille wrote:
> >>>>> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes:
>
> Derek> Why can't I use AS_* macros from configure.in? Derek
>
> ??? I guess you are using a new autoconf with old lib files. Either
> use an *installe
Akim Demaille wrote:
> >>>>> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes:
>
> Derek> I did install it. Even more bizarre is that if I trim the
> Derek> configure.in down to just the first 8 lines (the last being,
> Derek> 'AS_M
With the latest CVS Autoconf:
[dprice@empress testSubDir]$ cat >configure.ac <<\EOF
> AC_INIT()
> AS_ESCAPE(m4_quote(AS_MKDIR_P(["sdir"])), [\$`])
> EOF
[dprice@empress testSubDir]$ rm configure.in
[dprice@empress testSubDir]$ autoconf
[dprice@empress testSubDi
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 _s
"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 m
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&quo
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
Why do the AC_CANONICAL_* functions no longer set *_alias? There's a
FIXME comment and fixing it would be a matter of removing the 'dnl', as
far as I can see and the CVS Automake is still expecting *_alias to be
set:
# _AC_CANONICAL_SPLIT(THING)
# --
# Generate the variab
Tim Van Holder wrote:
> >> >* remake-hdr.am (@STAMP@): Use .T as suffix for the
> >> >temporary file.
> >>
> >> You should probably patch autoconf's autoreconf too.
> >
> > > What part would need patching?
> >
> > The one that choose stamp file names like those created by automake.
>
> Ri
Pavel Roskin wrote:
> Hello, Derek!
>
> On Fri, 9 Feb 2001, Derek R. Price wrote:
>
> > Why do the AC_CANONICAL_* functions no longer set *_alias? There's a
>
> "cvs annotate" and "cvs log" are your friends. Akim did it. But the log
> mes
What's the reason autotest uses a while/shift loop is used to read
arguments? 'getopts' is specified by XPG4, Posix.2, and SUS2. Is that
not portable enough?
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http:
Rasmus Tamstorf wrote:
> AC_OUTPUT([src/_$ARCH/Makefile:src/Makefile.in])
You know, there's a much more painless way to do this. Autoconf already knows
that if you:
mkdir $ARCH
cd $ARCH
../configure
Then the build tree will be created automatically in and under the current
directory. That'
once, but it turned
out that I hadn't.
Rasmus Tamstorf wrote:
> On Wed, 28 Feb 2001, Derek R. Price wrote:
>
> > Rasmus Tamstorf wrote:
> >
> > > AC_OUTPUT([src/_$ARCH/Makefile:src/Makefile.in])
> >
> > You know, there's a much more painl
Rasmus Tamstorf wrote:
> Hmmm ... I'm not sure I understand ...
>
> My 'configure' script is in 'topdir' (or preferably in 'topdir/config' but
> that's a different story).
Autoconf always assumes it is in topdir. I suspect there's no easy way to work around
that.
> Furthermore I'd like to be
Rasmus Tamstorf wrote:
> Maybe I'm missing something obvious though, so if anyone would like to
> enlighten me about how to deal easily with the code-debug-code cycle using
> a separate build tree, please let me know.
I find that modern window managers make most of the cd/path point moot as I ju
Anyone ever tried to come up with a test for whether a rename across
directories on the same file system/partition is atomic? The best I can
come up with is to rename a large file in a background process and try
and kill it real quick, but I don't think that would remain reliable
across a wide va
Mike Castle wrote:
> On Tue, Mar 06, 2001 at 05:51:45PM +0100, Assar Westerlund wrote:
>
> > Derek: what did you want this for? CVS? And have you escaped on
> > vacation yet? :-)
>
> Considering the RCS atomic rename() comment earlier, I was wondering what
> the issue was as well.
Yes on both
"Lars J. Aas" wrote:
> On Wed, Mar 28, 2001 at 11:29:14PM +0200, Peter Eisentraut wrote:
> : Lars J. Aas writes:
> : > : A Gnits dude would probably prefer
> : > :
> : > : configure (AC_PACKAGE_NAME) AC_PACKAGE_VERSION
> : > : generated by GNU Autoconf AC_ACVERSION
> : >
> : > Or
> : >
> : > conf
"Lars J. Aas" wrote:
> On Thu, Mar 29, 2001 at 08:29:19AM -0500, Derek R. Price wrote:
> : I also don't see a reason why it would be very useful to maintain a version
> : on a configure script separate from the pacage version. Anyone else?
>
> If you follow devel
Tim Van Holder wrote:
> GNU configure (PACKAGE VERSION) AC_VERSION
>
> After all, the relevant version number for configure itself, is that
> of the autoconf that created it; the name & version of the package
> it's intended for are useful extra information.
> And since you explicitly call it _GN
Tim Van Holder wrote:
> True. But if you apply 'the program being run', then you need a seperate
> version for configure, as it is neither autoconf, nor the package,
> really.
> I guess that is what it boils down to: do we see 'configure' as a) a
> program in its own right, b) an inextricable par
Ivan Vlaev wrote:
> Sorry if you already discussed it but, what about having both:
> configure --version
> and
> configure --autoconf-version
>
> at least i don't expect
> any-program --version
> to dump the version of the compiler used for building it.
>
> Probably this is matter of which
Peter Eisentraut wrote:
> Quoth the GCS:
>
> If you *need* to mention the version numbers of libraries which
>
> (Autoconf is sort of a library...)
>
> are distributed separately from the package which contains this
> program, you can do so by printing an additional line of version
Akim Demaille wrote:
> > "Tim" == Tim Van Holder <[EMAIL PROTECTED]> writes:
>
> Tim> Judging by the interesting appearance and disappearance of files
> Tim> in the repository, I assume someone (presumably Akim) is in the
> Tim> process of renaming autoconf.sh and friends to .in,
>
> Nice gue
35 matches
Mail list logo
