On Sun, Mar 27, 2016 at 08:16:42PM -0700, Buddy Burden wrote:
> Well, I'll take your word for it, since I know you're a fellow who _really_
> knows what he's talking about. :-) It's just that this is the _only_ point
> of correlation with this particular failure that I've been able to find.
> It's
Tony,
From Porting/Glossary in the perl distribution:
config_args (Options.U):
This variable contains a single string giving the command-line
arguments passed to Configure. Spaces within arguments,
quotes, and escaped characters are not correctly preserved.
To
On Sun, Mar 27, 2016 at 02:09:05PM -0700, Buddy Burden wrote:
Subject: The meaning of config_args
>From Porting/Glossary in the perl distribution:
config_args (Options.U):
This variable contains a single string giving the command-line
arguments passed to Configure. Spaces within
Ron,
Reading this msg, none of us has a clue as to the code you've used :-).
Well, I'm not actually asking for help solving the actual _problem_ ...
I have a pretty good idea what the problem is, and even how to fix it.
The problem is, I can't actually _reproduce_ the problem on my machine.
Hi Buddy
On 28/03/16 08:09, Buddy Burden wrote:
Guys,
Okay, trying to track down what's causing a certain quite prolific
failure in my initial module upload. Here's what I've been able to
determine (I'm pretty confident of almost all these numbers):
92% of reports with an empty config_args[1]
Guys,
Okay, trying to track down what's causing a certain quite prolific
failure in my initial module upload. Here's what I've been able to
determine (I'm pretty confident of almost all these numbers):
92% of reports with an empty config_args[1] pass
100% of reports with a *non*-empty config
