From: Brendan L. <bm...@ri...> - 2010-09-26 16:26:45
|
Victor, Also make sure you're in the right branch, commonification AKA master, and not in old_master. TuxType may have issues when trying to use t4k_common, even if everything goes right. If you have some time to help out, that might be a good place to start--let me know. As for the ldconfig step, maybe we could just tack on a "It's now recommended to run `ldconfig /path/to/lib` to ensure the library is found" message when installed from source. Users who know what they're doing are free to ignore it, and I don't foresee any issues if it's done unnecessarily. I still find it weird that there's no "good form" for this via automake. Best, Brendan On Sun, Sep 26, 2010 at 8:40 AM, David Bruce <dav...@gm...>wrote: > Hi Victor, > > > I already compiled the t4k_common and /user/local/lib is in my path. > > Does anyone know how can I fix it ? > > On my Debian and Ubuntu systems, I had to run "sudo ldconfig" with no > arguments, and the linker cache was updated and works fine ever after. > > This is something different from the PATH environmental variable that > is used to find binaries. > > Let me know if "sudo ldconfig" doesn't fix it. As t4kcommon becomes > part of our standard setup, we need to come up with a foolproof way to > avoid problems like this. > > Best, > > David Bruce > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Tuxmath-devel mailing list > Tux...@li... > https://lists.sourceforge.net/lists/listinfo/tuxmath-devel > |