> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Ralf S. > Engelschall > Sent: Tuesday, March 02, 2004 2:48 PM > To: [EMAIL PROTECTED] > Subject: Re: emacs, giflib, and tiff contributions > > On Tue, Mar 02, 2004, Dennis McRitchie wrote: > > > 3) tiff: emacs looks for tiff header files in specified include > > directories only. Since the OpenPKG tiff package put them in a tiff > > subdirectory within the OpenPKG include directory, they were not found > > by emacs and therefore not used. Note that both the RedHat 9 package > > and the sunfreeware package places them in /usr/include and > > /usr/local/include respectively, where they can be found by emacs. So > > I changed the package to place them where they are needed. I saw that > > you provide 12 header files while the RedHat 9 and sunfreeware > > packages only provide 4: tiff.h, tiffconf.h, tiffio.h, and tiffvers.h > > . I'm not sure what the other 8 are used for, but I put all 12 in the > > standard OpenPKG include directory. You may prefer to only put the 4 > > major header files there and leave the other 8 in the tiff > > subdirectory. The same change may need to be applied to your newer > > v3.6.1 package. [...] > > Err... this then might fix Emacs but will perhaps breaks lots > of other packages which search explicitly for Tiff in the > subdir. Best is to fix Emacs here also to search it in the > subdir. How can this be achieved?
I can look into that, but before I do, are you sure that this will break other packages? As I wrote, neither the Redhat 9's libtiff-devel-3.5.7-11.i386.rpm nor Sunfreeware's tiff-3.6.1-sol9-sparc-local.gz packages install their 4 header files in a tiff subdirectory. In fact I just went to the libtiff.org website and downloaded their v3.6.1 tarball, and it installs its header files into /usr/local/include by default. Also, their documentation shows that to compile a program with tiff, you should use #include "tiffio.h", not #include "tiff/tiffio.h". And emacs is a popular editor that has been ported to many OSs. It would be surprising to hear that it is looking for tiff in the wrong place all this time. Perhaps there are others, but the only context I was able to find where apps looked for tiff header files in a TIFF subdirectory was with users of ivtools. Ivtools (optionally?) includes the tiff package within it, and then installs the tiff header files in a TIFF subdirectory. But the regular tiff package does not do this, so I don't believe that apps using the tiff package without ivtools would be looking in a subdirectory for the header files. So I'm confused why you think many programs would be looking for those headers in a tiff subdirectory. Even if you're right, I have to believe that on RedHat 9 and Solaris 9 systems that most programs there would be looking for them in an include dir, not a tiff subdir, since that is where their *binary* packages install the tiff header files. If these are needed in both places in OpenPKG (due to multi-OS support?), then perhaps the 4 main header files should be copied to both the include dir and the tiff subdir, rather than try to change every package that is looking in what is surely the standard tiff header directory on RedHat and Solaris. Dennis ______________________________________________________________________ The OpenPKG Project www.openpkg.org Developer Communication List [EMAIL PROTECTED]
