bugGNU Octave - Bugs: bug #50249, Build fails if a parent directory...

 
 

bug #50249: Build fails if a parent directory contains a whitespace

Submitted by:  Martin Castillo <castilma>
Submitted on:  Wed 08 Feb 2017 12:34:02 AM UTC  
 
Category: Configuration and Build SystemSeverity: 1 - Wish
Priority: 1 - LaterItem Group: Build Failure
Status: Wont FixAssigned to: None
Originator Name: Open/Closed: Closed
Release: 4.2.0Operating System: GNU/Linux

Add a New Comment(Rich Markup)
   

You are not logged in

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

 

Wed 08 Feb 2017 05:31:30 AM UTC, comment #2:

I would mark this as won't fix. The specific error message here comes from libtool, which is completely outside of Octave's control to do anything about.

Here is an example of a shell code line that may be causing this error in the upstream libtool project:

https://git.savannah.gnu.org/cgit/libtool.git/tree/build-aux/ltmain.in#n6631

Martin - you are correct if you are talking about other autotools-based projects. You might want to raise the issue with the GNU libtool project to see if there is any interest in accepting patches to allow building in directories and files with spaces. There may also be some parts of autoconf and/or automake that assume a file name can be used unquoted. If you can get the upstream projects fixed to accept names with spaces, then we can look at whether Octave's build files need any tweaking.

Mike Miller <mtmiller>
Project Administrator
Wed 08 Feb 2017 04:56:06 AM UTC, comment #1:

On UNIX, and equivalent operating systems like Linux, a space character is special. The common practice is never to use spaces in directory or file names. If necessary, use an underscore "_" to replace a space in names.

Rik <rik5>
Project Administrator
Wed 08 Feb 2017 12:34:02 AM UTC, original submission:

I get the following error while building.

The full path is divided somewhere because of the whitespace.
This is not the first project that failed to build on my machine because of this. I'm starting to ask myself if there is any convention to not put source directories under directories with spaces in the name.
If not, is this maybe an autoconf bug?

Martin Castillo <castilma>

 

(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

Items that depend on this one: None found

 

Carbon-Copy List
  • -unavailable- added by mtmiller (Posted a comment)
  • -unavailable- added by rik5 (Posted a comment)
  • -unavailable- added by castilma (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
    Wed 08 Feb 2017 05:42:21 AM UTCrik5StatusNone=>Wont Fix
      Open/ClosedOpen=>Closed
    Wed 08 Feb 2017 04:56:06 AM UTCrik5Severity3 - Normal=>1 - Wish
      Priority5 - Normal=>1 - Later
      SummaryBuild fails, if a parent directory contains a whitespace=>Build fails if a parent directory contains a whitespace

    Back to the top


    Powered by Savane 3.1-cleanup1