in reply to Re^4: inline c
in thread inline c

I installed a VB6 on a different computer

I assume you mean "VC6", not "VB6".
There should be no trouble with Inline::C on ActivePerl, using MSVC++ 6.0.
Try running your scripts without Komodo (to begin with, at least) - that will make troubleshooting easier.
Also, try installing Inline::C from CPAN source. (I'm assuming you installed Inline::C using ppm.) Just download the source from http://search.cpan.org/~ingy/Inline-0.44/, extract the file to some location, 'cd' to that location and run 'perl Makefile.PL' followed by 'nmake test'. If there are no errors run 'nmake install'. If there are errors, tell us what they are. (Copy and paste the output inside <code> tags.)

Cheers,
Rob

Replies are listed 'Best First'.
Re^6: inline c
by panaman (Acolyte) on Apr 23, 2007 at 19:27 UTC

    Hi Rob et. al.

    Actually it was Visual Studio 6 which is the C compiler. When I run the the scripts from the command line I get the same errors that I get inside Komodo. I did install the Inline::C with ppm and it was 0.44 and seemed to go fine but I will download it and install it manually just to be sure. I will write to you with the <code> tags.

    Angel

Re^6: inline c
by panaman (Acolyte) on Apr 23, 2007 at 20:15 UTC

    Hi,

    I did the download and the manual perl Makefile.pl that
    seemed fine, thenI did the nmake test and was mostly errors.
    To many to list here so I placed the text file at:

    http://volcanbaru.com/OSOP/monks/
    the txt file is the output of the perl Makefile.pl
    and the nmake test.
    I have also zipped the entire folder in case it helps.
    I read that errors messages and the were mostly quite cryptic.
    What should I try next?

    Angel

    Hey!! I can be trained!!

      (quoting from the build log you linked to)

      link -out:blib\arch\auto\xsmode\xsmode.dll -dll -nologo -nodef +aultlib -d ebug -opt:ref,icf -libpath:"C:\Perl\lib\CORE" -machine:x86 xsmode.ob +j C:\Per l\lib\CORE\perl58.lib oldnames.lib kernel32.lib user32.lib gdi32.lib w +inspool.li b comdlg32.lib advapi32.lib shell32.lib ole32.lib oleaut32.lib netap +i32.lib uu id.lib ws2_32.lib mpr.lib winmm.lib version.lib odbc32.lib odbccp32.l +ib msvcrt. lib -def:xsmode.def link: invalid option -- o Try `link --help' for more information. NMAKE : fatal error U1077: 'link' : return code '0x1'

      I can't help getting the impression that it's not the linker belonging to the compiler suite that's being called here, but rather some Windows port of the Unix command 'link'  - at least, if I type the respective command on my Debian box, I get a rather similarly looking output:

      $ link -out:... link: invalid option -- o Try `link --help' for more information.

      I wouldn't be too surprised, if you got

      $ link --help Usage: link FILE1 FILE2 or: link OPTION Call the link function to create a link named FILE2 to an existing FIL +E1. --help display this help and exit --version output version information and exit Report bugs to <bug-coreutils@gnu.org>.

      if you typed link --help  :)

      In that case, make sure this command is no longer found along the search path, while trying to build stuff...   Just a thought.

        By gosh by golly

        You are right on. I think that it was seeing the cygwin "link"
        I removed that from the path and now it sees the correct linker
        but it still fails with this error.

        C:\Program Files\Microsoft Visual Studio\VC98\lib\msvcrt.lib : fatal error LNK1113: invalid machine type
        NMAKE : fatal error U1077: 'link' : return code '0x459'

        I have posted the nmake test output it since it is so long at:
        http://volcanbaru.com/OSOP/monks/Monks2.txt
        I have also posted the belarc for the computer it was run on
        2.00 gigahertz AMD Mobile Sempron
        I would have thought that it was x86 but now I am not so sure
        I am going to reinstall everything on yet another computer
        and try it.

        I am open to any and all suggestions.

        angel