Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perl Base Tests Fail on paths with Space #13611

Open
p5pRT opened this issue Feb 18, 2014 · 5 comments
Open

Perl Base Tests Fail on paths with Space #13611

p5pRT opened this issue Feb 18, 2014 · 5 comments

Comments

@p5pRT
Copy link

@p5pRT p5pRT commented Feb 18, 2014

Migrated from rt.perl.org#121275 (status was 'open')

Searchable as RT121275$

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Feb 18, 2014

From DStaal@usa.net

Created by DStaal@usa.net

Perl 5.18.2 install tests fail with​:

t/base/term ................................................... sh​: /Volumes/Mac​: is a directory
FAILED at test 2

on my box. `/Volumes/Mac` is *not* a valid path on my box​: `/Volumes/Mac Users` is - it lookes like
the test was trying something in the make directory (which was under `/Volumes/Mac Users`), and couldn't
handle the space in the name.

Tests and install were fine once I moved the make (perl-5.18.2) directory to another path, which didn't have spaces.

(Box is an old Mac OS X box, with the 'Users' directory on a seperate disk from the system. `/Volumes` is where all
mounted non-root disks are placed.)

Daniel T. Staal

Perl Info

Flags:
    category=install
    severity=low

Site configuration information for perl 5.18.2:

Configured by danieltstaal at Tue Feb 18 00:12:12 EST 2014.

Summary of my perl5 (revision 5 version 18 subversion 2) configuration:
   
  Platform:
    osname=darwin, osvers=11.4.2, archname=darwin-thread-multi-2level
    uname='darwin mac-pro 11.4.2 darwin kernel version 11.4.2: thu aug 23 16:26:45 pdt 2012; root:xnu-1699.32.7~1release_i386 i386 '
    config_args=''
    hint=recommended, useposix=true, d_sigaction=define
    useithreads=define, usemultiplicity=define
    useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
    use64bitint=define, use64bitall=define, uselongdouble=undef
    usemymalloc=n, bincompat5005=undef
  Compiler:
    cc='cc', ccflags ='-fno-common -DPERL_DARWIN -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -I/opt/local/include',
    optimize='-O3',
    cppflags='-fno-common -DPERL_DARWIN -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -I/opt/local/include'
    ccversion='', gccversion='4.2.1 Compatible Apple LLVM 4.2 (clang-425.0.28)', gccosandvers=''
    intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
    d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
    ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
    alignbytes=8, prototype=define
  Linker and Libraries:
    ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc', ldflags =' -fstack-protector -L/usr/local/lib -L/opt/local/lib'
    libpth=/usr/local/lib /opt/local/lib /usr/lib
    libs=-lgdbm -ldbm -ldl -lm -lutil -lc
    perllibs=-ldl -lm -lutil -lc
    libc=, so=dylib, useshrplib=false, libperl=libperl.a
    gnulibc_version=''
  Dynamic Linking:
    dlsrc=dl_dlopen.xs, dlext=bundle, d_dlsymun=undef, ccdlflags=' '
    cccdlflags=' ', lddlflags=' -bundle -undefined dynamic_lookup -L/usr/local/lib -L/opt/local/lib -fstack-protector'

Locally applied patches:
    


@INC for perl 5.18.2:
    /usr/local/lib/perl5/site_perl/5.18.2/darwin-thread-multi-2level
    /usr/local/lib/perl5/site_perl/5.18.2
    /usr/local/lib/perl5/5.18.2/darwin-thread-multi-2level
    /usr/local/lib/perl5/5.18.2
    .


Environment for perl 5.18.2:
    DYLD_LIBRARY_PATH (unset)
    HOME=/Volumes/Mac Users/danieltstaal
    LANG=en_US.UTF-8
    LANGUAGE (unset)
    LC_ALL=C
    LD_LIBRARY_PATH (unset)
    LOGDIR (unset)
    PATH=/Volumes/Mac Users/danieltstaal/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/bin:/sbin:/usr/bin:/usr/games:.:/opt/local/bin:/opt/local/sbin:
    PERL_BADLANG (unset)
    SHELL=/bin/bash

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Feb 21, 2014

From @jkeenan

On Tue Feb 18 11​:32​:37 2014, DStaal@​usa.net wrote​:

This is a bug report for perl from DStaal@​usa.net,
generated with the help of perlbug 1.39 running under perl 5.18.2.

-----------------------------------------------------------------
[Please describe your issue here]

Perl 5.18.2 install tests fail with​:

t/base/term ................................................... sh​:
/Volumes/Mac​: is a directory
FAILED at test 2

on my box. `/Volumes/Mac` is *not* a valid path on my box​:
`/Volumes/Mac Users` is - it lookes like
the test was trying something in the make directory (which was under
`/Volumes/Mac Users`), and couldn't
handle the space in the name.

Tests and install were fine once I moved the make (perl-5.18.2)
directory to another path, which didn't have spaces.

(Box is an old Mac OS X box, with the 'Users' directory on a seperate
disk from the system. `/Volumes` is where all
mounted non-root disks are placed.)

Daniel T. Staal

[Please do not change anything below this line]
-----------------------------------------------------------------
---
Flags​:
category=install
severity=low
---
Site configuration information for perl 5.18.2​:

Configured by danieltstaal at Tue Feb 18 00​:12​:12 EST 2014.

Summary of my perl5 (revision 5 version 18 subversion 2)
configuration​:

