Configure problem in a build directory with spaces in the name #8586
Comments
From @denimadeptOn the Mac, paths may contain spaces. This broke my "make": [x-ray:~/dev/perl/perl-5.8.8] hshubs% make Making DynaLoader (static) |
From guest@guest.guest.xxxxxxxxOn Wed Sep 06 09:42:25 2006, howard@shubs.net wrote:
Barring my missing something obvious, isn't this a problem more with the |
|
The RT System itself - Status changed from 'new' to 'open' |
From @denimadeptOn Wednesday, September 6, 2006, perlbug-followup@perl.org (Guest via RT) said:
No, I don't think so. The volume name is either "/Volumes/X-Ray Boot" or "/Volumes/X-Ray Users", depending on what it's trying to do. "/Volumes/X-Ray Boot" is the destination, and is mounted as /, so I don't think that's the one it means. I expect it's trying to refer to the source directory which is on "/Volumes/X-Ray Users". If the problem were the hyphen, the error text would have stopped at /Volume/X or complained about bad qualifiers/modifiers, which isn't what it did. Instead, it stopped where the space is. Since there is no location /Volumes/X-Ray, Configure fails when trying to refer to it. |
From cmoore@hellyeah.orgOn Wed Sep 06 14:26:27 2006, howard@shubs.net wrote:
My mistake. I didn't see the Boot/Users the first time around. |
From @smpetersOn Wed, Sep 06, 2006 at 05:14:15PM -0400, Howard S Shubs wrote:
I haven't yet pinpointed the actual problem, but it is not unique to Mac OS X. Steve Peters |
From @doughera88On Thu, 7 Sep 2006, Steve Peters wrote:
Actually, it occurs in lib/ExtUtils/MM_Unix.pm. This band-aid of a patch Inline Patchdiff -r -u perl-5.8.x/lib/ExtUtils/MM_Unix.pm perl-5.8.x-andy/lib/ExtUtils/MM_Unix.pm
--- perl-5.8.x/lib/ExtUtils/MM_Unix.pm 2006-06-13 15:31:11.000000000 -0400
+++ perl-5.8.x-andy/lib/ExtUtils/MM_Unix.pm 2006-09-07 11:57:38.000000000 -0400
@@ -1920,6 +1920,9 @@
$self->{ABSPERL} = 'MCR '.$self->{ABSPERL} if $has_mcr;
}
+ # Escape spaces in the path to ABSPERL (for Makefile expansion)
+ $self->{ABSPERL} =~ s/ /\\ /g;
+
# Are we building the core?
$self->{PERL_CORE} = $ENV{PERL_CORE} unless exists $self->{PERL_CORE};
$self->{PERL_CORE} = 0 unless defined $self->{PERL_CORE};
-- Andy Dougherty doughera@lafayette.edu |
From @doughera88This patch at least allows the build to finish. There are a number of commit 4291ccc Protect against spaces in build directory name when extracting .PL Inline Patch--- perl-current/Makefile.SH 2009-05-26 15:14:14.000000000 -0400
+++ perl-andy/Makefile.SH 2009-06-01 12:24:51.481678988 -0400
@@ -965,7 +965,7 @@
$(plextract): miniperl$(EXE_EXT) $(CONFIGPM) x2p/s2p
@-rm -f $@
- $(LDLIBPTH) $(RUN) ./miniperl$(EXE_EXT) -I`pwd`/lib $@.PL
+ $(LDLIBPTH) $(RUN) ./miniperl$(EXE_EXT) -I"`pwd`/lib" $@.PL
x2p/s2p: miniperl$(EXE_EXT) $(CONFIGPM) x2p/s2p.PL
cd x2p; $(LDLIBPTH) $(MAKE) s2p
-- Andy Dougherty doughera@lafayette.edu |
From PeterCMartini@GMail.comOn Mon Jun 01 09:40:06 2009, doughera wrote:
On blead, I can run configure with a space in my directory name but do Most are of the form: `$^X -le "print 'hi there'"` Can that portably be changed to: `"$^X" -le "print 'hi there'"` ? If that's portable enough, I'll go through all of the test failures of |
From @jkeenanOn Tue, 25 Sep 2012 14:20:55 GMT, pcm wrote:
Posters to this ticket: Is the issue of spaces in filenames still important enough that we should keep this ticket open? Thank you very much. |
From @hvdsOn Fri, 29 Dec 2017 05:40:42 -0800, jkeenan wrote:
I'm not a previous poster to this ticket, but I do consider this a bug in perl that we should fix. I suspect there may be multiple open tickets on the same general subject; if so, I think either there should be only one or they should be gathered under a meta-ticket. Hugo |
Migrated from rt.perl.org#40286 (status was 'open')
Searchable as RT40286$
The text was updated successfully, but these errors were encountered: