On Sun, Mar 30, 2008 at 02:26:54PM -0400, Jacob (Jack) Gryn wrote: > I deleted the transcode directory completely and redownloaded the latest 1.1 > CVS. > > I did see the difference in that I no longer needed to fix the ffmpeg paths > time. > > I realized that I didn't have PKG_CONFIG_PATH set. > > Now, I tried setting PKG_CONFIG_PATH; it configured and compiled on the > first try. > > Any chance these fixes can be applied in such a way that the average user > won't require the path to be set? For users who aren't developers or > experienced sysadmins, they won't necessarily know that LD_LIBRARY_PATH or > PKG_CONFIG_PATH need to be set, or what paths to set them to. > > In case it helps anyone in the future to have this on records, in Fedora > Core 5 on x86_64, I used the following defaults: > PKG_CONFIG_PATH=/usr/lib64/pkgconfig:/usr/local/lib64/pkgconfig:/usr/lib/pkg > config:/usr/local/lib/pkgconfig > LD_LIBRARY_PATH=/lib64:/usr/lib64:/usr/local/lib64:/lib:/usr/lib:/usr/local/ > lib
this is the problem. LD_LIBRARY_PATH, PKG_CONFIG_PATH, etc are OS dependent. as such, the OS is supposed to be setting these properly. adding this to transcode's, or any third party's, configure script becomes a mess, quickly. OTOH, mentioning the specifics for certain OSes kinda makes sense for the wiki, or maybe even install docs. -- [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org