> Wichert Akkerman wrote: > > In all sources I have here I can simply > > switch using either of: > > > > * CC=gcc-3.0 CXX=g++-3.0 ./configure --your-usual-options > > or > > * edit a toplevel makefile that defines CC and CXX which all submakefiels > > inherit. > > - This doesn't work in Makefiles where the compiler is hard-coded in each compilation rule. I agree this is not good practice, but it is frequently seen. For example, "g++" is hard-coded in the Makefile for my package, althea. Now, this can be changed using shell tricks, as you or someone else said. Or, for a system on which only one person is likely to be compiling stuff in C++ (or C for gcc), the symlink can be temporarily changed. I seem to have gone off on a tangent, but my basic point is stated above; even if a Makefile is "wrong", it still is often the operative Makefile for a program one would like to compile. (I would mention this issue to my upstream, but they plan to switch to autoconf anyway.) - Jimmy Kaplowitz jimmy@debian.org
Attachment:
pgp6sgxayhIHg.pgp
Description: PGP signature