Okay let's forget the flames and talk about something related to practical development today :)
As people reading my blog might already know, I've been experimenting with --as-needed LDFLAG in the past days. It seems pretty stable when you don't have GNOME installed (as many libraries from GNOME project don't like it), but it's usually also fixable when they fail. Now, I wanted to try writing something up about that with a quick guide to fix the most common cases when --as-needed fails. While --as-needed should remain unsupported (now and robably in the future), it might be helpful to have this sort of informations lying around for who wants to know how to fix the problems. I originally thought of putting it on my devspace, but using GuideXML there is a bit tricky, at least for me (as xsltproc seems to refuse working on the pure xml directly). So I was thinking if we had a way to put some "how to fix" guides somewhere, on the lines of the ones written by soalr and vapier for hardened. A part the --as-needed thing, it might also be useful to put something about "how to solve parallel make issues" and similar things that are tricky but usually just requires little knowledge of tricks. GDP might be the place where to put them, but as they are mainly developer-oriented, they might be better accessed directly by devs (at least for the first steps until they are drafts). What people think about this? -- Diego "Flameeyes" Pettenò - http://dev.gentoo.org/~flameeyes/ Gentoo/ALT lead, Gentoo/FreeBSD, Video, AMD64, Sound, PAM, KDE
pgpa0iC3APXTS.pgp
Description: PGP signature
