I had to change the plan slightly in mid stream. The libraries will still go in /usr/lib/ooRexx and the binaries will go in /usr/bin. What I did to get everything to work was to add a new entry to the /etc/ld.conf file (actually, the /etc/ld.so.conf.d subdir). This will put ALL the libraries into the correct path for linking. This was a much better fix than trying to force them into /usr/lib.
David Ashley On 02/21/2011 01:11 PM, Rick McGuire wrote: > They should be placed wherever is appropriate for the given platform. > The answer for Linux might not be the best answer for the other > platforms. The big question for MacOS should be "where is the > expected place that the files to be". > > Rick > > On Mon, Feb 21, 2011 at 2:02 PM, CVBruce<[email protected]> wrote: >> I just wanted to verify that for ooRexx 4.2 that the files will be in >> /usr/bin /usr/lib /usr/include and /usr/share. >> >> Thanks, >> >> Bruce >> ------------------------------------------------------------------------------ >> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: >> Pinpoint memory and threading errors before they happen. >> Find and fix more than 250 security defects in the development cycle. >> Locate bottlenecks in serial and parallel code that limit performance. >> http://p.sf.net/sfu/intel-dev2devfeb >> _______________________________________________ >> Oorexx-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/oorexx-devel >> > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Oorexx-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/oorexx-devel > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Oorexx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-devel
