* On Sun, Mar 21, 2010 at 10:27 AM, Ralf Wildenhues wrote:
noinst_PROGRAMS = unimain
unimain_SOURCES = unimain.c
unidata.tab.c: unimain$(EXEEXT) /usr/share/unicode/UnicodeData.txt
./unimain$(EXEEXT) $ $@
BTW, execution of built programs like this makes your package unsuitable
Steffen Dettmer wrote:
* On Sun, Mar 21, 2010 at 10:27 AM, Ralf Wildenhues wrote:
noinst_PROGRAMS = unimain
unimain_SOURCES = unimain.c
unidata.tab.c: unimain$(EXEEXT) /usr/share/unicode/UnicodeData.txt
./unimain$(EXEEXT) $ $@
BTW, execution of built programs like this makes your
2010/3/22 Russell Shaw rjs...@netspace.net.au:
Steffen Dettmer wrote:
* On Sun, Mar 21, 2010 at 10:27 AM, Ralf Wildenhues wrote:
BTW, execution of built programs like this makes your package unsuitable
for cross-compilation. Just so you're aware of that.
Not true. automake does not have
If searching is the problem how does the indices not fix the problem?
What about using a info browser to search through the manual?
On 3/22/2010 4:34 PM, Reuben Thomas wrote:
What about using a info browser to search through the manual?
I often do that. The trouble is that often what I want to know has to
be deduced from the manual, which is natural enough, because the
manual tends to be structured according to the
I have configured/make/make install on autoconf with no problems.
I have run automake's configure with no problems.
However, when I run make while trying to install automake I get the error:
-bash-3.1$ make
CDPATH=${ZSH_VERSION+.}: cd .
perllibdir=/home/wdrozd/cmake/automake-1.11.1/lib:./lib
On 3/22/10 6:50 PM, John Calcote wrote:
Reuben, you've just hit upon one of the two most significant problems
with Javadoc and the like (including doxygen, man pages, and info pages):
Agreed -- which is why I think it would be wonderful if there was strong
Autotools support for literate
