BIND 10 #1041: BIND10 build fails if a directory in the path has spaces

[BIND 10 Development]

#1041: BIND10 build fails if a directory in the path has spaces
-------------------------------------+-------------------------------------
                   Reporter:  cas    |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  Next-Sprint-
                   Priority:  major  |  Proposed
                  Component:         |            Resolution:
  configuration                      |             Sensitive:  0
                   Keywords:         |           Sub-Project:  Core
            Defect Severity:         |  Estimated Difficulty:  3.0
  Medium                             |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by cas):

 Replying to [comment:2 jinmei]:
 > Do we really want to solve this?
 >
 > Did it happen in someone's normal environment, or is it just as a
 > result of testing pathological cases?

 it was happen to me in a normal environment (I unpacked the source of BIND
 10 from a tgz file using the MacOS X finder, which creates a directory
 using the same name as the tgz file. The tgz file had a space).

 While hving a space in the path is uncommon in Unix environments, it is
 quite common on Windows. So it might become a problem for users trying to
 compile on windows (and they might not notice what the problem is from the
 error message given).

 A quick fix might be a check script in the make file that will give a
 meaningful error message early in the build process like 'BIND 10 cannot
 build from a path that contains spaces. exit'

 > If it's the latter, I think
 > the priority is quite low (in fact this doesn't seem to specific to
 > BIND 10, and I suspect many other products would fail to compile
 > in this situation).

 I've tested BIND 9 and unbound, and both also fail. it is a problem of
 proper quoting for the shell, but I agree that this is an upstream problem
 with autotools.

 -- Carsten

-- 
Ticket URL: <http://bind10.isc.org/ticket/1041#comment:4>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development