Your only hope is to re-re-re-re-re-recompile

Downloaded the source, and eventually managed to satisfy all of configure's requirements. Compilation looked good for a while .... until the non-existent (on windows) netinet/in.h could not be found.

UPDATE: Including winsock.h (or was it winsock2.h ?) instead of netinet/in.h in whichever header it was that was throwing the error, enabled the build to succeed - but the same undefined references srill crop up and I'm still undecided as to what needs doing. When I can be bothered, I'll probably contact the developers for some advice.

Obviously configure isn't doing all it ought. I might try an earlier version of gnome-vfs later on and, if that doesn't work, just submit a bug report and forget about the whole buggy mess until next time.

Cheers,
Rob

In reply to Re^2: [Win32] Building Gnome2::VFS by syphilis
in thread [Win32] Building Gnome2::VFS by syphilis

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.