From owner-freebsd-hackers Tue Mar 31 10:07:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07011 for freebsd-hackers-outgoing; Tue, 31 Mar 1998 10:07:14 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gratia.it.hq.nasa.gov (gratia.it.hq.nasa.gov [131.182.119.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07005 for ; Tue, 31 Mar 1998 10:07:06 -0800 (PST) (envelope-from cshenton@gratia.it.hq.nasa.gov) Received: from wirehead.it.hq.nasa.gov (WireHead.it.hq.nasa.gov [131.182.119.88]) by gratia.it.hq.nasa.gov (8.7.5/8.7.3) with ESMTP id MAA07419; Tue, 31 Mar 1998 12:59:54 -0500 (EST) Received: (from cshenton@localhost) by wirehead.it.hq.nasa.gov (8.8.8/8.8.8) id NAA03688; Tue, 31 Mar 1998 13:06:45 -0500 (EST) To: Tom Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 2.2.6-STABLE perl5 port broken (or is it me)? References: From: Chris Shenton Date: 31 Mar 1998 13:06:45 -0500 In-Reply-To: Tom's message of Tue, 31 Mar 1998 09:04:52 -0800 (PST) Message-ID: Lines: 32 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 31 Mar 1998, Chris Shenton wrote: > > > same place: an undefined type "recno_t". I don't find this defined > > anywhere in the Perl5.004.04 sources. Tom writes: > Of course. It is defined in /usr/include/db.h Then something's busted in the port cuz the first error occurs in DB_File.xs which has #include "EXTERN.h" #include "perl.h" #include "XSUB.h" #include as the first non-comments in the file, and so does the generated .c file. Inserting the line from the /usr/include/db.h file typedef u_int32_t recno_t; into the DB_File.xs causes the generated .c file to compile properly so something's broken with the CC processing of the .h typedef. But if it's really CC brain-damage, then I'd expect lots of other typedefs in .h files to fail spectacularly. This manual edit gets me through my roadblock but I'm very concerned about other damage if there's really a CC or .h problem. Any hints? Anyone else have this problem? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message