help-octave
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Octave-forge and 'pkg install' question


From: Tatsuro MATSUOKA
Subject: Re: Octave-forge and 'pkg install' question
Date: Sat, 26 Apr 2008 04:48:46 +0900 (JST)

Hello

Mmmm..
If you have build octave, like

export LDFLAGS='-L/tmp/lib64'
./configure .,,

The created mkoctfile-3.0.1 script file will inculde -L/tmp/lib64.
The pkg install command use mkoctfile script to build the package.

Please check mkoctfile-3.0.1 script file.
If it does not incude '-L/tmp/lib64', you modify the scrpt.
Please modify

: ${LDFLAGS="-L/tmp/lib64'"}

in mkoctfile-3.0.1 script file.

After that please try to use pkg install command.

Regards

Tatsuro


--- "E. Joshua Rigler" <address@hidden> wrote:

> Hi all,
> 
> My system is a 64-bit Intel Xeon machine that runs Redhat Enterprise
> Linux v4.  I have discovered that many of Redhat's standard library
> packages fail to create the lib*.so symbolic links in the /usr/lib64
> (or /usr/X11/lib64) subdirectories, even though the actual 64-bit
> library files (i.e., lib*.so.X.Y) are present and valid.  The result
> is that many source code distributions that need to link to these
> libraries end up trying, and failing, to link to 32-bit versions of
> the library instead.  My solution is to create a directory called
> /tmp/lib64, generate the necessary symbolic links there, and compile
> everything with the -L/tmp/lib64 option (I do NOT have root access to
> this machine).
> 
> Now, I recently compiled and installed Octave 3.0.1.  It took a little
> effort, but using the solution described above (plus a few other
> necessary tricks), everything finished, and 'make check' came back
> perfect.  However, when I tried to install the Octave-forge package
> 'plot' using "pkg install plot-1.0.4.tar.gz", I got errors related to
> the fact that the compiler was unable to link to libX11.so, for the
> very reason described above.  I assume any Octave-forge package that
> requires compiling and linking against such libraries will also fail.
> 
> So, my question is:  How does one force the pkg package installer to
> compile things with user-provided flags (LDFLAGS=-L/tmp/lib64 for
> example)?  Or do I just need to compile and install these packages by
> hand?
> 
> -EJR
> _______________________________________________
> Help-octave mailing list
> address@hidden
> https://www.cae.wisc.edu/mailman/listinfo/help-octave
> 


--------------------------------------
GANBARE! NIPPON! Win your ticket to Olympic Games 2008.
http://pr.mail.yahoo.co.jp/ganbare-nippon/


reply via email to

[Prev in Thread] Current Thread [Next in Thread]