octave-maintainers
[Top][All Lists]
Advanced

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

Re: [OctDev] munge-texi problem with static library build


From: Rob Frohne
Subject: Re: [OctDev] munge-texi problem with static library build
Date: Mon, 28 Mar 2011 14:08:58 -0700
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.14) Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8

Hi John,

Thanks so much for your willingness to try and help me. I'm not sure how to proceed. It seems like it might be a bigger problem than I thought to get a portable version of octave working. I am using the control package and it may require .oct files. Is it more feasible perhaps to make a self contained octave setup that uses dynamic libraries?

Thanks,

Rob

On 03/18/2011 12:17 PM, John W. Eaton wrote:
On 16-Mar-2011, Rik wrote:

| Unfortunately, I don't believe you will be able to easily build a
| statically linked version of Octave.  I just tried with the development
| code and it bombs out pretty badly.  The generated Makefile in the src
| directory, for example, can't even be read by Make because a line
| continuation character is missing.  Furthermore, if you look at Makefile.am
| in the src directory you will find this comment:
|   ## FIXME -- this list is probably not complete now.  It may not even
|   ## be possible to build a statically linked copy of Octave that is
|   ## fully functional.

I'd be willing to try to fix the Makefiles, but there may still be
some problems.  The last time I tried to build a fully static version
on my Debian system, it failed to link because there some
dependencies were only available as shared libraries.  Also, there
will likely be some problems with trying to load .oct files, which are
normally built as shared libraries.

jwe


--
Rob Frohne, Ph.D., P.E.
E.F. Cross School of Engineering
Walla Walla University
100 SW 4th Street
College Place, WA 99324
(509) 527-2075                   http://people.wallawalla.edu/~rob.frohne

Attachment: rob_frohne.vcf
Description: Vcard


reply via email to

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