Hi all,
I would like to submit the attached script to your collective attention. This
is a helper script to automate handling project version numbers in a mixed
autoconf / svn / git-svn environment.
Some context: I work in an environment where source code is primarily stored in
and distributed
Hi Joachim,
Op 5 feb 2010, om 16:55 heeft j.wuttke het volgende geschreven:
> A user of my software package reported that compilation on
> a virtual Linux machine running on his Mac failed because
> '::malloc' was not declared.
I have encountered the same issue as a producer of another software
Op 6 mrt 2010, om 14:47 heeft Akos Rajna het volgende geschreven:
> Is there any way to use same named sources located in different folders with
> automake for a C++ project?
This is the autoconf list, not the Automake list.
But anyways:
...SOURCES = $(srcdir)/../../relative/path/to/other/sou
delegated to it.
The key point from a technical perspective is not how to *run* the concurrency,
it's to find it in the first place. The analysis itself will be the trickiest,
agreed.
Cheers
--
Raphael 'kena' Poss · r.c.p...@uva.nl · +31 20 525 7559
UvA · FNWI · IvI · CSA · 109
Hi Sam,
Op 25 mei 2010, om 23:44 heeft Sam Shin het volgende geschreven:
> I'm debating over what the most appropriate location for installing example
> programs for a library would be. Would it be acceptable to install example
> programs into datadir? Or should I create a non-standard directory
mber, which contains a
newline in your case. that's why the period is alone (and invalid) on the next
line.
Cheers,
--
Raphael 'kena' Poss · r.c.p...@uva.nl · +31 20 525 7559
UvA · FNWI · IvI · CSA · 1098XG 107 Amsterdam (NL)
z = \f. (\x. f (\y. x x y)) (\x. f (\y. x x y))
Th
Op 3 jun 2010, om 22:52 heeft Bruno Haible het volgende geschreven:
> AM_CONDITIONAL([LIBUNISTRING_]AS_TR_CPP([$1]), [true])
I'd try
AM_CONDITIONAL([LIBUNISTRING_]m4_quote(AS_TR_CPP([$1])), [true])
___
Autoconf mailing list
Autoconf@gnu.org
http://l
Op 29 jun 2010, om 22:35 heeft Wesley Smith het volgende geschreven:
>
> I don't disagree, but let's consider this an academic exercise at this
> point. I'd actually like to know how to do this regardless of whether
> it violates anyones code sensibilities.
Before we answer your question, I'd l