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
/dbus-binding-tool-glib.c:799: undefine
d reference to `_g_file_open_tmp_utf8'
Note that the errors differ only in their line numbers. Whatever does it mean?
On 5/31/07, Igor Peshansky <[EMAIL PROTECTED]> wrote:
On Thu, 31 May 2007, Scott Peterson wrote:
> Sorry about the large email:
processor is getting that method? C really
isn't my thing so when I have problems like this with prerequisite
packages, I'm really at a loss. Thanks everyone for lending me a hand
with this!
Greg Chicares wrote:
On 2007-05-30 00:12Z, Scott Peterson wrote:
Here's the content of
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:
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?
--
Scott.
--
Unsubscribe info: http://cygw
5 matches
Mail list logo
