bugGNU Octave - Bugs: bug #44640, strings package: fails to compile...

 
 

bug #44640: strings package: fails to compile in windows

Submitted by:  John Donoghue <lostbard>
Submitted on:  Thu 26 Mar 2015 08:52:41 PM UTC  
 
Category: Octave Forge PackageSeverity: 3 - Normal
Priority: 5 - NormalItem Group: Build Failure
Status: FixedAssigned to: None
Originator Name: JohnDOpen/Closed: Closed
Release: devOperating System: Microsoft Windows

Add a New Comment(Rich Markup)
   

You are not logged in

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

 

Sat 06 Jun 2015 09:51:30 PM UTC, comment #5:

I have also added the PCRE_CPPFLAGS in the Makefile. The package installs cleanly on Octave Windows now using the pkg command.

Oliver Heimlich <oheim>
Mon 01 Jun 2015 06:31:52 PM UTC, comment #4:

Thanks for the PCRE_CPPFLAGS hint. I can easily add that too.

I think that cross-compilation is no “official” use case for the src/Makefile at the moment. You probably have to adjust other Makefiles, which make use of $(OCTAVE), for cross-compilation as well.

Oliver Heimlich <oheim>
Mon 01 Jun 2015 06:06:38 PM UTC, comment #3:

This is the same kind of change I made in the communications package to find the values of HDF5_* variables.

Oliver: You probably want to use the value of PCRE_CPPFLAGS as well, even if it is empty for most distros, and maybe even MXE, you probably shouldn't depend on that being true. Can you add that as well?

Cross-compiling is a separate issue, if that's something important we should probably open a bug for mkoctfile to put out more useful variables.

Mike Miller <mtmiller>
Project Administrator
Mon 01 Jun 2015 04:21:09 PM UTC, comment #2:

The only issue I see with this is that mxe-octave wont be able to use the value of octave_config_info during the mxe build process as it is cross compiled binary.

It should however work for a standard -forge install in Windows

John Donoghue <lostbard>
Project Member
Mon 01 Jun 2015 03:36:02 PM UTC, comment #1:

I have patched the Makefile in the Octave Forge repository with a mechanism that uses octave_config_info from Octave for the correct compile switches.

The bug can be closed.

Oliver Heimlich <oheim>
Thu 26 Mar 2015 08:52:41 PM UTC, original submission:

On running both the released, and whats in mercurial for the strings package:

It doesn't like the way the Makefile is trying to find the libraries, most likely due to windows file names having the '\' in them.

If

is changed to

It compiles OK.

The issue of course will then be systems that don't have pcre-config

John Donoghue <lostbard>
Project Member

 

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

Attach File(s):
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Digest:
   bug dependencies.

 

Carbon-Copy List
  • -unavailable- added by oheim (Posted a comment)
  • -unavailable- added by mtmiller (Updated the item)
  • -unavailable- added by lostbard (Submitted the item)
  •  

    Do you think this task is very important?
    If so, you can click here to 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 5 latest changes.

    Date Changed By Updated Field Previous Value => Replaced By
    Sat 06 Jun 2015 10:00:59 PM UTCmtmillerStatusIn Progress=>Fixed
      Open/ClosedOpen=>Closed
    Wed 03 Jun 2015 08:11:37 PM UTCmtmillerDependencies-=>bugs #45250 is dependent
    Mon 01 Jun 2015 06:06:38 PM UTCmtmillerStatusNone=>In Progress
    Sun 31 May 2015 05:21:07 PM UTCmtmillerSummaryoctave-forge strings fails to install in windows=>strings package: fails to compile in windows

    Back to the top


    Powered by Savane 3.1-cleanup1