The subject line says it all. 'make all' output this before giving up:
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include-
I/usr/include/freetype2 -W -Wall -Wconversion -o out/general-scheme.o
general-scheme.cc
general-scheme.cc:17:39: utf8/wchar.h: No such file or directory
general-sche
On Tuesday 29 March 2005 2:43, David Jedlinsky wrote:
> OpenBSD puts the wchar.h file into a utf8 subdirectory, and uses a
> libutf8.a library. I added a rule to configure to detect this situation,
> and adjust accordingly.
>
Thanks. The 2.5.16 port I maintain now builds without any patches or ot
[EMAIL PROTECTED] writes:
>
> OpenBSD puts the wchar.h file into a utf8 subdirectory, and uses a
> libutf8.a library. I added a rule to configure to detect this situation,
> and adjust accordingly.
>
> Also, I had a problem with the new check for the shared libkpathsea
> library; for some reason
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Anthony Fok wrote on 22.06.2004 05:38:
| On Mon, Jun 21, 2004 at 10:10:32PM +0200, Jan Nieuwenhuizen wrote:
[snip]
|>Done. Will debian users be able to build the package without these
|>files, or will you send a patch? [I assume so, just tried 2.2.3 C
OpenBSD puts the wchar.h file into a utf8 subdirectory, and uses a
libutf8.a library. I added a rule to configure to detect this situation,
and adjust accordingly.
Also, I had a problem with the new check for the shared libkpathsea
library; for some reason the shared_size variable was not being
Pedro Kröger writes:
> it does. it's in testing and sid.
Ah, thanks; apt works better when I spell envince as evince :-)
I'm not impressed, does it have anti-aliasing?
Jan.
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | htt
