automake links my C programs with the C++ compiler

Hi, Some of the gettext programs contain or don't contain C++ source code, depending on the platform and configure options. Automake-1.9.6 and -1.9b emit rules to always link the programs with the C++ compiler. For automake-1.9.6 this was easy to work around: # Linking with C++ libraries is

Can't find the correct set of libs on FC5/x64

I'm currently taking a course in graphics programming with OpenGL, and thought it would be kind of me to turn in assignments which are ./configurable. My desktop environment is an OS X box, and the TAs are running a variety of different Unices. This seems like a job for Autotools, so I set up a

distdir unset in subdir Makefiles?

Hi, I've noticed that the distdir variable in generated Makefile.in's only appears in the top-level Makefile.in, however, it is not set in subdirectories' Makefile.in's. Is this intentional? According to the top Makefile.in, distdir and top_distdir are passed down recursively during a

differences between gmake and freebsd's make

I've got a project that uses automake-1.9.6. I run autoreconf. I go to a FreeBSD machine, create a subdir for the build, cd there, and run ../configure. I run 'gmake' and everything builds. I run 'gmake' again and the beast completes without building anything (no surprise). I run 'make' and

Re: differences between gmake and freebsd's make

Hello Harlan, * Harlan Stenn wrote on Fri, Aug 25, 2006 at 03:07:52AM CEST: I run 'gmake' and everything builds. I run 'gmake' again and the beast completes without building anything (no surprise). I run 'make' and things get built. Yes, this rings two bells, a general and a more

Re: differences between gmake and freebsd's make

Thanks, Ralf! I also am seeing a problem with /usr/ccs/bin/make on solaris. I do suspect a VPATH thing at the moment. It is very strange to me that it only happens in some directories and not in others. I'm digging... H -- Hello Harlan, * Harlan Stenn wrote on Fri, Aug 25, 2006 at