I have question (out of ignorance, if anything) -- why on earth would you want to build and compile mod_perl yourself, when you can let CPAN do all the nonsense? I let CPAN do it, and I am wondering if I missed out on something? Needless to say, I know diddly about build and make and -DUSE... you get the picture.
pk/ On Wednesday, April 3, 2002, at 04:36 AM, Mark Setzer wrote: > One more, eh? > > Sorry if this is an already-answered question, but, I'm trying to > compile mod_perl and have hit the following snag: > > env LD_RUN_PATH=/System/Library/Perl/darwin/CORE cc -c -I.. > -I/System/Library/Perl/darwin/CORE -I../os/unix -I../include -DDARWIN > -DMOD_PERL -DUSE_PERL_SSI -pipe -fno-common -DHAS_TELLDIR_PROTOTYPE > -fno-strict-aliasing -I/usr/local/include -DUSE_HSREGEX -DNO_DL_NEEDED > -pipe -fno-common -DHAS_TELLDIR_PROTOTYPE -fno-strict-aliasing > -I/usr/local/include `../apaci` alloc.c > alloc.c: In function `spawn_child_core': > alloc.c:2291: `STDOUT_FILENO' undeclared (first use in this function) > alloc.c:2291: (Each undeclared identifier is reported only once > alloc.c:2291: for each function it appears in.) > alloc.c:2297: `STDIN_FILENO' undeclared (first use in this function) > alloc.c:2303: `STDERR_FILENO' undeclared (first use in this function) > make[4]: *** [alloc.o] Error 1 > make[3]: *** [subdirs] Error 1 > make[2]: *** [build-std] Error 2 > make[1]: *** [build] Error 2 > make: *** [apaci_httpd] Error 2 > > > Anyone seen this before? I'm running OSX 10.1.3, it's mod_perl 1.26 > compiling against apache 1.3.24. Any help appreciated. > > Thanks, > Mark >
