error building skipstone

Nathan Kinkade nkinkade at
Sat Mar 29 07:45:19 PST 2003

On Fri, Mar 28, 2003 at 07:16:27PM -0500, David Banning wrote:
> I got this error building skipstone. I wonder if anyone knows 
> what I can do with it.
> ...spr -I/usr/X11R6/include/mozilla/uconv -I/usr/X11R6/include/mozilla/webbrowserpersist   -c -o mozilla.o mozilla.cpp
> In file included from /usr/X11R6/include/mozilla/string/nsSharableString.h:35,
>                  from /usr/X11R6/include/mozilla/string/nsPromiseFlatString.h:28,
>                  from /usr/X11R6/include/mozilla/string/nsString2.h:70,
>                  from /usr/X11R6/include/mozilla/string/nsString.h:54,
>                  from /usr/X11R6/include/mozilla/content/nsIDocument.h:44,
>                  from mozilla.cpp:19:
> /usr/X11R6/include/mozilla/string/nsBufferHandleUtils.h:36: `#include' expects "FILENAME" or <FILENAME>
> In file included from /usr/X11R6/include/mozilla/xpcom/nsCRT.h:45,
>                  from /usr/X11R6/include/mozilla/xpcom/nsFileSpec.h:150,
>                  from mozilla.cpp:20:
> /usr/X11R6/include/mozilla/xpcom/nsCppSharedAllocator.h:6: `#include' expects "FILENAME" or <FILENAME>
> gmake[1]: *** [mozilla.o] Error 1
> gmake[1]: Leaving directory `/usr/ports/www/skipstone/work/skipstone-0.8.3/src'
> gmake: *** [all] Error 2
> *** Error code 2
> Stop in /usr/ports/www/skipstone.

I had this same problem and got around it by commenting out the
offending lines.  I have no clue what the ramifications of doing such
might be, but the build worked and Skipstone seemed to work fine during
a few test runs.  The offending lines are something like:

#include NEW_H

I simply turned that into:

// #include NEW_H

You will have to do this on both files:

Then after this the build will fail again due to some undeclared
function reference.  Again, probably unwisely, I just commented out the
reference to the offending function and the build completed
successfully.  My main goal was just to get Skipstone up to some degree
so that I could see what it looked like and how it rendered various
pages.  It seemed OK, but I wasn't all that impressed.  It's memory
usage isn't that much less than that of Phoenix.

Probaby the port maintainer should be notified about these problems.

Good luck,

GPG Public Key ID: 0x4250A04C
gpg --keyserver --recv-keys 4250A04C
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-questions mailing list