On Mon, Mar 03, 2003 at 07:14:59PM +1100, Sisyphus wrote: > Hi, > Par sounds good - but I can't build version 0.64 on either msvc-built perl > or > mingw32-built perl (running on Windows2000). > > Here's the error dmake produces (mingw32): > main.c: In function `main': > main.c:74: `Perl_atfork_lock' undeclared (first use in this function) > main.c:74: (Each undeclared identifier is reported only once > main.c:74: for each function it appears in.) > main.c:75: `Perl_atfork_unlock' undeclared (first use in this function) > dmake.exe: Error code 1, while making 'main.o' > dmake.exe: Error code 255, while making 'subdirs'
Indeed? What version of perl is this? I built against 5.8 without problems. Can I have your perl -V? > Here's the error nmake produces(msvc++6.0): > main.c > main.c(74) : error C2065: 'Perl_atfork_lock' : undeclared identifier > main.c(75) : error C2065: 'Perl_atfork_unlock' : undeclared identifier > NMAKE : fatal error U1077: 'cl' : return code '0x2' > Stop. > NMAKE : fatal error U1077: 'cd' : return code '0x2' > Stop. > > I can't post to Usenet - which is really pissing me off - my ISP's news > server is crap, and posting via Google generally no longer works for me as > of about a fortnight ago. > > Hence the email. Looks like if mine (and ActiveState's) perl was not built > with threads support, this problem would not arise. Hopefully there's a > simple workaround. Try commenting out line 74-76 and see if it builds. Thanks, /Autrijus/
pgp00000.pgp
Description: PGP signature
