Per Persson | 1 Aug 14:56 2003
Picon

Re: more on octave & OS X

Hi all,
if I read peoples mail more carefully, I would save myself (and other 
people) a lot of time.
(imagine the sound of my head banging aginst a brick wall...)

Of course it is the stream reading bug[1] reported previously that 
causes this.
I recompiled octave using gcc 3.3 and voila! reading -mat4-binary works.

Updating the dev-tools and recompiling octave should fix Andy's problem.

/Per

[1] There was a bug in libstc++ provided with gcc 3.1 which caused the 
final byte of a file to be dropped.

Andy wrote:

> Hi All,
>
>         First, I want to report that I've downloaded and compiled
>         octave-2.1.46 and 2.1.48, both with Apple's g++ 3.1, and they
>         both have this trouble reading binary data.  So I cannot
>         confirm Per's observation that 2.1.46 is OK.  Pertaining to a
>         comment by Jeff, please note that I do not have Apple's g++
>         3.3.  I misspoke when I said I had Apple's latest devtools--I
>         had forgotten the fink warning that 3.3 is too buggy to use
>         right now.
> Also, Jeff, I could not compile octave-2.1.50 with
>         g++2; it failed with unrecognized characters in UGLY_DEFS when
(Continue reading)

Andy Jacobson | 1 Aug 15:27 2003
Picon

Re: more on octave & OS X

>>>>> "Per" == Per Persson <persquare <at> mac.com> writes:

    Per> Of course it is the stream reading bug[1] reported previously
    Per> that causes this.  I recompiled octave using gcc 3.3 and
    Per> voila! reading -mat4-binary works.

    Per> Updating the dev-tools and recompiling octave should fix
    Per> Andy's problem.

    Per> [1] There was a bug in libstc++ provided with gcc 3.1 which
    Per> caused the final byte of a file to be dropped.

Thanks, Per.  The final byte problem is almost certainly the issue;
reading a binary file with two or more matrices stored in it generates
a stream state problem only upon reading the last variable.

Unfortunately, there exists a pragmatic problem with gcc 3.3--it is
strongly discouraged to use the latest dev tools with fink [1].  Among
many other dire warnings, fink developers claim that fortran breaks
completely with gcc 3.3 from Apple.

Is libstdc++ always dynamically linked?  Can one build a completely
statically-linked octave with the gcc 3.3 developer tools, then use
that executable on a machine that does not have those tools?  That
might be a nice interim solution until fink gets everything sorted
out.

        Thanks again,

                Andy
(Continue reading)

Per Persson | 1 Aug 16:10 2003
Picon

Re: more on octave & OS X


On fredag, aug 1, 2003, at 15:27 Europe/Stockholm, Andy Jacobson wrote:
>
> Is libstdc++ always dynamically linked?  Can one build a completely
> statically-linked octave with the gcc 3.3 developer tools, then use
> that executable on a machine that does not have those tools?  That
> might be a nice interim solution until fink gets everything sorted
> out.

Right, (taking the risk of exposing how little know about this stuff)
I think that octave is indeed linking libstdc++ statically and that it 
should work to switch to gcc 3.3, build octave
and then switch back to gcc 3.1

/Per

-------------------------------------------------------------
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
-------------------------------------------------------------

Andy Jacobson | 1 Aug 16:21 2003
Picon

Re: more on octave & OS X

>>>>> "Per" == Per Persson <persquare <at> mac.com> writes:

    Per> I think that octave is indeed linking libstdc++ statically
    Per> and that it should work to switch to gcc 3.3, build octave
    Per> and then switch back to gcc 3.1

...except that according to the fink people, one cannot simply switch
back to gcc 3.1, once the Dec 2002 dev tools patch (taking you to gcc
3.3) is applied.  It's a one-way street!

If you already have a gcc-3.3 statically-linked executable, could you
perhaps make it available to the community?

        Thanks,
                Andy

--

-- 
Andy Jacobson

andyj <at> splash.princeton.edu

Program in Atmospheric and Oceanic Sciences
Sayre Hall, Forrestal Campus
Princeton University
PO Box CN710 Princeton, NJ 08544-0710 USA

Tel: 609/258-5260  Fax: 609/258-2850

-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.
(Continue reading)

John W. Eaton | 1 Aug 21:37 2003
Picon

Problems configuring octave on FreeBSD

On  8-Jun-2003, Pedro F. Giffuni <giffunip <at> yahoo.com> wrote:

| I'm using the latest development octave (2.1.48) on FreeBSD 5.0R
| and configure is doing some really wrong things;
| 
| 1) I have blas and ATLAS installed on /usr/local/lib but it
| doesn't find them, and it's not clean in the documetation how to
| add -lf77blas -latlas -L/usr/local/lib. lapack is not detected
| either.

Something like

  configure LDFLAGS="-L/usr/local/lib"

should work.  The configure script will check for "-lf77blas -latlas"
but since you apparently don't have them installed where your compiler
normally looks for libraries, you have to add the location of the
libraries to LDFLAGS.

