From owner-freebsd-stable@FreeBSD.ORG Thu May 12 06:59:49 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 70BC5106564A for ; Thu, 12 May 2011 06:59:49 +0000 (UTC) (envelope-from jdc@koitsu.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id 56BA08FC0A for ; Thu, 12 May 2011 06:59:49 +0000 (UTC) Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta03.emeryville.ca.mail.comcast.net with comcast id iWyH1g0061Y3wxoA3WzoHi; Thu, 12 May 2011 06:59:48 +0000 Received: from koitsu.dyndns.org ([67.180.84.87]) by omta15.emeryville.ca.mail.comcast.net with comcast id iWzm1g0021t3BNj8bWzm8r; Thu, 12 May 2011 06:59:47 +0000 Received: by icarus.home.lan (Postfix, from userid 1000) id 03218102C36; Wed, 11 May 2011 23:59:46 -0700 (PDT) Date: Wed, 11 May 2011 23:59:45 -0700 From: Jeremy Chadwick To: joerg_surmann Message-ID: <20110512065945.GA55199@icarus.home.lan> References: <4DCB7962.6090706@snafu.de> <20110512061312.GA54574@icarus.home.lan> <4DCB81EF.2080104@snafu.de> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="FCuugMFkClbJLl1L" Content-Disposition: inline In-Reply-To: <4DCB81EF.2080104@snafu.de> User-Agent: Mutt/1.5.21 (2010-09-15) X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-stable@freebsd.org Subject: Re: can't update libzip-0.9.3 to libzip-0.10 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 12 May 2011 06:59:49 -0000 --FCuugMFkClbJLl1L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, May 12, 2011 at 08:45:03AM +0200, joerg_surmann wrote: > Hey Jeremy, > > Ok i'll put the files in a attachment > on the end from this email. [...snip...] [attachment: zipconf.h] Oh dear. I'm not sure what to make of this: > #ifndef _HAD_ZIPCONF_H > #define _HAD_ZIPCONF_H > > /* > zipconf.h -- platform specific include file > > This file was generated automatically by ./make_zipconf.sh > based on ../config.h. > */ > > #define LIBZIP_VERSION "0.10" > #define LIBZIP_VERSION_MAJOR 0 > #define LIBZIP_VERSION_MINOR 10 > #define LIBZIP_VERSION_MICRO 0 > > #include > > typedef signed char int8_t; > #define ZIP_INU8_MAX SCHAR_MAX > > typedef unsigned char uint8_t; > #define ZIP_?INU8_MAX ?CHAR_MAX > > typedef shor? int16_t; > #define ZIP_INU16_MIN ?CHAR_MIN > #define ZIP_INU16_MAX ?CHAR_MAX > > typedef unsigned shor? uint16_t; > #define ZIP_?INU16_MAX ?CHAR_MAX > > typedef in? int32_t; > #define ZIP_INU32_MIN ?CHAR_MIN > #define ZIP_INU32_MAX ?CHAR_MAX > > typedef unsigned in? uint32_t; > #define ZIP_?INU32_MAX ?CHAR_MAX > > typedef long int64_t; > #define ZIP_INU64_MIN SLONG_MIN > #define ZIP_INU64_MAX SLONG_MAX > > typedef unsigned long uint64_t; > #define ZIP_?INU64_MAX ?LONG_MAX > > > #endif /* zipconf.h */ All of these values have a "?" injected in them, at seemingly randomly places. This is the problem, and why the C compiler is throwing errors. I don't know how or why this is happening. There could be many things going on that might explain it. Worst case would be odd/awkward hardware failure (bad RAM would show something like this), corrupt filesystem, a disk going bad silently ("bit rot"), etc.. My initial guess -- because this port uses a GNU autoconf script -- is that it's obtaining the types for things incorrectly. Are you using any sort of LC_CTYPE or LANG setting in your dotfiles that gets propagated to the root environment (during su, sudo, etc.)? I see that you're in .de which is why I ask. I've attached a zipconf.h file from my system. You can compare the differences; it should be obvious. My system does not have "?" characters injected into the typedefs, but more importantly (and this is indeed important!), the types it detects/uses are completely different. I'm not sure what's going on with your system, but it almost implies that you have a separate set of include files that are "trumping" or "overriding" the FreeBSD base system defaults. -- | Jeremy Chadwick jdc@parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP 4BD6C0CB | --FCuugMFkClbJLl1L--