[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Libcdio-help] unknown type name 'ULONG'

From: Pete Batard
Subject: Re: [Libcdio-help] unknown type name 'ULONG'
Date: Mon, 13 Feb 2012 12:45:43 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1

Hi Kyle,

On 2012.02.11 18:58, Kyle Schwarz wrote:
-I../../include/ -D_FILE_OFFSET_BITS=64 -D_OFF_T_DEFINED -D_OFF_T_
-D_off_t=off64_t -Doff_t=off64_t
error: unknown type name '_off64_t'
error: unknown type name 'off64_t'

That's weird.
Can you tell the version of MinGW-w64 you are using and where you downloaded it from?

I did test with with MinGW-w64 and the Large File Support workaround, that is added with the defines above, and that relies on redefining off_t to off64_t as is the case on other platforms, should not prevent the off64_t to be properly defined from stdio.h

In the MinGW-w64 I use (from TDM-GCC), stdio.h defines the offeset types as follows:

#ifndef _OFF_T_DEFINED
#define _OFF_T_DEFINED
#ifndef _OFF_T_
#define _OFF_T_
  typedef long _off_t;
#if !defined(NO_OLDNAMES) || defined(_POSIX)
  typedef long off_t;

#ifndef _OFF64_T_DEFINED
#define _OFF64_T_DEFINED
  __MINGW_EXTENSION typedef long long _off64_t;
#if !defined(NO_OLDNAMES) || defined(_POSIX)
  __MINGW_EXTENSION typedef long long off64_t;

Thus, none of what we do should have an impact on off64_t and _off64_t being accessible. But apparently, that is not the case on your platform.

Can you please have a look at your stdio.h and let me know how off64_t is defined there (if defined at all)?



reply via email to

[Prev in Thread] Current Thread [Next in Thread]