octave-dev

[OctDev] Problems building comm-docs

[Kay L. <kay...@we...>]

Hello,

I try to build a Port for Freebsd, but I have some problems building the
docs from the comm-package, which I don't know how to solve. The
Versions I use are:
octave-2.1.39 and octave-forge 2003.06.02
Error messages are:

Making texinfo comms.texi
Making info comms.info
comms.texi:2445: Node `Linear Algebra' previously defined at line 2099.
comms.texi:2499: Node `Signal Processing' previously defined at line
2153.
comms.texi:2574: Node `Function Reference' previously defined at line
2228.
comms.texi:2793: Node `Linear Algebra' previously defined at line 2099.
comms.texi:2847: Node `Signal Processing' previously defined at line
2153.
comms.texi:2922: Node `Function Reference' previously defined at line
2228.
comms.texi:3143: Node `Linear Algebra' previously defined at line 2099.
comms.texi:3197: Node `Signal Processing' previously defined at line
2153.
comms.texi:3272: Node `Function Reference' previously defined at line
2228.
comms.texi:3495: Node `Linear Algebra' previously defined at line 2099.
comms.texi:3549: Node `Signal Processing' previously defined at line
2153.
....
and so on. Everything else seems fine. Can somebody tell me how to fix
this?

Thanks in advance.
Kay Lehmann

-- 
Kay Lehmann <kay...@we...>

[OctDev] Automatically generated files and RPM binaries

[Quentin S. <qsp...@ie...>]

I think I mentioned on one of the lists a while ago that I had written a 
spec file for generating RPM binaries, and I recall RPM binaries being 
mentioned recently by someone else. The file I currently have has two 
strings that will change from one build to the next: the current octave 
version and current octave-forge version. I would like to make it so 
these are taken care of automatically, but I'm trying to figure out when 
this should happen. The octave version is detected at the configure 
stage. The octave-forge version is not detected anywhere that I can 
tell, but it is set in release.sh. I suppose it may be possible to grep 
OCTAVE_FORGE_VERSION.m to find it out when configuring, but I'm not sure 
what makes the most sense and I'm not that familiar with the GNU 
autotools. Suggestions?

Quentin Spencer

Re: [OctDev] Problems building comm-docs

[David B. <Dav...@mo...>]

This is weird.. Can you type "make comms.texi" in the main/comm directory
and send me the comms.texi file it generates? I can't seem to generate the
same problem. Could you also type "makeinfo --version" and tell me what version
of makeinfo you have installed..

Cheers
David


According to Kay Lehmann <kay...@we...> (on 06/08/03):
> Hello,
> 
> I try to build a Port for Freebsd, but I have some problems building the
> docs from the comm-package, which I don't know how to solve. The
> Versions I use are:
> octave-2.1.39 and octave-forge 2003.06.02
> Error messages are:
> 
> Making texinfo comms.texi
> Making info comms.info
> comms.texi:2445: Node `Linear Algebra' previously defined at line 2099.
> comms.texi:2499: Node `Signal Processing' previously defined at line
> 2153.
> comms.texi:2574: Node `Function Reference' previously defined at line
> 2228.
> comms.texi:2793: Node `Linear Algebra' previously defined at line 2099.
> comms.texi:2847: Node `Signal Processing' previously defined at line
> 2153.
> comms.texi:2922: Node `Function Reference' previously defined at line
> 2228.
> comms.texi:3143: Node `Linear Algebra' previously defined at line 2099.
> comms.texi:3197: Node `Signal Processing' previously defined at line
> 2153.
> comms.texi:3272: Node `Function Reference' previously defined at line
> 2228.
> comms.texi:3495: Node `Linear Algebra' previously defined at line 2099.
> comms.texi:3549: Node `Signal Processing' previously defined at line
> 2153.
> ....
> and so on. Everything else seems fine. Can somebody tell me how to fix
> this?
> 
> Thanks in advance.
> Kay Lehmann
> 
> -- 
> Kay Lehmann <kay...@we...>
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by:  Etnus, makers of TotalView, The best
> thread debugger on the planet. Designed with thread debugging features
> you've never dreamed of, try TotalView 6 free at www.etnus.com.
> _______________________________________________
> Octave-dev mailing list
> Oct...@li...
> https://lists.sourceforge.net/lists/listinfo/octave-dev

-- 
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 25 00 (Ph)
Espace Technologique, Commune de St Aubin    +33 1 69 35 25 01 (Fax)
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

Re: [OctDev] Problems building comm-docs

[Kay L. <kay...@we...>]

