This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Build problems - unistd.h


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/Scott/downloads/dbus-glib-0.73/dbus/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?

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 MinGW/native win32 builds is getting pulled
in for a Cygwin build and report it upstream, otherwise it'll never get
fixed.

The undefined reference looks like a link error, a completely unrelated
and separate failure.  You aren't doing anyone any good by deleting all
of the surrounding context of these errors.  If we had the link command
that produced the error we might be able to spot a problem, like
incorrect ordering of -l arguments or something.  But without that, all
that can be said is "find where that symbol is defined and then find why
the linker can't find it."

Brian

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]