Text 1985, 103 rader
Skriven 2011-12-06 08:32:07 av Ben Morrow
Ärende: Re: Problem configuring OS/2 for installing CPAN packages
=================================================================
sv3-cmowz7F/GrVnm/+HwkHJBk5gPkhFojHUFO8dKhS2kFRr75x4yfNouxtEvcBYs8Wk8md1pv18UPJmJ5i!/uu7DdHdG0niDWsLq3Cz3v+T7qAHzFX0xiPThn1qdFkCQhA0k6MhIKfoqwcw7KEAcVfBfZ5jzKqW!8w==

properly
comp.os.os2.ecomstation:1156 comp.os.os2.misc:3745
From: Ben Morrow <ben@morrow.me.uk>


Quoth Shmuel (Seymour J.) Metz <spamtrap@library.lspace.org.invalid>:
> In <OtOdneN9eYaJ6kDTnZ2dnUVZ8kOdnZ2d@bt.com>, on 12/05/2011
>    at 07:59 PM, Ben Morrow <ben@morrow.me.uk> said:
> 
> >Weird. Did you put gcc in your path, or did you edit Config_heavy.pl?
> 
> The latter, to get the gcc in Paul Smedley's build environment.

OK. It *may* be worth putting the entry in Config_heavy.pl back to just
'gcc' and then running the build with U:\usr\bin first in your PATH,
since that seems to be the way Paul did things.

> >If you edited Config_heavy, which slashes did you use?
> 
> \

OK. That ought to be safer than the other way, in this case.

>  cc='U:\usr\bin\gcc.exe'
>  ccname='gcc'
>  cpprun='gcc -E'
>  cppstdin='gcc -E'
>  gccversion='3.3.5 (Bird Build 2007-06-10 14:30)'
>  ld='gcc'
>  libpth='/usr/lib /usr/lib/gcc-lib/i386-pc-os2-emx/3.3.5 /extras/lib
> /dev/qt/trunk/lib /openldap/lib /cups/lib'

I presume you have a mapping / -> U:\ set up for kLibc?

>  libspath=' /usr/lib /usr/lib/gcc-lib/i386-pc-os2-emx/3.3.5
> /extras/lib /dev/qt/trunk/lib /openldap/lib /cups/lib'
> 
> config.pm has
> 
>     cc => 'U:\usr\bin\gcc.exe',
>     libpth => 'U:/usr/lib U:/usr/lib/gcc-lib/i386-pc-os2-emx/3.3.5
> u:/extras/lib u:/dev/qt/trunk/lib u:/openldap/lib u:/cups/lib',

I don't like the fact that this is different from the _heavy entry, even
if they do end up mapping to the same directory. I also don't know
whether it matters which slashes you use here, but I would *expect* that
true native paths (with backslashes) are always the safest option.

> >Does OS/2 allow you to run a command (from the cmd.exe prompt) 
> >using forward slashes in the path,
> 
> No.
> 
> From your question should I infer that i Need / rather than \ in the
> gcc path?

No, since this is intended to be passed to cmd.exe (in the end)
backslashes are correct.

My current theory (have you worked out yet that I'm mostly just
guessing?) is that, for some as-yet-unknown reason, gcc is invoking
as.exe with forward rather than backslashes in its name, and cmd is
complaining because it doesn't like that. So, things to check:

    - are there any entries in your PATH with forward slashes in?
    - do you have GCC_EXEC_PREFIX set in the environment?

The next thing I would try is setting 

    GCC_EXEC_PREFIX=U:\usr\i386-pc-os2-emx\bin\

(with backslashes, and with a trailing \) in the environment. That ought
to make gcc look exactly there and nowhere else for as.exe. If that
fails (and I don't know which versions of gcc support that env var) then
I would try putting

    cc='u:\usr\bin\gcc.exe -BU:\usr\i386-pc-os2-emx\bin\'

in Config_heavy.pl, to see if that works instead.

At some point you will probably need to take whichever set of changes
worked and apply them to the 'ld' entry as well.

> >Can you run gcc at all?
> 
> I don't know; I haven't tried to configure the one that comes with my
> system.

I don't mean the one that comes with your system, I mean the one perl's
trying to use. If you run

    U:\usr\bin\gcc.exe -o hello.exe hello.c

for some suitable hello.c, do you get a working executable, or does it
yell about being unable to find as.exe?

Ben


--- Internet Rex 2.31
 * Origin: The gateway at Omicron Theta (1:261/20.999)