Am Sa, 2003-05-10 um 11.22 schrieb David Bateman:
> This is weird.. Can you type "make comms.texi" in the main/comm directory
> and send me the comms.texi file it generates? I can't seem to generate the
> same problem. Could you also type "makeinfo --version" and tell me what version
> of makeinfo you have installed..
> 
> Cheers
> David
> 
> 
Hello,

first of all I want to thank you for your answer. Here are the infos you
wanted:

makeinfo --version: makeinfo (GNU texinfo) 4.2

comms.texi is attached (gziped). 

Thanks for your help.
Greetings,
Kay
-- 
Kay Lehmann <kay...@we...>

Re: [OctDev] Problems building comm-docs

[David B. <Dav...@mo...>]

Your file comms.txi is completely stuffed up as it has multiple versions
of each section. It seems that there might have been a cvs checkout problem..
Can you remove it and do a cvs update to recover it. It also seems to be
correct in the latest release...

Cheers
David

According to Kay Lehmann <kay...@we...> (on 06/10/03):
> Am Sa, 2003-05-10 um 11.22 schrieb David Bateman:
> > This is weird.. Can you type "make comms.texi" in the main/comm directory
> > and send me the comms.texi file it generates? I can't seem to generate the
> > same problem. Could you also type "makeinfo --version" and tell me what version
> > of makeinfo you have installed..
> > 
> > Cheers
> > David
> > 
> > 
> Hello,
> 
> first of all I want to thank you for your answer. Here are the infos you
> wanted:
> 
> makeinfo --version: makeinfo (GNU texinfo) 4.2
> 
> comms.texi is attached (gziped). 
> 
> Thanks for your help.
> Greetings,
> Kay
> -- 
> Kay Lehmann <kay...@we...>



-- 
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 25 00 (Ph)
Espace Technologique, Commune de St Aubin    +33 1 69 35 25 01 (Fax)
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary

Re: [OctDev] Problems building comm-docs

[Kay L. <kay...@we...>]

On Tue, 2003-06-10 at 12:46, David Bateman wrote:
> Your file comms.txi is completely stuffed up as it has multiple versions
> of each section. It seems that there might have been a cvs checkout problem..
> Can you remove it and do a cvs update to recover it. It also seems to be
> correct in the latest release...
> 
> Cheers
> David
> 
Hmm,

this is a little bit weired. First of all I have to say that I use
latest release and comms.txi is exactly the same as in cvs. So I think
this is a problem with the mkdoc and mktexi scripts which are used in
the comm-module to create the texi-file. To be exactly: it seems to be a
problem with perl-version, which comes with FreeBSD4. Maybe it is to
old? It's version 5.00503. I have tested my theory with FreeBSD5.1,
which comes with perl5.6 and now it is working without any problems.

So, thanks again for your help.
Greetings,
Kay
-- 
Kay Lehmann <kay...@we...>

Re: [OctDev] Problems building comm-docs

[David B. <Dav...@mo...>]

You are probably right. But in this case a test should be added for
the version of perl to ensure that the file is compiled correctly. I
have a 5.6.1 version installed and it works. On an old redhat 7.2
machine I have 5.005_03 and it has similar issues to what you have
seen.

At this point without know which version work, a warning should probably
be given if the version in earlier than 5.6.0

cheers
David

According to Kay Lehmann <kay...@we...> (on 06/10/03):
> On Tue, 2003-06-10 at 12:46, David Bateman wrote:
> > Your file comms.txi is completely stuffed up as it has multiple versions
> > of each section. It seems that there might have been a cvs checkout problem..
> > Can you remove it and do a cvs update to recover it. It also seems to be
> > correct in the latest release...
> > 
> > Cheers
> > David
> > 
> Hmm,
> 
> this is a little bit weired. First of all I have to say that I use
> latest release and comms.txi is exactly the same as in cvs. So I think
> this is a problem with the mkdoc and mktexi scripts which are used in
> the comm-module to create the texi-file. To be exactly: it seems to be a
> problem with perl-version, which comes with FreeBSD4. Maybe it is to
> old? It's version 5.00503. I have tested my theory with FreeBSD5.1,
> which comes with perl5.6 and now it is working without any problems.
> 
> So, thanks again for your help.
> Greetings,
> Kay
> -- 
> Kay Lehmann <kay...@we...>

-- 
David Bateman                                Dav...@mo...
Motorola CRM                                 +33 1 69 35 25 00 (Ph)
Espace Technologique, Commune de St Aubin    +33 1 69 35 25 01 (Fax)
91193 Gif-Sur-Yvette FRANCE

The information contained in this communication has been classified as: 

[x] General Business Information 
[ ] Motorola Internal Use Only 
[ ] Motorola Confidential Proprietary