tried to buid SPO from sourceforge's CVS. Relevant output: 07/09 16:16 ot@wasabi /usr/local/perl/modules/spo% perl Makefile.PL Checking if your kit is complete... Looks good Note (probably harmless): No library found for -lD:\osp\lib\Release\osp152.lib Writing Makefile for SGML::Parser::OpenSP 07/09 16:18 ot@wasabi /usr/local/perl/modules/spo% make cl -TP -EHsc -ID:/osp/ -c -D_REENTRANT -D_GNU_SOURCE -DTHREADS_HAVE_PIDS -DDEBIAN -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -O2 -DVERSION=\"0.02\" -DXS_VERSION=\"0.02\" -fPIC "-I/usr/lib/perl/5.8/CORE" -DSP_MULTI_BYTE=1 OpenSP.c /bin/sh: cl: command not found make: *** [OpenSP.o] Error 127 cl as in the windows C compiler? Just a guess, - "cl" is not an easy thing to google - but that and the lD with backslashes seem to point in the same direction. So... Is SPO win32 only on purpose, is my makemaker (or its user) stupid, or...? I can probably hack the Makefile, though, just wanted to know if it's a problem on my side or not. -- olivierReceived on Tuesday, 7 September 2004 07:35:46 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:54:46 UTC