On Jan 14 12:32, Greg Chicares wrote:
> On 2010-01-14 10:15Z, Schwerzmann Stephan wrote:
> >
> > /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../include/w32api/winsock.h:4
> > 79: error: declaration of C function 'int select(int, _types_fd_set*,
> > _types_fd_set*, _types_fd_set*, const timeval*)'
On 2010-01-14 10:15Z, Schwerzmann Stephan wrote:
>
> /usr/lib/gcc/i686-pc-cygwin/4.3.4/../../../../include/w32api/winsock.h:4
> 79: error: declaration of C function 'int select(int, _types_fd_set*,
> _types_fd_set*, _types_fd_set*, const timeval*)' conflicts with
> /usr/include/sys/select.h:3
Without "-lfestival", I have some errors.. because in my code, I use some
functiond defined in the libfestival.a
Ken Jackson-3 wrote:
>
>
> Wait. The switch "-lfestival" tells the linker to use archive
> libfestival.a, which presumably has stubs for festival.dll.
>
> But you are creating fes
Stefano Facchetti writes:
> g++ -shared -o festival.dll festivaldll.o -L. -lfestival -lestools
> -lestbase -leststring -ltermcap -lwinmm -I ../src/include/
> -I ../../speech_tools/include/
> -I ./ -mno-cygwin -I./mingw/include -L./mingw/lib/
Wait. The switch "-lfestival" tells the linker
I build my custom dll in this two step:
g++ -c festivalDll.cc -L. -lfestival -lestools -lestbase -leststring
-ltermca
p -lwinmm -I ../src/include/ -I ../../speech_tools/include/ -I ./ -o
festivalDl
l.o -mno-cygwin -I./mingw/include -L./mingw/lib/
g++ -shared -o festival.dll festivaldll.o -L. -l
Stefano Facchetti wrote:
> When I compile my cc files under cygwin with this command line:
> g++ -c festivalDll.cc -o festivalDll.o -L. -lfestival -lestools -lestbase
> -leststring -ltermcap -lwinmm -I../src/include/
> -I../../speech_tools/include/ -I ./ -mno-cygwin -I./mingw/include
> -L./mingw/l
You really should not edit unistd.h or any other system header, ever.
That's a very bad practice to get into. If "#undef pipe" in
dbus-binding-tool-glib.c works, then go with that, but even that's a
horrible hack. The best way would be to find out why this macro that
seems to be relevant only to
Scott Peterson wrote:
> On that advice, I now get a new error:
>
> /home/Scott/downloads/dbus-glib-0.73/dbus/dbus-binding-tool-glib.c:800:
> undefine
> d reference to `_g_file_open_tmp_utf8'
>
> This is nearly identical to the error I got when commenting out line
> 108 of unistd.h:
>
> /home/S
On that advice, I now get a new error:
/home/Scott/downloads/dbus-glib-0.73/dbus/dbus-binding-tool-glib.c:800: undefine
d reference to `_g_file_open_tmp_utf8'
This is nearly identical to the error I got when commenting out line
108 of unistd.h:
/home/Scott/downloads/dbus-glib-0.73/dbus/dbus-bin
On Thu, 31 May 2007, Scott Peterson wrote:
> Sorry about the large email: didn't realize how big it was when I cut
> and pasted.
> Line 108 is indeed:
>
> int _EXFUN(pipe, (int __fildes[2] ));
>
> I've greped around for "define pipe" and the only results I could find
> are /usr/include/glib-1.
Sorry about the large email: didn't realize how big it was when I cut
and pasted.
Line 108 is indeed:
int _EXFUN(pipe, (int __fildes[2] ));
I've greped around for "define pipe" and the only results I could find
are /usr/include/glib-1.2/glib.h and
/usr/include/glib-2.0/glib/gwin32.h. Both fi
Greg Chicares wrote:
On 2007-05-30 00:12Z, Scott Peterson wrote:
Here's the content of the intermediate file dbus-binding-tool-glib.i:
[major snip]
On 2007-05-29 02:07Z, you had written:
In file included from /usr/include/unistd.h:4,
from dbus-binding-tool-glib.c:39:
/usr/inc
On 2007-05-30 00:12Z, Scott Peterson wrote:
>
> Here's the content of the intermediate file dbus-binding-tool-glib.i:
[major snip]
On 2007-05-29 02:07Z, you had written:
>
> In file included from /usr/include/unistd.h:4,
> from dbus-binding-tool-glib.c:39:
> /usr/include/sys/unis
Scott Peterson wrote:
> Here's the content of the intermediate file dbus-binding-tool-glib.i:
Did you really have to send a 350 KB message to thousands of people?
Some people consider that a little wasteful when exactly one line of all
of that was relevant. If you're going to do that at least s
Scott Peterson wrote:
> Eric, when I try make CC="gcc -E" I get this error in the output:
> .libs/dbus-glib.o: file not recognized: File format not recognized
You just created an .o file consisting of the output of the
preprocessor. That's obviously not going to work in the context of make
where
Eric, when I try make CC="gcc -E" I get this error in the output:
.libs/dbus-glib.o: file not recognized: File format not recognized
I'm building dbus-glib from source and I get this error when I make:
In file included from /usr/include/unistd.h:4,
from dbus-binding-tool-glib.c:
Scott Peterson wrote:
> I'm building dbus-glib from source and I get this error when I make:
>
> In file included from /usr/include/unistd.h:4,
> from dbus-binding-tool-glib.c:39:
> /usr/include/sys/unistd.h:108: error: parse error before numeric constant
>
> Ideas?
There's not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Scott Peterson on 5/28/2007 8:07 PM:
> I'm building dbus-glib from source and I get this error when I make:
>
> In file included from /usr/include/unistd.h:4,
> from dbus-binding-tool-glib.c:39:
> /usr/include/sys/unistd.h
I had not trouble building putty-0.58-cygterm-20060525.tar.gz
you do need to do:
install -s path-to.../cthelper/cthelper.exe /usr/local/bin
install -s path-to /utty.exe /usr/local/bin
for cygwin based system.
See if you /bin/ld program is there. You'll need it if you want to
Dave Korn wrote:
On 07 December 2006 16:00, Keith Christian wrote:
Baffling. Any ideas?
Different binutils versions? make versions? Run "cygcheck -s -v -r" on
each machine and then diff the two?
Yesterday I downloaded the 0.59 binary zipfile, and it WORKS on the machine
where the 0.5
On 07 December 2006 16:00, Keith Christian wrote:
>
> Baffling. Any ideas?
Different binutils versions? make versions? Run "cygcheck -s -v -r" on
each machine and then diff the two?
cheers,
DaveK
--
Can't think of a witty .sigline today
--
Unsubscribe info: http:/
21 matches
Mail list logo
