bugGNU Octave - Bugs: bug #35588, Documentation bugs in octave or...


bug #35588: Documentation bugs in octave or OpenBSD

Submitted by:  Edd Barrett <vext01>
Submitted on:  Wed 22 Feb 2012 11:19:51 AM UTC  
Category:  Configuration and Build System Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Build Failure
Status:  Fixed Assigned to:  None
Originator Name:  Open/Closed:  Closed
Release:  dev Operating System:  BSD

Add a New Comment(Rich Markup)

You are not logged in

Please log in, so followups can be emailed to you.


( Jump to the original submission)

Thu 08 Aug 2013 03:08:30 AM UTC, comment #8:

I am able to build the development version of Octave completely on OpenBSD 5.3 with --disable-docs and ran into no such problems with documentation or makeinfo/texinfo, so this has been fixed somewhere in the development branch.

I would say yes to bumping the default Fortran to gfortran 4.x to match gcc 4.x and rebuilding all Fortran libs.

Mike Miller <mtmiller>
Project Administrator
Tue 06 Aug 2013 08:11:16 AM UTC, comment #7:

Having thought a little more. I recommend you install (into /opt) lapack and blas from source manually using gfortran. Then you can install octave's other dependencies from packages.

If you can get to a point where the latest version of octave builds, installs and runs under the above configuration, that will be a huge step forward.

At that stage, I would be willing to look into whether we can bump the default fortran compiler in OpenBSD on GCC4 architectures.

Edd Barrett <vext01>
Tue 06 Aug 2013 07:48:34 AM UTC, comment #6:

Hi Mike,

Sadly I garbage collected much of my website only a few weeks ago.

IIRC there were patches to build blas and lapack with a different fortran compiler than the system default. Looking at my OpenBSD system it looks like g77 is the default compiler, but gfortran is also available. I think there was an issue with mixing object files from g77 with code compiled by gcc4???

There were also patches to turn off the optimiser for certain object files as the fortran compiler was buggy.

I think I am going to have to have a dig around for the files in the link below, as the above info is too vague. I am not even sure if the above applies any more.

Edd Barrett <vext01>
Tue 06 Aug 2013 04:54:42 AM UTC, comment #5:

I happen to have an OpenBSD VM up and running. You mention that some steps are needed to get blas and lapack configured, can you link to instructions on how to do that? The link provided in comment #4 is now broken.

Mike Miller <mtmiller>
Project Administrator
Thu 23 Feb 2012 02:25:59 PM UTC, comment #4:


I have uploaded detailed instructions and patches here:

I really hope we can get this working. Thanks for your help.

Edd Barrett <vext01>
Thu 23 Feb 2012 12:49:27 AM UTC, comment #3:

I can install OpenBSD in a virtual machine, but I don't want to have to become an expert with OpenBSD to do that, so you'll have to tell me precisely step by step what to do.

John W. Eaton <jwe>
Project Administrator
Wed 22 Feb 2012 11:03:16 PM UTC, comment #2:

That was starting afresh. Infact, I have no option. OpenBSD ports ensures you can not reconfigure without untarring afresh.

Rik -- I see you have replied to a few of my bug reports, perhaps you have realised by now, octave does not work on OpenBSD (although some part our fault perhaps). Would you be interested helping us?

The main hurdle is finding an ocatve developer who is willing to install OpenBSD on a spare machine... There are a few hurdles to jump regarding blas and lapack, but i have diffs for this.

Perhaps we can talk on irc? Where do you hang?

Edd Barrett <vext01>
Wed 22 Feb 2012 04:58:34 PM UTC, comment #1:

Try starting over completely from the base tar.gz file. The documentation is pre-built and is distributed in the tarball. Only if you have 'touched' files and updated timestamps will there be a problem.

tar xf octave-tarball.tar.gz
cd octave-build-directory

You shouldn't need the --disable-docs options at all.

Rik <rik5>
Project Administrator
Wed 22 Feb 2012 11:19:51 AM UTC, original submission:


With the 3.6.1rc0 tarball on OpenBSD, I get some errors relating to .texi files:

I tried again with --disable-docs:

OpenBSD uses texinfo 4.8 in it's base distribution - the latest in 4.13. Our version is probably too old, but I would expect --disable-docs to prevent building of all docs?


Edd Barrett <vext01>


(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

No files currently attached


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by vext01 (Submitted the item)

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.


    Please enter the title of George Orwell's famous dystopian book (it's a date):



    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    Thu 08 Aug 2013 03:08:30 AM UTC mtmiller StatusNeed Info => Fixed
        Open/ClosedOpen => Closed
    Tue 06 Aug 2013 04:54:42 AM UTC mtmiller Item GroupNone => Build Failure
        StatusNone => Need Info

    Back to the top

    Powered by Savane 3.1-cleanup1