Re: Automake Installation Error

2010-03-22 Thread Ralf Wildenhues
Hello William, * William Drozd wrote on Mon, Mar 22, 2010 at 03:48:58PM CET: > 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$ m

Re: Building prog first

2010-03-22 Thread Ralf Wildenhues
Hello Reuben, * Reuben Thomas wrote on Mon, Mar 22, 2010 at 04:44:17PM CET: > 2010/3/22 Russell Shaw: > > 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-compilatio

Re: Building prog first

2010-03-22 Thread Robert J. Hansen
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 progra

Automake Installation Error

2010-03-22 Thread William Drozd
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/l

Re: Building prog first

2010-03-22 Thread John Calcote
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 struc

Re: Building prog first

2010-03-22 Thread Reuben Thomas
2010/3/22 Alfred M. Szmidt : > If searching is the problem *Web* searching is the answer, not the problem. > how does the indices not fix the problem? I rarely find anything useful in the indices other than particular functions or variables. Rarely, in GNU manuals, concepts, but that is because

Re: Building prog first

2010-03-22 Thread Alfred M. Szmidt
If searching is the problem how does the indices not fix the problem? What about using a info browser to search through the manual?

Re: Building prog first

2010-03-22 Thread Reuben Thomas
2010/3/22 Russell Shaw : > 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 explicit suppor

Re: Building prog first

2010-03-22 Thread Russell Shaw
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 pack

Re: Building prog first

2010-03-22 Thread Steffen Dettmer
On Sun, Mar 21, 2010 at 11:18 AM, Russell Shaw wrote: > But it is somewhat big, and i had already searched through the > online one a lot first. It is no wonder it takes noobs so long > to get productive. Yes, indeed; and even longer to get it productive correctly. I think this is no matter of t

Re: Building prog first

2010-03-22 Thread Steffen Dettmer
* 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