Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 8 Jan 2007 15:35:25 +0300
From:      Eygene Ryabinkin <rea-fbsd@codelabs.ru>
To:        Bob <bob@tamara-b.org>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: discrepancy between WV2 and LIBGSF Header files?
Message-ID:  <20070108123525.GM37482@codelabs.ru>
In-Reply-To: <20070108065458.558b98d2@tania.servebbs.org>
References:  <20070108065458.558b98d2@tania.servebbs.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Bob, good day!

I doubt that this posting should go into the freebsd-hackers, but
nevertheless ;))

> While attempting to compile koffice-1.6.1 I ran into this error:
> 
> In file included from /usr/local/include/wv2/olestream.h:22,
>                  from graphicshandler.cpp:23:
> 
> The offending code is in the file /usr/local/include/wv2/olestorage.h 
> and reads:
> #include <gsf/gsf.h>
> 
> I have libgsf-1.14.1 installed and it installs gsf.h at:
> /usr/local/include/libgsf-1/gsf/gsf.h
> 
> I also have wv2-0.2.3 Installed
>  
> To fix this error, I edited the file /usr/local/include/wv2/olestorage.h
> and changed:
>  #include <gsf/gsf.h> 
> to 
>  #include </usr/local/include/libgsf-1/gsf/gsf.h>

Please, undo these changes and try to build your port with command
'CFLAGS=-I/usr/local/include/libgsf-1 make clean install clean'.
This should clean your build, point the preprocessor to the right
location of the gsf/gsf.h, build your port once again, install it
and clean the build area.

> Can someone either tell me who to report this to, or go ahead and
> report this to the proper maintainer? Perhaps the maintainer of koffice
> should add a patch? 

PRs are welcome: they are made through send-pr utility. The maintainer
for the port can be looked up using the following command:
$ grep MAINTAINER /usr/ports/editors/koffice-kde3/Makefile
MAINTAINER=     kde@FreeBSD.org

You can Cc your problem report to him. And if 'CFLAGS' trick will do
the work, you can mention it in the report.

But previous to sending the PR, look into the PR database: maybe your
bug is already reported, but was not handled yet.

See http://www.freebsd.org/send-pr.html for the long explanation and
links.
-- 
Eygene



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070108123525.GM37482>