version number in mercurial

[Carlo de Falco-2]

After several failed attempts I finally managed to build sources fron
the savannah repository (pulled this morning) on my macbook with OSX  
10.5.7.

When running the newly built binary I noticed that the version is  
still set to 3.1.55 and I was wondering whether, given that 3.2.0 is  
now out, this shold rather be 3.3.x or 3.2.1 or anything else > 3.2.0?

Sorry if this is a silly question, it's just that I am curios about  
how the version numbering works...
c.

P.S. My build was done using gcc4.2 from Xtools and g95 and all other  
dependencies from fink, all attempts to use gcc4.3 or 4.4 and gfortran  
failed for me, has anyone managed to build octave with gfortran on OSX?

[Jean-Francois Cardoso]

Carlo de Falco-2 wrote:

After several failed attempts I finally managed to build sources fron
the savannah repository (pulled this morning) on my macbook with OSX  
10.5.7.

[....]
P.S. My build was done using gcc4.2 from Xtools and g95 and all other  
dependencies from fink, all attempts to use gcc4.3 or 4.4 and gfortran  
failed for me, has anyone managed to build octave with gfortran on OSX?

Yes, I managed to build 3.2.0 (not mercurial's tip, though)
wtih some inputs from the list (using the ff2c swith now seems
to be necessary on the Mac) and by installing
the latest gfortran *and* gcc from  http://hpc.sourceforge.net

However, I do not have a working setup yet because some of
my home-made oct files (interfacing octave to a FITS library) are
now broken.  I do not have time+skills to debug this by myself,
so I am back to gcc 4.2 and to octave 3.0.5.  

I hope that MacOS 10.6 will come with an updated gcc
which may clear up this issue.   Anyone knows about that ?

Cheers, JF

[John W. Eaton-3]

On 10-Jun-2009, Carlo de Falco wrote:

| When running the newly built binary I noticed that the version is  
| still set to 3.1.55 and I was wondering whether, given that 3.2.0 is  
| now out, this shold rather be 3.3.x or 3.2.1 or anything else > 3.2.0?

Yeah, I just haven't changed it yet.  The next snapshot will likely be
3.3.0, so then the version number in the mercurial archive will be set
to 3.3.0+.

jwe