Platform​:
osname=darwin, osvers=11.4.2, archname=darwin-thread-multi-2level
uname='darwin mac-pro 11.4.2 darwin kernel version 11.4.2​: thu aug
23 16​:26​:45 pdt 2012; root​:xnu-1699.32.7~1release_i386 i386 '
config_args=''
hint=recommended, useposix=true, d_sigaction=define
useithreads=define, usemultiplicity=define
useperlio=define, d_sfio=undef, uselargefiles=define, usesocks=undef
use64bitint=define, use64bitall=define, uselongdouble=undef
usemymalloc=n, bincompat5005=undef
Compiler​:
cc='cc', ccflags ='-fno-common -DPERL_DARWIN -fno-strict-aliasing
-pipe -fstack-protector -I/usr/local/include -I/opt/local/include',
optimize='-O3',
cppflags='-fno-common -DPERL_DARWIN -fno-strict-aliasing -pipe
-fstack-protector -I/usr/local/include -I/opt/local/include'
ccversion='', gccversion='4.2.1 Compatible Apple LLVM 4.2 (clang-
425.0.28)', gccosandvers=''
intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t',
lseeksize=8
alignbytes=8, prototype=define
Linker and Libraries​:
ld='env MACOSX_DEPLOYMENT_TARGET=10.3 cc', ldflags =' -fstack-
protector -L/usr/local/lib -L/opt/local/lib'
libpth=/usr/local/lib /opt/local/lib /usr/lib
libs=-lgdbm -ldbm -ldl -lm -lutil -lc
perllibs=-ldl -lm -lutil -lc
libc=, so=dylib, useshrplib=false, libperl=libperl.a
gnulibc_version=''
Dynamic Linking​:
dlsrc=dl_dlopen.xs, dlext=bundle, d_dlsymun=undef, ccdlflags=' '
cccdlflags=' ', lddlflags=' -bundle -undefined dynamic_lookup
-L/usr/local/lib -L/opt/local/lib -fstack-protector'

Locally applied patches​:

---
@​INC for perl 5.18.2​:
/usr/local/lib/perl5/site_perl/5.18.2/darwin-thread-multi-2level
/usr/local/lib/perl5/site_perl/5.18.2
/usr/local/lib/perl5/5.18.2/darwin-thread-multi-2level
/usr/local/lib/perl5/5.18.2
.

---
Environment for perl 5.18.2​:
DYLD_LIBRARY_PATH (unset)
HOME=/Volumes/Mac Users/danieltstaal
LANG=en_US.UTF-8
LANGUAGE (unset)
LC_ALL=C
LD_LIBRARY_PATH (unset)
LOGDIR (unset)
PATH=/Volumes/Mac
Users/danieltstaal/bin​:/usr/sbin​:/usr/local/bin​:/usr/local/sbin​:/bin​:/sbin​:/usr/bin​:/usr/games​:.​:/opt/local/bin​:/opt/local/sbin​:
PERL_BADLANG (unset)
SHELL=/bin/bash

In an attempt to understand this problem, I renamed the directory on the Dromedary server (Linux/x86_64) on which I customarily test Perl 5 blead from 'perl' to 'My Dir With Space', then built and tested blead.

The failures were massive -- too many to list. So I'm surprised you only got failures in one test file.

Nevertheless, I have to say that, IMO, anyone who tries to do serious software development in directories with spaces in their names is asking for trouble. Consequently, I don't think we should expend much effort in addressing this ticket.

Thank you very much.
Jim Keenan

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Feb 21, 2014

The RT System itself - Status changed from 'new' to 'open'

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Feb 21, 2014

From @bulk88

On Thu Feb 20 16​:12​:34 2014, jkeenan wrote​:

In an attempt to understand this problem, I renamed the directory on
the Dromedary server (Linux/x86_64) on which I customarily test Perl 5
blead from 'perl' to 'My Dir With Space', then built and tested blead.

The failures were massive -- too many to list. So I'm surprised you
only got failures in one test file.

Nevertheless, I have to say that, IMO, anyone who tries to do serious
software development in directories with spaces in their names is
asking for trouble. Consequently, I don't think we should expend much
effort in addressing this ticket.

Thank you very much.
Jim Keenan

Oh yes this is normal, there are a couple dozen .ts that fail. In POSIX all characters except / and NULL are valid as file names. More work needs to be done to make Perl whitespace path safe.

--
bulk88 ~ bulk88 at hotmail.com

@p5pRT
Copy link
Author

@p5pRT p5pRT commented Feb 23, 2014

From DStaal@usa.net

--As of February 20, 2014 4​:12​:34 PM -0800, James E Keenan via RT is
alleged to have said​:

In an attempt to understand this problem, I renamed the directory on the
Dromedary server (Linux/x86_64) on which I customarily test Perl 5 blead
from 'perl' to 'My Dir With Space', then built and tested blead.

The failures were massive -- too many to list. So I'm surprised you only
got failures in one test file.

Nevertheless, I have to say that, IMO, anyone who tries to do serious
software development in directories with spaces in their names is asking
for trouble. Consequently, I don't think we should expend much effort in
addressing this ticket.

--As for the rest, it is mine.

I only got failures in the one test file because `make test` stopped
immediately when it failed​: No further tests ran.

But I'll agree that this probably doesn't need to be high priority - if it
didn't come up before now it's not a major issue. (And I did recognize the
problem from the error message.) Just thought it should be something
people are aware of. I do think it should be fixed - eventually - but it's
not a huge issue.

Daniel T. Staal


This email copyright the author. Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes. This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant