I'm noticing that after a "make World" there are two things that seem problematic. The first is that many of the applications aren't being built due to the linking phase bombing out since it can't find libiconv (since it's not using -liconv during the link/compile). Manually adding -liconv does result in a compile. Both dtpad and dtmail are good examples.
The second problem is apparent after the first. Why doesn't "make World" stop when the errors occur? It just keeps truckin' and I didn't even know I was missing anything. The same goes for the "installCDE" script which didn't bomb out due to missing apps. Maybe all that is intentional and I'm just new to the process. My questions are:: 1. What is the "right" way to add additional libraries so that they will be -l'ed (so to speak) at compile time? 2. Is there a way to raise the hysteresis of the compile process so that it will fatally panic when any of the apps don't get built. If the answer to #2 is "no" then what about a test-harness that checks the dist before any install/packaging is done? Does such a beast exist? Sorry if any of this is common knowledge. I'm just getting started. -Swift ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ cdesktopenv-devel mailing list cdesktopenv-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/cdesktopenv-devel
