Sebastian Redl <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Thu, 19 Oct 2006 11:54:47 +0200:
> Duncan wrote: >> So... anytime I see this error, the first thing I try is flipping some >> CFLAGS on and off, and see if there's a reasonable combination that >> works. >> Only if that fails do I try -fPIC and bug it as necessary. >> > But wouldn't that apply only to errors that occur during the configuration > step? Or have you observed a situation where a compilation change > triggered by a failing non-essential test caused an error later? Yes. Case in point is the very -fPIC we are discussing. If the configure tests -fPIC and due to a warning decides it can't be used, it doesn't simply abort, but continues the process thru the rest of the config and into the compile and linking. Only later in the linking, and gets an error similar to that of this thread because shared objects require -fPIC on this platform, does it realize things went wrong. Then the error it spits out says to compile with -fPIC, when that's what it would have been doing if the config hadn't misinterpreted an unrelated warning on the -fPIC test as an indication that it shouldn't be used. (The other half of your post addressed in the other subthread.) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [email protected] mailing list
