Re: Problem with Symbolic package in octave-forge 2004.07.07

[Paul Kienzle]

On Jul 21, 2004, at 9:40 PM, grumpy steve wrote:

> Shai
> Good suggestions, and this might indeed be the problem, but I'm not
> convinced.  All of the components have been built with V3.3.1 of the 
> gnu
> compiler set, and, although this doesn't rule out the possibility that 
> some
> dependent libraries might have changed.  What I have noticed is that 
> some of
> the .oct files in the most recent octave-forge release did build 
> correctly
> and appear to work, while some (most significantly and, for me, 
> annoyingly,
> the symbols package) did not.  I'm wondering whether it has anything 
> to do
> with the fact that I'm using a cygwin environment rather than a native 
> posix
> one.  Has anyone succeeded in building the whole shooting match under
> Cygwin, and, if so, were there any steps that needed to be taken, or
> parameters that needed to be supplied in addition to the basic
> configure-make-install cycle.  If all else fails, I'll just re-build
> everything, but I expect it will end up taking days!

Or in my case, months, but I don't have much time to
spend on it ;-)

I've got a version of octave 2.1.57 on my machine
with symbolic, gsl, geometry, hdf5, fftw3, gnuplot 3.8k
and read/write png/jpg functions.

I put the libraries that I use on the octave-forge
download site.  They can be untarred into /usr/local,
or following my packaging for windows suggestions
on wiki.octave.org RFC1, in /opt/octave-2.1.xx.  Each
package contains doc/README.<package>,
lib/, include/ and possibly bin/ if it contains DLLs.

I'm still not ready for a new octave windows release
but this set of packages might make it easier for you
to build your own octave-forge.  Please let me know.

Warning: I haven't updated my cygwin distribution
in a couple of years, so things may seem out of
date.  This is by design---recent gcc versions for
cygwin have done something brutal to malloc functions,
really slowing down octave, and they haven't been
fixed yet.  The upshot of this is that ./configure on
my machine may have found compiler/library
features which are not available on your version
of cygwin, so my binary packages may not work for you.

Paul Kienzle
address@hidden


> Steve
>
> -----Original Message-----
> From: Shai Ayal [mailto:address@hidden
> Sent: 20 July 2004 07:17
> To: grumpy steve
> Cc: address@hidden
> Subject: Re: Problem with Symbolic package in octave-forge 2004.07.07
>
> You probably did this already, but just to make sure, this is the order
> of building these things:
>
> first do whatever upgrade to cygwin you want or need using the cygwin
> setup program
>
> now do a clean compile/install of octave
>
> now do a clean compile/install of octave-forge
>
> I think you error messages might stem from compiling different bits of
> your setup with different compiler/library versions. Using the above
> order of building should eliminate this uncertainty at least.
>
>         Shai
>
> grumpy steve wrote:
> > Hi
> >
> > I'm a real novice, so please be very patient with me if I say 
> > something
> > stupid.  You are, however, permitted to laugh if I say something
> > inadvertently funny - all I would ask is that you let me in on the 
> > joke!
> >
> > I've been trying to get octave 2.1.57 + octave-forge 2004.07.07 
> > working
> > on my WinXP PC using a very recent download of Cygwin.  Most things 
> > work
> > well, and I am altogether hugely impressed.  However, sadly, one of 
> > the
> > packages in which I'm most interested, the symbolic package from
> > octave-forge, is proving more stubborn, almost certainly because I 
> > don't
> > know how to build it properly.  I have downloaded, built and installed
> > cln-1.1.8, GiNaC-1.2.1, and octave-forge, and I did end up with a
> > "symbols.oct" file on the appropriate path, along with a large number 
> > of
> > ".oct" files symbolically linked to it.  However, whenever I try to
> > execute any of the functions in the symbols.oct, I get the message
> > "error: dlopen: Win32 error 998".  I have a strong suspicion that
> > something hasn't linked correctly, meaning that symbols.oct is broken,
> > and quite possibly, incomplete, but such is my ignorance I don't have
> > the slightest idea how to fix it.  I could try rebuilding everything
> > starting off with different options to the configure step, or, heaven
> > forbid, start messing about with makefiles, but given the time it 
> > takes
> > to build everything, it might be a very long time before I get 
> > anywhere.
> >
> > All suggestions welcome, and all ridicule tolerated.
> >
> > Steve
>
> --
> Shai Ayal, Ph.D.
> Head of Research
> BioControl Medical BCM
> 3 Geron St.
> Yehud 56100
> ISRAEL
> Tel:  + 972 3 6322 126
> Fax:  + 972 3 6322 125
> email: address@hidden
>
>
>
> -------------------------------------------------------------
> Octave is freely available under the terms of the GNU GPL.
>
> Octave's home on the web:  http://www.octave.org
> How to fund new projects:  http://www.octave.org/funding.html
> Subscription information:  http://www.octave.org/archive.html
> -------------------------------------------------------------
>
>
>
>
>
> -------------------------------------------------------------
> Octave is freely available under the terms of the GNU GPL.
>
> Octave's home on the web:  http://www.octave.org
> How to fund new projects:  http://www.octave.org/funding.html
> Subscription information:  http://www.octave.org/archive.html
> -------------------------------------------------------------



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------