From owner-freebsd-questions Fri May 17 17:10:12 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id 0E6E237B400 for ; Fri, 17 May 2002 17:10:07 -0700 (PDT) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.12.1/8.12.1) with ESMTP id g4I0A19V159944; Fri, 17 May 2002 20:10:01 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <200205171038.DAA52246@uplift.sunquest.com> References: <200205171038.DAA52246@uplift.sunquest.com> Date: Fri, 17 May 2002 20:10:00 -0400 To: "Terry R. Friedrichsen" , questions@FreeBSD.ORG From: Garance A Drosihn Subject: Re: printf(3) problem? Content-Type: text/plain; charset="us-ascii" ; format="flowed" X-Scanned-By: MIMEDefang 2.3 (www dot roaringpenguin dot com slash mimedefang) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 3:38 AM -0700 5/17/02, Terry R. Friedrichsen wrote: >I've never tried this before, so I may simply be doing it >wrong. I'm using FreeBSD 4.5-RELEASE, and the following >program appears to print the wrong thing. Try compiling your program with -Wall, eg: cc -Wall -o test test.c >I'm somewhat buoyed by the fact that Tru64 and Linux >agree with me. These operating systems may have different fundamental types for off_t. Or, you may have the same type-mismatch, but the way they pass parameters around might mean that you still get the output you are expecting, even though the parameters are not right. -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message