On Tue, Jul 21, 2009 at 9:45 PM, ghtdak<gl...@tarbox.org> wrote: > > I've been building lots of stuff inside Sage which gets nailed > together in various ways. Keeping includes and libraries straight > when many libraries are duplicated in Ubuntu has been necessary > lately. > > Most recently, I have found 2 specific problems and perhaps something > more general to consider. I wanted to ask here first because there > may be a reason for this > > First, libpng12.so is the same version as libpng.so in the current > ubuntu distro but there is no symbolic link which maps libpng.so to > libpng12.so. Building certain packages (VTK for example) gets a > little confused having found the header files in sage but by default > only finds libpng in /usr/lib > > I've put a sym-link in sage and it appears OK. > > Second, is zlib. Again, the versions are the same and in this case > the symlinks exist... However, some programs which use zlib don't work > properly, in particular git. Git complains: > > tar...@puget:$ git st > git: /home/tarbox/projects/sage/sage-4.1/local/lib/libz.so.1: no > version information available (required by git) > > This one has me a bit boggled... I looked at the docs and there > doesn't appear to be a switch which turns on versioning... and the > numbering scheme using symlinks is identical. So, this is just weird. > > More generally, when building larger packages (Qt, VTK) its non- > trivial to adjust makefiles... makefiles are generated by other > systems. I've been able to add the include path and all "seems" ok > but I'll do more testing. > > However, I noticed that sage sets the environment variable > LIBRARY_PATH which is a gcc variable. OTOH, it doesn't set CPATH or > C_INCLUDE_PATH or CPLUS_INCLUDE_PATH. This seems inconsistent. > LD_LIBRARY_PATH is set, as it would need to be, but that is for ld and > I'm not sure that gcc uses it and I've had problems although many of > the build systems do take a look and try various "tricks" to help > out. Sometimes this helping causes very subtle problems. > > If there is a reason for this, cool I'd just like to know the logic. > If its something which should be looked into / fixed, I'll enter a > bug / enhancement into trac.
I can't think of any particular reason for us not setting CPATH, etc. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
