Re: Perl Distribution differences for i686/x86

If you're running `uname -m` in backticks you're just getting the output of the uname command on the host OS, so not a Perl Issue. You could try POSIX::uname and see if you get anything more useful.

Comment on Re: Perl Distribution differences for i686/x86_64 and ia64 over Linux. Download Code

Replies are listed 'Best First'.
Re^2: Perl Distribution differences for i686/x86_64 and ia64 over Linux. by jpl (Monk) on Apr 12, 2011 at 13:27 UTC
This, too, was a good call. I put the emulator directory at the start of my search path, just to make sure POSIX wasn't using the system uname to determine its output, then ran a quick debugging session. PATH=/emul/ia32-linux/bin:$PATH perl -de 0 Loading DB routines from perl5db.pl version 1.3 Editor support available. Enter h or `h h' for help, or `man perldebug' for more help. main::(-e:1): 0 DB<1> use POSIX DB<2> x POSIX::uname 0 'Linux' 1 'frodo' 2 '2.6.16.60-0.60.1-default' 3 '#1 SMP Tue Mar 9 09:44:12 UTC 2010' 4 'ia64' [download]	[reply] [d/l]
Re^3: Perl Distribution differences for i686/x86_64 and ia64 over Linux. by salva (Canon) on Apr 12, 2011 at 13:53 UTC
`POSIX::uname()` does not call the external uname(1) program but the uname(2) syscall that, depending on the instruction set for which the running program was compiled, returns `ia64` or `i686`. So, calling `POSIX::uname()` is not going to solve the OP problem.	[reply] [d/l] [select]