At 6:58 PM +0200 10/25/07, [EMAIL PROTECTED] wrote: >On Thu, 25 Oct 2007 05:24:16 +0200, Craig A. Berry <[EMAIL PROTECTED]> wrote: > >>At 12:25 AM +0200 10/25/07, [EMAIL PROTECTED] wrote: >>>On Wed, 24 Oct 2007 23:26:32 +0200, <[EMAIL PROTECTED]> wrote: >>>> >>>>Just for laughs (I am not serious to make this work): >>> >>>Well, I couldn't stop. To get around this rather stupid problem I changed >>>configure.com: >>> >>>A400> diff configure.com,;1 >>>************ >>>File TMP:[AI26.perl-current]configure.com;5 >>>6606 $ 'Perl_CC' 'ccflags' munchconfig.c >>>6607 $ IF Needs_Opt >>>****** >>>File TMP:[AI26.perl-current]configure.com;1 >>>6606 $ 'Perl_CC' munchconfig.c >>>6607 $ IF Needs_Opt >>>************ >> >>Getting rid of your compiler flags means all bets are off. >> > >It's the other way round. configure.com as shipped discards >all flags. I added them and then munchconfig compiles.
I've added your change: http://public.activestate.com/cgi-bin/perlbrowse/p/32199 The best way to chase the other problems you reported would be to configure a debug build like so: $ @configure -"Dusevmsdebug" -"des" and then build with $ MMK/MACRO=__DEBUG__=1 You'll get listing files which would tell you a lot about what the compiler is or is not seeing. Upgrading the compiler would probably be a lot less work. And yes, I understand you've pursued this as far as you want to, which is fine. -- ________________________________________ Craig A. Berry mailto:[EMAIL PROTECTED] "... getting out of a sonnet is much more difficult than getting in." Brad Leithauser
