Text 1974, 102 rader
Skriven 2011-11-29 19:32:31 av Dave Yeo
Ärende: Re: Problem configuring OS/2 for installing CPAN packages
=================================================================
Firefox/8.0.1 SeaMonkey/2.5
DXC=f=NQjMC8D3S?W?WaA<e5APL?0kYOcDh@Z:A^o>K6GhCSE3=kG9hhb7RDfFNQVaeXVS7L_PK1nQceV\JRTl1FdLPQDE`]a04iRaW[7cBlglXZ0Y

comp.os.os2.ecomstation:1130 comp.os.os2.misc:3734
From: Dave Yeo <dave.r.yeo@gmail.com>

Jumping in to try to clarify a few things,

Ben Morrow wrote:
>
> Quoth Shmuel (Seymour J.) Metz<spamtrap@library.lspace.org.invalid>:
>> In<QIadnRHMSrAkpUnTnZ2dnUVZ8sydnZ2d@bt.com>, on 11/28/2011
>>     at 07:43 PM, Ben Morrow<ben@morrow.me.uk>  said:
>>
>>> Is this a standard OS/2 build of perl from the perl source,
>>
>> It's a 5.10.0 build from
>> <http://download.smedley.info/perl-5.10.0-os2-20071227.zip>.
>
> OK. That site doesn't seem to say anything about patches applied to
> perl, but it does seem to build everything against a libc with some sort
> of Cygwin-like Unix emulation layer. Since the perl libraries are
> expecting OS/2 to use OS/2 paths (starting with a drive letter) I'm not
> sure that is the most helpful thing to do.

Klibc is actually a fork of EMX, understands drive letters fine along 
with both types of directory separators.

>
>>> README.os2 doesn't mention anything about any path remapping.
>>
>> I believe that 5.8.0 was the last official OS/2 build. I don't know
>> whether the path remapping is something that Paul Smedley or whether
>> it was in the source.
>
> When you say 'official' do you mean the builds Ilya used to do? There
> are no official binary builds of perl (for any platform): the only
> release supported by p5p is the source release.

5.8.0 is the last build that trivially built out of the box (using EMX) 
though I don't think Ilya ever released a 5.8.0.

> If you were on a Unix
> system I would at this point be suggesting you install a proper dev
> environment and build perl yourself from the source tarball. I don't
> know whether that's something you would be able to do, but IME getting
> MakeMaker and the CPAN shell to work with pre-packaged binary builds is
> a nightmare. There are just too many details of the build environment to
> get wrong.
>
> If you do try to build from source, I don't know if the gcc packages
> from Paul Smedley are suitable. I understand building perl on OS/2
> requires something called 'EMX', which I presume you have, but those gcc
> builds seem to be using an additional emulation layer on top of that.
> (In Win32 terms, it seems to me Paul is providing the equivalent of
> Cygwin when the equivalent of MinGW would probably be better.)

As I said, it's a fork with updated headers, updated GCC (which Paul has 
updated more) and some stuff removed such as DOS support. Generally it 
is quite compatible with EMX but Perl is complex. In the past I tried 
building with klibc but don't remember the problems. Personally I still 
use 5.8.0 as it was built for my system and works fine including CPAN 
(using EMX) last time I tried a few years back.
EMX is really old now, missing a lot of common headers and using GCC 2.8.1

>
> The rest of this is about trying to fix the installation you've got,
> assuming you can't build one that works better.
>
>>> is there some way you can invoke it as /perl5/bin/perl (or whatever
>>> the proper path is) instead of Q:\PROGRAMS\PERL\BIN\PERL?
>>
>> Q:\PROGRAMS\PERL\BIN\perl.exe is the actual location[1].
>
> I wasn't clear. I realise that the binary is actually in
> q:\programs\perl\bin, however there appear to be some parts of the
> system that want to call that directory /perl5/bin. Presumably if you
> were to type '/perl5/bin/perl' into cmd.exe it would either complain
> about a non-existent binary or about the wrong sort of slashes. Do you
> have some other shell, built against kLibc, which *will* let you invoke
> perl by that path?
>
> (I've no idea if this will make a difference. I am simply mystified as
> to where perl got the path Q:\PROGRAMS\PERL\LIB from, and can only
> assume it is starting with the path to the invoked binary and working
> back from there.)
>
> For reference, what does 'perl -V' give you? Does the @INC list at the
> end have paths under q:\programs\perl or under /perl5?
>
>>> Is this the make used to build that copy of perl?

Any recent make should work but it is important to have the MAKESHELL 
environment variable set correctly, to (pdk)sh.exe IIRC, not cmd.exe. 
Ash.exe might well work as well.
Helps also to have sh.exe in \bin
[...]

Dave

--- Internet Rex 2.31
 * Origin: Unlimited download news at news.astraweb.com (1:261/20.999)