On Thursday, September 22, 2011 2:56 PM, Michal Hocko [mailto:msts...@gmail.com] wrote: > On Thu, Sep 22, 2011 at 02:15:14PM -0500, Bollinger, John C wrote: > > On Thursday, September 22, 2011 12:40 PM, Michal Hocko > [mailto:msts...@gmail.com] wrote: > [...] > > > > > Most libraries have their parameters to specify compilation and > > > link > > > parameters. > > > E.g. boost should be specified as --with-boost-libdir=PATH > > > LibT1: --with-t1-library=PATH > > > > > > Ok. The boost and t1 options are documented, and that's how I > worked > > around the problem. > > So is the problem still present with those 2 parameters?
If I specify the correct library locations via those parameters then the program links successfully, even zlib. In fact, I only need to specify the correct location for one library, since all the needed ones are in the same place, and the linker processes all -L options before any -l option. My complaint is that I shouldn't need to specify library locations when the libaries are in an LSB-approved and distro-standard place to begin with. Obviously, that is much less significant problem than not being able at all to build the program. If I can find the time to improve the autoconf macros in this area then I will be helping myself. Thanks, John Email Disclaimer: www.stjude.org/emaildisclaimer ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ Pdfedit-support mailing list Pdfedit-support@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pdfedit-support