bugGNU Octave - Bugs: bug #62408, strange errors when running...

 
 

bug #62408: strange errors when running "bootstrap" script

Submitter:  Pascal Dupuis <cdemills>
Submitted:  Tue 03 May 2022 04:30:46 PM UTC
   
 
Category:  Configuration and Build System Severity:  2 - Minor
Priority:  3 - Low Item Group:  Build Failure
Status:  Wont Fix Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * 7.1.0 Operating System:  * GNU/Linux
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 04 May 2022 01:11:35 PM UTC, comment #8: 

Sometimes things like our use of gnulib change in ways that require a clean checkout or a completely clean build tree.  Those kinds of changes don't happen frequently I don't think it is worth any effort to "fix" this problem in the bootstrap script.

John W. Eaton <jwe>
Group administrator
Wed 04 May 2022 09:23:43 AM UTC, comment #7: 


> The dir was checkout in January, 2014. I think I was using Fedora 16. Then I worked by incrementally pulling from Octave main repository at each new release and running the 'bootstrap' script.


Aah yes. That could be an explanation.

Imho, it is probably not worth the effort to adapt the `bootstrap` script to handle the case when it is executed in a very old checkout (and deviate from the upstream version even further).

I'm closing this as "won't fix" because the workaround of deleting the "gnulib" folder before running `./bootstrap` is pretty easy in comparison. I'd also guess that you'll probably not need to delete that folder again any time soon.
If you (or anyone else) would like to work on this, please let us know and we can re-open.

Markus Mützel <mmuetzel>
Group administrator
Wed 04 May 2022 09:09:52 AM UTC, comment #6: 


commentaire #5 :

> I'm guessing now that the gnulib Git repository didn't get updated correctly for you by the `bootstrap` script for some reason and that repository was still pretty old. Do you have an idea why that could be?
>
> Was the source tree very old? A couple of years ago, Octave hosted its own gnulib clone and included it as a Mercurial subrepository. Now, we are letting the `bootstrap` script fetch the upstream Git repository instead. Maybe, that could fail if the Mercurial subdirectory wasn't deleted in the local checkout...
>


Hmmm ... The dir was checkout in January, 2014. I think I was using Fedora 16. Then I worked by incrementally pulling from Octave main repository at each new release and running the 'bootstrap' script. This occured around 33 times.

My guess is that one of those incremental pull didn't go well, or , as you said, that there were both old-style mercurial and new-style git files lying around.

So starting 'gnulib' from scratch was the right cure.

Regards

Pascal


Pascal Dupuis <cdemills>
Group Member
Wed 04 May 2022 08:43:04 AM UTC, comment #5: 

Sorry, I misunderstoof. I thought that `m4/acinclude.m4` would be "included" in the `configure` script. It is not included in the `bootstrap` script. Because editing `m4/acinclude.m4` avoided the error, I thought that meant that it was emitted by the `configure` script.

However, the `bootstrap` script creates the `configure` script from `configure.ac` using those autom4te modules.
The `gl_PROG_BISON` module was added to gnulib in May 2020:
https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=6c71b2c51bc633f230054d9496d6bb2f0c1d4874

Octave updated to a newer version than that before the release of version 6.1.0:
https://hg.savannah.gnu.org/hgweb/octave/rev/7b819cd7ff54

I'm guessing now that the gnulib Git repository didn't get updated correctly for you by the `bootstrap` script for some reason and that repository was still pretty old. Do you have an idea why that could be?

Was the source tree very old? A couple of years ago, Octave hosted its own gnulib clone and included it as a Mercurial subrepository. Now, we are letting the `bootstrap` script fetch the upstream Git repository instead. Maybe, that could fail if the Mercurial subdirectory wasn't deleted in the local checkout...

Markus Mützel <mmuetzel>
Group administrator
Wed 04 May 2022 08:04:51 AM UTC, comment #4: 


commentaire #3 :

> Thank you for clarifying.
>
> I'm not sure how running the `bootstrap` script could result in an error from the `configure` script. They should not be calling each other...
>
> We'd probably need some steps to reproduce the error before we can try to fix it.
>
> Lowering the priority for now.


Title says it: the error occurs during "bootstrap". So it's before launching the 'configure' script.
Regards
Pascal

Pascal Dupuis <cdemills>
Group Member
Wed 04 May 2022 07:59:17 AM UTC, comment #3: 

Thank you for clarifying.

I'm not sure how running the `bootstrap` script could result in an error from the `configure` script. They should not be calling each other...

We'd probably need some steps to reproduce the error before we can try to fix it.

Lowering the priority for now.

Markus Mützel <mmuetzel>
Group administrator
Wed 04 May 2022 07:44:23 AM UTC, comment #2: 


commentaire #1 :

> What is "bootstrap.sh"? Do you mean the `bootstrap` script in the root of the source tree (not ending in ".sh")? Or is there another script with that name?
>
> Did you build from the tarball of 7.1.0? Or from a Mercurial checkout? In the latter case, which hg id?
>
> Which exact error messages did you see?
>


Hello
Sorry, I was a bit vague.
Platform: CentOS 8 Stream x86-64; gcc-8.5.0. Sources checked out from hg with ID 30904 (release-7-1-0). After that I ran './bootsrap' (without .sh). Previous compilation in January, 2022: the gnulib dir was last updated at this date. I can't reproduce the problem anymore, but from memory it was "autoconf: missing module bison". This error went away after commenting out,
in m4/acinclude.m4:3078:
AC_DEFUN([OCTAVE_PROG_BISON], [
  dnl FIXME: What is our actual required minimum version for Bison?
  gl_PROG_BISON([BISON], [3.0])

the 'gl_PROG_BISON' macro

Regards

Pascal

Pascal Dupuis <cdemills>
Group Member
Wed 04 May 2022 07:24:04 AM UTC, comment #1: 

What is "bootstrap.sh"? Do you mean the `bootstrap` script in the root of the source tree (not ending in ".sh")? Or is there another script with that name?

Did you build from the tarball of 7.1.0? Or from a Mercurial checkout? In the latter case, which hg id?

Which exact error messages did you see?

Markus Mützel <mmuetzel>
Group administrator
Tue 03 May 2022 04:30:46 PM UTC, original submission:  

Dear all,
After pulling the new 7.1.0 revision, the 'bootstrap' step failed with strange messages about bison not available, autoconf missing bison module, ...

FYI I compiled 6.4.0 a few month ago.

Then I pulled a fresh copy of the repository, where this step worked. The fix in my case is to completelly remove the 'gnulib' subdir and call 'bootstrap' once more.

It seems that updating gnulib by executing "bootstrap" may fail; the simplest cure is create a fresh copy.

Regards

Pascal

Pascal Dupuis <cdemills>
Group Member

 

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

Attach Files:
   
   
Comment:
   

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 jwe (Posted a comment)
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by cdemills (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 8 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2022-05-04 mmuetzel StatusWorks For Me Wont Fix
        Open/ClosedOpen Closed
    2022-05-04 mmuetzel CategoryOther Configuration and Build System
        Severity3 - Normal 2 - Minor
        Priority5 - Normal 3 - Low
        StatusNeed Info Works For Me
        Summarystrange errors when running &quot;bootstrap.sh&quot; strange errors when running "bootstrap" script
    2022-05-04 mmuetzel StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-caa5.
    Corresponding source code