Jean-François Mertens wrote: > On 18 Jun 2007, at 00:23, Alexander Hansen wrote: > > >> We have a few packages in the distribution (often involving Tk) that >> don't seem to build at all with a non-Apple X11, e.g. sparky-py*, due >> to the lack of a "/usr/include/X11 -> /usr/X11R6/include/X11" symlink >> The failure mode is as follows (and it's generally applicable): >> ... >> g++ -O3 -ffast-math -fPIC -fno-common -Wno-long-double -I/sw/include >> -c /sw/src/fink.build/sparky-py24-3.112-1000/sparky/c++/winsystem- >> unix.cc >> In file included from >> /sw/src/fink.build/sparky-py24-3.112-1000/sparky/c++/winsystem- >> unix.cc:6: >> /sw/include/tk.h:83:23: error: X11/Xlib.h: No such file or directory >> ... >> Many packages can be fixed to see the X11 headers via setting a >> FLAGS variable: >> >> SetCPPFLAGS: /usr/X11R6/include >> >> -or sometimes (e.g. xcircuit)- >> >> SetCFLAGS: /usr/X11R6/include >> >> However, there are some packages where this doesn't work (I tried with >> sparky, to no avail). >> > even exporting CPATH doesn't work ? > Ah. I didn't think of that. > (or at worst creating "X11 -> /usr/X11R6/include/X11" somewhere in > the build-dir ?) > Nor that. >> What follows is the .info for a package that gets around this problem >> by copying header files from /usr/X11R6/include/X11 into >> %p/include/X11. >> > If this works, it is because %p/include can be put in the search path > for those > pkgs. Why can't /usr/X11R6/include be put there too ? > If such a pkg is really necessary, I understand it would not be right > to create > "X11 -> /usr/X11R6/include/X11" in %p/include, since openmotif3 and > xaw3d > already install such a dir. > But would it not suffice to do smthng like: > > mkdir -p %i/include/X11 > ln -s /usr/X11R6/include/X11/* %i/include/X11 > # and then for openmotif3 : > rm %i/include/X11/bitmaps > > ? > > JF Mertens > > PS: Obviously I would still prefer xorg to install the (completely > traditional) > symlink "X11 -> /usr/X11R6/include/X11" in /usr/include (as I've always > done on my own machine). > > I'm not particularly wedded to my package--whatever solution that we come up with will be fine.
Ideally, it would be incumbent on the package maintainer to come up with a solution for an individual package, but I thought I'd put this out there as an option, too. -- Alexander K. Hansen Fink User Liaison/Documenter akh AT finkproject DOT org ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fink-devel
