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? > -fPIC is an interesting beast. It's required on amd64 for all shared > objects (*.so*), but isn't recommended (except for hardened) for > application binaries, both due to occasional unexpected complications and > because it's slower. Thus, putting it in CFLAGS is NOT a good thing, > unless it's for a specific library package only, to get it to merge while > you are waiting for the bug you filed on it (right?) to get > researched/fixed/tested. > Speaking of which, is there any way to configure flags per package? Something like /etc/portage/package.flags, where I can configure CFLAGS, CXXFLAGS and LDFLAGS?
Sebastian Redl -- [email protected] mailing list
