Re: libname with versio number

Hello Martin, * Martin Kalbfuß wrote on Mon, Jan 11, 2010 at 03:13:22AM CET: > I have a libname with version number. > > liballegro-4.9.14 > > I added this name to AC_CHECK_LIB. And it is found. > > # Checks for libraries. > > AC_CHECK_LIB([allegro-4.9.14], [al_create_display], [], > [AC_MSG_E

Re: development work flow

Hello Martin, * Martin Kalbfuß wrote on Sun, Jan 10, 2010 at 10:59:52PM CET: > I like to know if > > make & make install & program_name > > is the typically development work flow. For many developers, I guess so. (If you meant the above literally, then you need to use && instead of &.) Howeve

Re: Where can I get 1.10a?

Hello Bernd, * Bernd Jendrissek wrote on Mon, Jan 11, 2010 at 03:59:43PM CET: > I have been trying to update to more recent autotools, and being a > traceability nazi, I want to rebuild from as far upstream as possible. > That means ignoring the distributed ./configure and Makefile.in and > rebui

problem with automake and bison

I am using the autotools in combination with GNU Bison and Flex. In particular I am using the %glr directive in my bison file (parse.y). Everything works fine, except that when I run 'make', 'ylwrap' is invoked which runs 'bison -y -d' on 'parse.y' producing 'y.tab.h' and 'y.tab.c'. 'ylwrap' then r

Where can I get 1.10a?

I have been trying to update to more recent autotools, and being a traceability nazi, I want to rebuild from as far upstream as possible. That means ignoring the distributed ./configure and Makefile.in and rebuilding them with currently installed autotools. Here's my problem: Recent automake depe