| 2) I don't have gnuplot but the configure script detects it.

That is very strange.  Can you please try to debug why that happens?

jwe

-------------------------------------------------------------
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
(Continue reading)

Bernt Guldbrandtsen | 5 Aug 14:12 2003
Picon

Compilation problems: Octave-2.1.50, gcc-3.3, AIX 4.3.3

Hi,

Compiling of recent development versions (including 2.1.50) of octave with 
gcc-3.3 and the AIX-linker fails with unresolved symbol errors under AIX-4.3.3.

After building the rest of the octave-2.1.50 distribution

	cd octave-2.1.50
	make >& make.log

resulted in the output shown below. More complete linker output (including 
the -Wl,bnoquiet option for the linker) is available at 
http://genetics.agrsci.dk/~bg/make.log.gz

I checked, that Array.o is in fact included in liboctave.a. Output of ar t 
liboctave.a | grep Array is shown below.

Is this due to a problem specific gcc-3.3? I have compiled previous 
versions of octave (including 2.1.48) with previous versions of gcc-3 
including revisions of gcc-3.2.

Any help would be appreciated!

Best regards,

Bernt Guldbrandtsen
################### GCC version ########################################
GNU C Compiler
gcc -v
Reading specs from /usr/local/lib/gcc-lib/rs6000-ibm-aix4.3.3.0/3.3/specs
(Continue reading)

Axel Heim | 7 Aug 00:06 2003
Picon
Picon

error reading multi-line text applying 'system'-function

The file 'sample.tr' contains a sample of bigger files which I use
regards.

To: bug-octave <at> bevo.che.wisc.edu
Cc: axel
Subject: error reading multi-line text applying 'system'-function
--------
Bug report for Octave 2.1.50 configured for i386-pc-linux-gnu

Description:
-----------

  * When reading a multi-line text file (one column) into a vector of 
characters, the number of read lines is smaller than the total number of 
lines. This happens only sometimes when calling the same function 
several times.

Repeat-By:
---------

  * no sequence, just one line:
    f_lines(q) = str2num(system(["wc ",file{q,1}," | awk '{print $1}'"]));

Fix:
---

  * just now, I repeat calling this line until the number of read lines 
is correct

Configuration (please do not edit this section):
(Continue reading)

Sam Halliday | 13 Aug 15:29 2003
Picon

octave-2.1.49 not finding libs

hi there,

using GNU/Linux form Scratch, i upgraded from octave-2.1.44 to octave-2.1.49 and
now octave does not start up:

octave: error while loading shared libraries: liboctinterp.so: cannot open
shared object file: No such file or directory

the file does exist however in /usr/lib/octave

i went back to version 2.1.44 to see if i had messed up the compile, but by
using the exact same command line options in installing both versions, 2.1.44
works whereas 2.1.49 breaks.

i compiled with gcc-3.2.3

./configure --prefix=/usr --enable-shared --enable-dl --libexecdir=/usr/lib

i cannot even fix this by setting LD_LIBRARY_PATH. this is really weird. has
anyone else experienced this?

cheers,
Sam
PS: please CC responses to me
Ole Jacob Hagen | 13 Aug 17:40 2003
Picon

Re: octave-2.1.49 not finding libs

Hi.

I believe that the install-script in Octave is "broken".
I had to move octave-libraries to the /usr/lib/octave manually, 
and edit the /etc/ld.so.conf -file, and run /sbin/ldconfig, and now your Octave-installation should work.

Cheers, 

Ole J. 

On Wed, 13 Aug 2003 14:29:37 +0100
Sam Halliday <fommil <at> yahoo.ie> wrote:

> hi there,
> 
> using GNU/Linux form Scratch, i upgraded from octave-2.1.44 to octave-2.1.49 and
> now octave does not start up:
> 
> octave: error while loading shared libraries: liboctinterp.so: cannot open
> shared object file: No such file or directory
> 
> the file does exist however in /usr/lib/octave
> 
> i went back to version 2.1.44 to see if i had messed up the compile, but by
> using the exact same command line options in installing both versions, 2.1.44
> works whereas 2.1.49 breaks.
> 
> i compiled with gcc-3.2.3
> 
> ./configure --prefix=/usr --enable-shared --enable-dl --libexecdir=/usr/lib
(Continue reading)

Sam Halliday | 13 Aug 16:13 2003
Picon

Re: octave-2.1.49 not finding libs

Geraint Paul Bevan wrote:
> Sam Halliday wrote:
> > using GNU/Linux form Scratch, i upgraded from octave-2.1.44 to
> > octave-2.1.49 and now octave does not start up:
> If it does exist and is a shared object, I've no idea why
> LD_LIBRARY_PATH wouldn't work, but you could perhaps try running
> ldconfig on the directory manually to see if any errors are reported.

this fixed it, but i dont think it is a preferred solution. i much prefer the
octave-2.1.44 behaviour where there is no need to fiddle with /etc/ld.co.conf

cheers,
Sam
--

-- 
Death is nature's way of saying `Howdy'.

Gmane