Geoffrey Lassner <[EMAIL PROTECTED]> writes: > I talked to one of the FreeBSD core team members about > default search path with gcc and he explained some of it to me; > unfortunately it is somewhat of a 'holy war' type of issue so it > does not sound like anything will change any time soon.
I can imagine. On the one hand, a distribution should assign a place where the sysadmin can install additional packages (ie, /usr/local/*). Then, everything including the compiler, should support that. Otoh, users (that are not that much of a sysadmin) can break the whole system, or introduce subtle (security) bugs, by having an old or buggy package addon package installed (eg, in /usr/local), and then recompiling the system. > So in the meantime I guess I will stick to this method: > CPPFLAGS='-I/usr/local/include' LDFLAGS='-L/usr/local/lib' > ./configure Yes, that's the only sane option, I guess. > I know you guys have bigger problems to work on for lilypond but > if the configure script could pick this up without having to define > these variables that would be awesome. I'm not so sure about that. For one, what additional dirs should we include, and secondly, we'd be overruling the decisions made by the distributor. I'd rather not do that. Greetings, Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org _______________________________________________ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond
