From maintainers-request at octave dot org Wed Mar 1 11:21:11 2006 Subject: Re: Compiling octave-workshop From: "Sebastien Loisel" To: "Quentin Spencer" , "octave maintainers mailing list" Date: Wed, 1 Mar 2006 18:19:32 +0100 ------=_Part_729_4122316.1141233572644 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, Quentin stumbled onto a problem, which is actually the symptom of a deeper problem. I don't know how to get compile and link options out of mkoctfile (and I haven't found an octave-config script.) How do I find link and compile options to create Octave binaries? If there is no way, looking forward, can we get an octave-config like many other packages? In the mean time, what's a good way of pulling the compile and link options out of (say) mkoctfile? Quentin, as a workaround, can you add these libraries to your LDFLAGS environment variable? Cheers, S=E9bastien Loisel On 3/1/06, Quentin Spencer wrote: > > Hi Sebastien, > > I got a local installation of qt4 working and am trying to build > octave-workshop, but I've hit my first snag: > > checking for liboctave compile options... ok > checking whether we can build a liboctave program... configure: error: > Cannot link against liboctave > > The problem appears to be missing linker flags. You probably didn't run > into this because your copy of octave was not compiled with support for > the ufsparse libraries. I was able to get the test to pass by adding > "-lcholmod -lcolamd -lccolamd -lmetis" to the compile command. These are > optional libraries that are required for sparse matrix support in 2.9.4 > and later releases. > > -Quentin > > ------=_Part_729_4122316.1141233572644 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello,

Quentin stumbled onto a problem, which is actually the sympto= m of a deeper problem. I don't know how to get compile and link options out= of mkoctfile (and I haven't found an octave-config script.) How do I find = link and compile options to create Octave binaries? If there is no way, loo= king forward, can we get an octave-config like many other packages?

In the mean time, what's a good way of pulling the compile and link= options out of (say) mkoctfile?

Quentin, as a workaround, can you a= dd these libraries to your LDFLAGS environment variable?

Cheers,

S=E9bastien Loisel

On 3/1/0= 6, Quentin Spencer <qspencer@ieee dot org> wrote:
Hi Sebastien,

I got a local installation of qt4 working and am tryin= g to build
octave-workshop, but I've hit my first snag:

checking = for liboctave compile options... ok
checking whether we can build a libo= ctave program... configure: error:
Cannot link against liboctave

The problem appears to be missing = linker flags. You probably didn't run
into this because your copy of oct= ave was not compiled with support for
the ufsparse libraries. I was able= to get the test to pass by adding
"-lcholmod -lcolamd -lccolamd -lmetis" to the compile command= . These are
optional libraries that are required for sparse matrix suppo= rt in 2.9.4
and later releases.

-Quentin


------=_Part_729_4122316.1141233572644--