Skip Menu |

This queue is for tickets about the Machine-Epsilon CPAN distribution.

Report information
The Basics
Id: 98971
Status: resolved
Priority: 0/
Queue: Machine-Epsilon

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 1.00
Fixed in: (no value)



Subject: Check for 32/64 bit perl does not work
There are a couple of problems: * `which perl` would give you the first perl in PATH, but not necessarily the perl which is currently in use for running the test. Use $^X instead (also, "which" is not available on non-Unix platforms, as an additional problem) * `file ...` may return results like "symbolic link to ...". And again, this is Unix-only. It's probably better to use the Config module and look at something like byteorder, archname, ivsize or so...
On Thu Sep 18 14:22:41 2014, SREZIC wrote: Show quoted text
> There are a couple of problems: > * `which perl` would give you the first perl in PATH, but not > necessarily the perl which is currently in use for running the test. > Use $^X instead (also, "which" is not available on non-Unix platforms, > as an additional problem) > * `file ...` may return results like "symbolic link to ...". And > again, this is Unix-only. It's probably better to use the Config > module and look at something like byteorder, archname, ivsize or so...
Thanks for your feedback. I hope to have a fix in place today.
On Thu Sep 18 14:22:41 2014, SREZIC wrote: Show quoted text
> There are a couple of problems: > * `which perl` would give you the first perl in PATH, but not > necessarily the perl which is currently in use for running the test. > Use $^X instead (also, "which" is not available on non-Unix platforms, > as an additional problem) > * `file ...` may return results like "symbolic link to ...". And > again, this is Unix-only. It's probably better to use the Config > module and look at something like byteorder, archname, ivsize or so...
I have released 1.0.1 which fixes this issue.
On Mon Nov 03 22:32:28 2014, BINARY wrote: Show quoted text
> On Thu Sep 18 14:22:41 2014, SREZIC wrote:
> > There are a couple of problems: > > * `which perl` would give you the first perl in PATH, but not > > necessarily the perl which is currently in use for running the test. > > Use $^X instead (also, "which" is not available on non-Unix platforms, > > as an additional problem) > > * `file ...` may return results like "symbolic link to ...". And > > again, this is Unix-only. It's probably better to use the Config > > module and look at something like byteorder, archname, ivsize or so...
> > Thanks for your feedback. I hope to have a fix in place today. > >
1.0.1 corrects this problem