bugGNU Octave - Bugs: bug #47367, mkoctfile does not work in Windows

 
 

bug #47367: mkoctfile does not work in Windows

Submitted by:  Philip Nienhuis <philipnienhuis>
Submitted on:  Wed 09 Mar 2016 07:55:23 AM UTC  
 
Category:  Octave Function Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Regression
Status:  Fixed Assigned to:  None
Originator Name:  Philip Nienhuis Open/Closed:  Closed
Release:  dev Operating System:  Microsoft Windows

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 10 Mar 2016 11:01:05 PM UTC, comment #13: 

I can confirm that this is finally fixed.
Closing report.

Philip Nienhuis <philipnienhuis>
Project Member
Thu 10 Mar 2016 08:18:11 PM UTC, comment #12: 

I'm crossbuilding on my other machine now with fresh core Octave & mxe-octave clones; on this desktop it didn't seem to work.
I really hope that it fixes several build problems I had lately.

Philip Nienhuis <philipnienhuis>
Project Member
Thu 10 Mar 2016 05:18:24 PM UTC, comment #11: 

The changeset in comment #7 fixed the issue with mkoctfile not working for me.

Im rebuilding packages now to see which ones still fail for me

John Donoghue <lostbard>
Project Member
Thu 10 Mar 2016 04:14:59 AM UTC, comment #10: 

After 21425 (29e8d4a922b5) I get better results than before.

A lot more pkgs install with build_packages

mxe and dev branch.

Doug Stewart <dastew>
Wed 09 Mar 2016 10:00:08 PM UTC, comment #9: 

Still does not work :-(

I verified, my build tree is at fdb9adcc02f9 "don't substitute SONAME_FLAGS"

There are more problems with the cross-build; I get 26 FAILS with _run_test_suite_, several related to not recognizing the JAVA JRE, some others related to tolerances.

Tomorrow night I'll investigate further.

Philip Nienhuis <philipnienhuis>
Project Member
Wed 09 Mar 2016 06:24:51 PM UTC, comment #8: 

Thanks for the prompt fix, I'll try tonight,

Philip Nienhuis <philipnienhuis>
Project Member
Wed 09 Mar 2016 06:20:02 PM UTC, comment #7: 

I checked in the following changeset:

http://hg.savannah.gnu.org/hgweb/octave/rev/29e8d4a922b5

Sorry I forgot to add this bug report number to the commit message...

John W. Eaton <jwe>
Project Administrator
Wed 09 Mar 2016 05:31:41 PM UTC, comment #6: 

Yes, it was so that they could be expanded on the command line, but that probably never worked properly anyway because values changed on the command line wouldn't necessarily be inserted into the various files.  So now I'm trying to prevent inconsistencies like that from happening.  Expanding them in the configure script is probably the right thing to do.

John W. Eaton <jwe>
Project Administrator
Wed 09 Mar 2016 05:06:14 PM UTC, comment #5: 

Due to this change;

http://hg.savannah.gnu.org/hgweb/octave/rev/1aa293d58df0

I wonder if we could simply expand the MKOCTFILE_XXX vars in configure.ac now? I guess that this was deferred to allow variables to be changed on the make command-line?

Mike Miller <mtmiller>
Project Administrator
Wed 09 Mar 2016 05:04:54 PM UTC, comment #4: 

OK, I'll fix this.

John W. Eaton <jwe>
Project Administrator
Wed 09 Mar 2016 04:58:47 PM UTC, comment #3: 

Same on latest dev

build-aux/subst-config-vals.sh: line 117: shell: command not found
build-aux/subst-config-vals.sh: line 118: shell: command not found
build-aux/subst-config-vals.sh: line 119: shell: command not found
build-aux/subst-config-vals.sh: line 120: shell: command not found
build-aux/subst-config-vals.sh: line 122: shell: command not found
build-aux/subst-config-vals.sh: line 123: shell: command not found
build-aux/subst-config-vals.sh: line 124: shell: command not foun

when subst-config-vals.sh is created, the MKOCTFILE_XXX variables are all now in the form of:

MKOCTFILE_AR="$(shell echo ${AR} | ${SED} "s,${CROSS_TOOL_PREFIX},,")

ie: the values from configure are being used as make variables without being expanded to the final value they would be.

John Donoghue <lostbard>
Project Member
Wed 09 Mar 2016 01:46:50 PM UTC, comment #2: 

Looking at the build log in mxe when using 74a676d5ce09 of octave, I have a number of build-aux/subst-config-vals.sh: shell: command not found just before creating mkoctfile.

In windows, using mkoctfile -p CXX returns an empty line

I am going to try the latest dev octave

John Donoghue <lostbard>
Project Member
Wed 09 Mar 2016 11:26:27 AM UTC, comment #1: 

I also saw this problem.

Doug Stewart <dastew>
Wed 09 Mar 2016 07:55:23 AM UTC, original submission:  

With latest Octave tip (7ce76114b321), cross-built with latest mxe-octave (513a335905f0), once in Windows mkoctfile does not work:

>> mkoctfile csv2cell.cc
mkoctfile: no way to compile C++ file csv2cell.cc
warning: mkoctfile: building exited with failure status
warning: called from
    mkoctfile at line 171 column 5

Running mkoctfile-4.1.0+ directly in an msys shell makes no difference.

Philip Nienhuis <philipnienhuis>
Project 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 mtmiller (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by lostbard (Posted a comment)
  • -email is unavailable- added by dastew (Posted a comment)
  • -email is unavailable- added by philipnienhuis (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.

     

     

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-03-10 philipnienhuis StatusReady For Test => Fixed
        Open/ClosedOpen => Closed
    2016-03-09 philipnienhuis StatusNone => Ready For Test

    Back to the top


    Powered by Savane 3.5