[perl #40286] Configure problem in a build directory with spaces inthe name

On Tue, 25 Sep 2012 14:20:55 GMT, pcm wrote:
> On Mon Jun 01 09:40:06 2009, doughera wrote:
> > This patch at least allows the build to finish.  There are a number of 
> > test failures still due to the spaces in the directory name.
> > 
> > commit 4291ccc37ced038dfc84c91175fda3d5e05590c4
> > Author: Andy Dougherty <doughera@lafayette.edu>
> > Date:   Mon Jun 1 12:34:36 2009 -0400
> > 
> >     Protect against spaces in build directory name when extracting .PL 
> > files
> > 
> > --- 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
> > 
> 
> On blead, I can run configure with a space in my directory name but do
> still see those test failures.
> 
> 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
> that form and send a patch.

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.
-- 
James E Keenan (jkeenan@cpan.org)

---
via perlbug:  queue: perl5 status: open
https://rt.perl.org/Ticket/Display.html?id=40286

• [perl #40286] Configure problem in a build directory with spaces in the name by Peter Martini via RT
• [perl #40286] Configure problem in a build directory with spaces inthe name by James E Keenan via RT