libcdio-help
[Top][All Lists]
Advanced

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

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


From: Rocky Bernstein
Subject: Re: [Libcdio-help] unknown type name 'ULONG'
Date: Fri, 10 Feb 2012 11:33:43 -0500


On Thu, Feb 9, 2012 at 12:58 PM, Kyle Schwarz <address@hidden> wrote:
Hello,

I'm trying to compile libcdio 0.83 with MinGW-w64, but I'm running into this compile error:
make[3]: Entering directory `/home/kyle/software/ffmpeg/packages/libcdio/source/libcdio-0.83/lib/driver'
/bin/bash ../../libtool  --tag=CC   --mode=compile i686-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib/driver -I../../include -I../../include/ -I/home/kyle/software/ffmpeg/packages/libiconv/libiconv-1.14-win32/include  -g -O2 -Wall -Wchar-subscripts -Wmissing-prototypes -Wmissing-declarations -Wunused -Wpointer-arith -Wwrite-strings -Wnested-externs -Wno-sign-compare -MT win32_ioctl.lo -MD -MP -MF .deps/win32_ioctl.Tpo -c -o win32_ioctl.lo `test -f 'MSWindows/win32_ioctl.c' || echo './'`MSWindows/win32_ioctl.c
libtool: compile:  i686-w64-mingw32-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../lib/driver -I../../include -I../../include/ -I/home/kyle/software/ffmpeg/packages/libiconv/libiconv-1.14-win32/include -g -O2 -Wall -Wchar-subscripts -Wmissing-prototypes -Wmissing-declarations -Wunused -Wpointer-arith -Wwrite-strings -Wnested-externs -Wno-sign-compare -MT win32_ioctl.lo -MD -MP -MF .deps/win32_ioctl.Tpo -c MSWindows/win32_ioctl.c -o win32_ioctl.o
In file included from /home/kyle/software/mingw-w64/4.6.2/mingw-w64-i686/lib/gcc/i686-w64-mingw32/4.6.2/../../../../i686-w64-mingw32/include/ntddcdrm.h:26:0,
                from MSWindows/win32_ioctl.c:33:
/home/kyle/software/mingw-w64/4.6.2/mingw-w64-i686/lib/gcc/i686-w64-mingw32/4.6.2/../../../../i686-w64-mingw32/include/ntddstor.h:224:3: error: unknown type name 'ULONG'

The full error is much longer, but I don't think it will fit in the email.

The full error can be viewed here: http://pastebin.com/r44vmmW1

I'm not sure if the problem is on MinGW-w64's end or libcdio's.

It is probably libcdio 0.83's problem.
 
Recently there has been some terrific work done specifically to address compilation on MSWindows  -- specifically for both MinGW and native visual C++. This is currently on git in the pbatard branch of the git repository.

So my recommendation is to try that.

 

Best regards,
 Kyle Schwarz

_______________________________________________
Libcdio-help mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/libcdio-help


reply via email to

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