> Removing the X11/Intrinsinc.h worked well on both Fedora 4 > and recent Ubuntu 8.04 > > This said, there are two things to report: > 1. Removing this including should also be followed by a > <string.h> include in replacement as otherwise, we don't get > the memcpy prototype declaration at least on ubuntu 8.04
Hmm - that's odd. When I removed it, I didn't see a warning about implicit declaration of memcpy on my ubunutu-8.04 build. Odd. That said, explicitly including <string.h> seems like the right thing to do anyway. > 2. I also had to remove the -lXext depency for permitting a > successful link in Ubuntu. Again, that's odd, as my ubuntu build proceeded OK. Probably at some point in the past I have added the necessary package to my ubuntu baseline, although I don't recall doing it. It seems to me that the ubuntu people are fairly aggressive about *not* installing dev support things, and have split the old meta-packages up into an awful lot of smaller units, so that now to install X11-dev support you need to trawl about for a long time getting many small packages installed... Or am I just misisng some easy trick to get it all in one go? The Fedora builds seem easier in that regard, you aks for X11 dev and get the whole lot... But then I end up with a laod of stuff I never use, so... Anyway - returning to the question at hand... Do we actually need Xext or not? I'm not even clear as to what it provides! -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
