Oh, so we require automake >= 1.5 now? No, not really. This is just the first time since I installed 1.4 that it hasn't cut the mustard. I'll upgrade it tomorrow.
Randy David Thompson: |Is there a reason you are stuck down at version 1.4 of Automake? |Automake is the problem here. I've tested it with 1.5 and 1.6 and |everything works fine. You can upgrade Automake to 1.5 without having |to upgrade to the venerable Autoconf 2.5x. Automake 1.6 |caught/reported a few errors for us and it is the one that doesn't |like the fact that we were trying to build libraries as _PROGRAMS. | |> |>Yes, it's failing. I'm not getting a configure file when CVSMake is done. | |> |Is it really failing? The library name should only be a warning, at |> |least when I tested it on my Linux system with autoconf 2.13. I had |> |to update it do to incompatibilities with autoconf 2.53. The real |> |solution here to remove this warning would be to use libtool on this |> |1 shared library we need to build--but I'm not ready to start digging |> |into that before a release. -- Randall Hopper [EMAIL PROTECTED]
