[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Octave-forge and 'pkg install' question
From: |
E. Joshua Rigler |
Subject: |
Re: Octave-forge and 'pkg install' question |
Date: |
Sun, 27 Apr 2008 13:33:39 -0600 |
Thanks Tatsuro. It turns out that even though I compiled all of the
libraries that Ocatve depended on (SuiteSparse, fftw, etc.) using the
LDFLAGS option, I did not set this when I compiled Octave, which is
why mkoctfile wasn't working as expected. I made the change you
suggested and everything works fine now.
...well, almost fine. Can anyone tell me why my *.oct files get
placed in my personal directory (i.e., ~/octave), even though the *.m
scripts get placed in the system directory (i.e.,
~/local/share/octave/packages), when I install using 'pkg install
-global plot-1.0.4.tar.gz'? Maybe I misunderstand the '-global'
option.
-EJR
On Fri, Apr 25, 2008 at 1:48 PM, Tatsuro MATSUOKA <address@hidden> wrote:
> 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/
>
- Octave-forge and 'pkg install' question, E. Joshua Rigler, 2008/04/25
- Re: Octave-forge and 'pkg install' question, Tatsuro MATSUOKA, 2008/04/25
- Re: Octave-forge and 'pkg install' question,
E. Joshua Rigler <=
- Re: Octave-forge and 'pkg install' question, Tatsuro MATSUOKA, 2008/04/28
- Re: Octave-forge and 'pkg install' question, E. Joshua Rigler, 2008/04/28
- [CHANGESET] Re: Octave-forge and 'pkg install' question, David Bateman, 2008/04/29
- [CHANGESET] Re: Octave-forge and 'pkg install' question, John W. Eaton, 2008/04/29
- Re: [CHANGESET] Re: Octave-forge and 'pkg install' question, E. Joshua Rigler, 2008/04/29
Re: Octave-forge and 'pkg install' question, Sergei Steshenko, 2008/04/25