* David E. Wheeler <[EMAIL PROTECTED]> [2008-02-25 20:05]:
> I'd probably make :utf8 the default, and apply it to STDOUT
> and STDERR if running on Perl 5.6 or later. That way, any
> time something is emitted via diag() that is in Perl's internal
> encoding, it will work (provided, of course, that
On 25 Feb 2008, at 23:59, Michael G Schwern wrote:
Andy Armstrong wrote:
Is there a generally approved way for an XS module to test for the
existence of a C compiler before attempting to build?
MakeMaker uses ExtUtils::CBuilder->have_compiler() in it's tests.
It's worked well with no compl
Andy Armstrong wrote:
Is there a generally approved way for an XS module to test for the
existence of a C compiler before attempting to build?
MakeMaker uses ExtUtils::CBuilder->have_compiler() in it's tests. It's worked
well with no complaints. It's an additional testing dependency, but it'
# from chromatic
# on Monday 25 February 2008 14:45:
>Are there ways in which use CPAN 1.92 (); doesn't work in this case?
> I've assumed so far that it does.
Well, we seem to avoid requiring them because it is a burden on the
manual install case (and we would have to require both CPAN and
CPA
On Monday 25 February 2008 14:24:56 David Golden wrote:
> To chromatic's point about "people don't want to install stuff" --
> they do want to install stuff, but -- to generalize from my own point
> of view -- they don't want to have to manually figure out what the
> dependencies are based on what
On Mon, Feb 25, 2008 at 4:09 PM, Eric Wilhelm
<[EMAIL PROTECTED]> wrote:
> >I think configure_requires is a great idea, as long as one also puts
> >"use 5.010;" at the top of the Build.PL and Makefile.PL.
>
> Perhaps the CPAN(PLUS) needs to be upgraded. Would you be extolling the
You're right.
On 25 Feb 2008, at 21:36, David Cantrell wrote:
I'm using Devel::CheckLib and relying on David Cantrell to make it
all
work. If there's a problem in his compiler detection logic it's more
likely to get fixed quickly than it is if I roll some ad-hoc code of
my own. It's also more likely to get d
On Mon, Feb 25, 2008 at 06:49:13PM +, Andy Armstrong wrote:
> On 25 Feb 2008, at 18:44, David Cantrell wrote:
> > Devel::CheckLib's _findcc() function ...
> And quite splendid it appears to be, thanks :)
> Did I miss a mention in the documentation of its use to detect merely
> compiler pre
On Mon, Feb 25, 2008 at 06:47:32PM +, Andy Armstrong wrote:
> On 25 Feb 2008, at 18:42, Guy Hulbert wrote:
> >You still need to figure out whether to check 'ccversion' or
> >'gccversion' to when $Config{cc} can be either 'cc' or 'gcc' and also
> >how to find the '--version' string on windows ..
On Monday 25 February 2008 13:09:39 Eric Wilhelm wrote:
> We always install the latest version of a dependency dist (jagged edges
> and all -- except if it was not indexed[1]), so why include stale
> versions of some odd number of build tools in the tarball? Why not
> just bundle 3 (or 7) compile
# from David Golden
# on Monday 25 February 2008 12:50:
>Assuming that a recent CPAN.pm is installed that knows what to do with
>configure_requires.
>
>Is it me or does this list have some variation of this discussion
>every couple weeks? :-)
I guess that's about how often I post ;-)
>I think co
On Mon, Feb 25, 2008 at 2:25 PM, Eric Wilhelm
<[EMAIL PROTECTED]> wrote:
> >> May not be MakeMaker, but would ExtUtils::CBuilder::have_compiler()
> >> work?
> >
> >It should, but it's not always installed.
>
> Just 'configure_requires' it?
Assuming that a recent CPAN.pm is installed that kn
# from David Golden
# on Monday 25 February 2008 10:55:
>> May not be MakeMaker, but would ExtUtils::CBuilder::have_compiler()
>> work?
>
>It should, but it's not always installed.
Just 'configure_requires' it?
--Eric
--
I arise in the morning torn between a desire to improve the world and a
On Feb 24, 2008, at 12:02, Michael G Schwern wrote:
Test::Builder dups STDERR and STDOUT, this is so you can mess with
them to your heart's content and still get testing done. File I/O
disciplines don't appear to be copied across dups. That's what
everyone was complaining about, that they
On Mon, Feb 25, 2008 at 1:32 PM, Curtis Jewell
<[EMAIL PROTECTED]> wrote:
> May not be MakeMaker, but would ExtUtils::CBuilder::have_compiler()
> work?
It should, but it's not always installed.
Devel::Checklib is designed to make life easy by bundling itself into
an inc/ directory in the distri
On 25 Feb 2008, at 18:44, David Cantrell wrote:
Devel::CheckLib's _findcc() function first looks to see if the Config
variable is -x-able. If it's not, it looks everywhere in the
$ENV{PATH}
for it, which is what 'which' is supposed to do.
And quite splendid it appears to be, thanks :)
Did
On 25 Feb 2008, at 18:42, Guy Hulbert wrote:
You still need to figure out whether to check 'ccversion' or
'gccversion' to when $Config{cc} can be either 'cc' or 'gcc' and also
how to find the '--version' string on windows ... but it looks doable.
I'm using Devel::CheckLib and relying on David
On Mon, Feb 25, 2008 at 06:33:29PM +, Andy Armstrong wrote:
> On 25 Feb 2008, at 18:30, Guy Hulbert wrote:
> > `which $Config{cc} --version` =~ m/$Config{gccversion}/
> >seems to "work" for all the combinations below ... but I can imagine
> >that there are situations where it might not.
> See
On 25 Feb 2008, at 18:30, Guy Hulbert wrote:
On Mon, 2008-02-25 at 13:22 -0500, Guy Hulbert wrote:
something as
horrible as:
-x `which $Config{cc}`
plus:
`which $Config{cc} --version` =~ m/$Config{gccversion}/
seems to "work" for all the combinations below ... but I can imagine
On 25 Feb 2008, at 18:10, Guy Hulbert wrote:
On Mon, 2008-02-25 at 16:29 +, Andy Armstrong wrote:
Personally I'd like such a test to be standard in MakeMaker,
because
I am
of the (old fashioned) opinion that if %Config says that there is a
C
compiler and there isn't one, then it's lying
# from Ricardo SIGNES
# on Monday 25 February 2008 04:59:
>Basically, it lets you say "author_tests('xt')" in your Makefile.PL
> (using Module::Install) to have a directory (or directory tree) of
> tests run only by the module's authors.
Now we only have to determine 'author'ness. I was thinking
On 25 Feb 2008, at 16:35, David Golden wrote:
Look at Devel::Checklib. If you don't select any libraries, I believe
it still checks for a compiler.
Oh, so it does. I looked at it, quickly scanned assert_lib and
concluded that it wouldn't work - but now I see that _findcc can die.
Cool, tha
On Mon, Feb 25, 2008 at 10:59 AM, Andy Armstrong <[EMAIL PROTECTED]> wrote:
> Is there a generally approved way for an XS module to test for the
> existence of a C compiler before attempting to build?
Look at Devel::Checklib. If you don't select any libraries, I believe
it still checks for a com
On 25 Feb 2008, at 16:25, Nicholas Clark wrote:
On Mon, Feb 25, 2008 at 03:59:14PM +, Andy Armstrong wrote:
Is there a generally approved way for an XS module to test for the
existence of a C compiler before attempting to build?
Personally I'd like such a test to be standard in MakeMaker,
On Mon, Feb 25, 2008 at 03:59:14PM +, Andy Armstrong wrote:
> Is there a generally approved way for an XS module to test for the
> existence of a C compiler before attempting to build?
Personally I'd like such a test to be standard in MakeMaker, because I am
of the (old fashioned) opinion th
Is there a generally approved way for an XS module to test for the
existence of a C compiler before attempting to build?
I'd like to avoid test failures that result from the lack of a
compiler without risking failing to build on a system that has an
obscure compiler that the build system wo
I thought I'd relay my journal post here:
http://use.perl.org/~rjbs/journal/35746
Basically, it lets you say "author_tests('xt')" in your Makefile.PL (using
Module::Install) to have a directory (or directory tree) of tests run only by
the module's authors.
--
rjbs
27 matches
Mail list logo
