in reply to Re: XCOFF32 object files are not allowed in 64-bit mode
in thread XCOFF32 object files are not allowed in 64-bit mode

Thanks much for looking at this.. is there any alternative which dont make me remove perl 32 and install perl 64 and solve this situation... Also, if i had to move to perl 64., how can i get all my installed modules in 32-bit env.. again i need to install them?
  • Comment on Re^2: XCOFF32 object files are not allowed in 64-bit mode

Replies are listed 'Best First'.
Re^3: XCOFF32 object files are not allowed in 64-bit mode
by Corion (Patriarch) on Feb 02, 2016 at 13:48 UTC

    According to this random manpage for ld, maybe you can/have to add -b32 to the LD= line in Makefile to make ld work in 32-bit mode.

    If that works, you can either explicitly reconfigure and recompile your perl (and all modules) to have the -b32 parameter in the LD invocation or you can try patching lib/Config_heavy.pl and add the -b32 there and pray that everything still works.

      Thanks Guys for your help.. Finally i got one solution... instead of using perl modules that are built with 'C' language, i now use built-in perl module... in this case it is "Digest::SHA::PurePerl module." Now there is no overhead of 32-bit/64-bit... (may be this solution is bit slow, but satisfied my hunger from last 2 days) :-)
        instead of using perl modules that are built with 'C' language, i now use built-in perl module

        Given that you want a 32-bit perl, I think that's a fair enough solution - though a more interesting (and more efficient) solution would be to get Digest-SHA working.

        Corion's suggestion sounds promising - I've had good success in the past messing with config_heavy.pl settings on Windows. (It sometimes requires a matching change to Config.pm as well.)
        However, on all of my systems (Windows, Ubuntu and Debian), $Config{ld} is set to the same as $Config{cc} and I'm not sure how that impacts when it comes to altering LD.

        Cheers,
        Rob