sam th               
        [EMAIL PROTECTED]
        http://www.abisource.com/~sam/
        GnuPG Key:  
        http://www.abisource.com/~sam/key



I tried sending this message to the abiword-dev mailing list, but it
bounced even though I am subscribed to that list.  Can you send this
along?   

Thanks,

Alec


------- Forwarded Message

To: [EMAIL PROTECTED]
Subject: freebsd build problem
Date: Mon, 13 Nov 2000 20:10:48 -0800
From: "Alec Wolman" <[EMAIL PROTECTED]>
MIME-Version: 1.0

I am attempting to build the cvs version AbiWord on FreeBSD.
The build is failing for me in the src/af/ev directory,
when compiling the ev_UnixKeyboard.cpp file.  Here is the 
error message:

ev_UnixKeyboard.cpp:
In file included from /usr/X11R6/include/gtk12/gdk/gdktypes.h:33,
                 from /usr/X11R6/include/gtk12/gdk/gdk.h:31,
                 from ev_UnixKeyboard.cpp:21:
/usr/local/include/glib12/glib.h:1301: warning: ANSI C does not allow macro with 
variable arguments
/usr/local/include/glib12/glib.h:1304: warning: ANSI C does not allow macro with 
variable arguments
/usr/local/include/glib12/glib.h:1307: warning: ANSI C does not allow macro with 
variable arguments
In file included from ev_UnixKeyboard.cpp:33:
/local/wolman/scratch/abiword/build/abi/src/af/util/xp/ut_mbtowc.h:41: iconv.h:
No such file or directory
In file included from ev_UnixKeyboard.cpp:33:
/local/wolman/scratch/abiword/build/abi/src/af/util/xp/ut_mbtowc.h:48: syntax error 
before `;'
gmake[4]: *** 
[/local/wolman/scratch/abiword/build/abi/src/FreeBSD_4.1-RELEASE_i386_OBJ/obj/ev_UnixKeyboard.o]
 Error 1
gmake[4]: Leaving directory `/local/wolman/scratch/abiword/build/abi/src/af/ev/unix'
gmake[3]: *** [build] Error 2
gmake[3]: Leaving directory `/local/wolman/scratch/abiword/build/abi/src/af/ev'
gmake[2]: *** [build] Error 2
gmake[2]: Leaving directory `/local/wolman/scratch/abiword/build/abi/src/af'
gmake[1]: *** [build] Error 2
gmake[1]: Leaving directory `/local/wolman/scratch/abiword/build/abi/src'
gmake: *** [compile] Error 2


The problem is that none of the complex Makefile magic ensures that
libiconv/include directory is in the compiler include path.  I could
provide a patch to fix this problem, but I'm not sure where the
best place to fix it is.  Perhaps the code that is in 
config/require/unix/Makefile can set the include path properly in the
section that decides to use the libiconv peer directory....

Alec

- --UAA99430.974175050/june.cs.washington.edu--

------- End of Forwarded Message


PGP signature

Reply via email to