On Wed, Feb 23, 2005 at 12:49:41PM -0500, Frank Ch. Eigler wrote: > Regarding -fmudflap => -lmudflap, it used to do that. The problem was > that the simplest use of specs machinery creates a final sequence of > "-lFOO" options that sometimes cannot work. libmudflap must be in a > particular spot on the command line so it can intercept calls into > libc and other libraries, and from libgcc. Adding -lmudflap once to > the beginning or end of all the libraries/objects is not sufficient > IIRC.
That suggests that it is all the more important that the gcc driver insert the -lmudflap flag in the correct spot(s) in the command line. The users aren't going to be able to figure it out easily.
