Re: new snapshot?

[Jonathan Stickel]

John W. Eaton wrote:
> On  9-Feb-2009, Jonathan Stickel wrote:
>
> | On 2/6/09 address@hidden wrote:
> | >      +. Graphics:
> | >    + Refactor base_properties
> | >    + Specific types for properties with improved property value
> | >      checking
> | >    + Implement the addprops function allow additional properties
> | >      to objects
> | >    + add the hggroup object that has no fixed properties for use
> | >      by barseries, etc.
> | >    + Add callback DeleteFcn/CreateFcn to objects
> | >    + Allow listener functions to be added to objects
> | >    + Clean separation of backend from property database
> | >    + Implement experimental backend based on OpenGL and GUI
> | >      toolkit
> | 
> | I have been interested for some time now to hack around with the new
> | OpenGL backend.  However, the FTGL text dependency was not detected 
> | properly on my Mac (OS X 10.4.11).  After a recent mercurial update, 
> | this problem still exists:
> | 
> | configure: WARNING: "FTGL library not found. Native renderer will not 
> | have on-screen text"
> | configure: WARNING:
> | configure: WARNING: I didn't find the necessary libraries to compile native
> | configure: WARNING: graphics. It isn't necessary to have native graphics
> | configure: WARNING: but you will have to use gnuplot or you won't be able
> | configure: WARNING: to use any of Octave's plotting commands
> | configure: WARNING:
> | 
> | I do have ftgl-2.1.2 installed via Macports.  Anyway, it would be nice 
> | if this could be resolved before the next snapshot.  I remember quite a 
> | long thread about this problem some time ago, but I don't remember what 
> | the conclusion was.  I am willing to help debug if someone can suggest 
> | something for me to try.
>
> It's unlikely to be resolved unless it's reported, and this is the
> first I'ver heard of the problem in quite some time as I thought we
> fixed it.
>
> You could start by showing the relevant part of config.log, so we
> could see why the test fails.
>
> As I recall, I used to have to add
>
>   -I/usr/include/freetype2
>
> to CPPFLAGS on my system when running configure, but I think we fixed
> that problem as it no longer seems to be required.

Here is what seems to be the FTGL test in config.log:

configure:12370: checking FTGL/ftgl.h usability
configure:12387: g++ -c -I/usr/local/include -I/opt/local/include 
-I/opt/local/include/freetype2 -I/opt/local/include 
-I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include 
conftest.cpp >&5
configure:12394: $? = 0
configure:12408: result: yes
configure:12412: checking FTGL/ftgl.h presence
configure:12427: g++ -E  -I/opt/local/include 
-I/opt/local/include/freetype2 -I/opt/local/include conftest.cpp
configure:12434: $? = 0
configure:12448: result: yes
configure:12476: checking for FTGL/ftgl.h
configure:12485: result: yes
configure:12659: checking for FTGLTextureFont in -lftgl
configure:12699: g++ -o conftest -I/usr/local/include 
-I/opt/local/include -I/opt/local/include/freetype2 -I/opt/local/include 
 -I/opt/local/include -I/opt/local/include/freetype2 
-I/opt/local/include -L/usr/local/lib -L/opt/local/lib -lmetis 
conftest.cpp -lhdf5 -lz -lm  -Wl,-framework -Wl,Carbon -L/usr/X11R6/lib 
-lGL -lGLU -L/opt/local/lib -lfreetype -lz -Wl,-framework,CoreServices 
-Wl,-framework,ApplicationServices -lftgl >&5
conftest.cpp: In function 'int main()':
conftest.cpp:81: error: 'FTGLTextureFont' was not declared in this scope
conftest.cpp:81: error: expected `;' before 'font'
configure:12706: $? = 1
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME ""
| #define PACKAGE_TARNAME ""
| #define PACKAGE_VERSION ""
| #define PACKAGE_STRING ""
| #define PACKAGE_BUGREPORT ""
| #define OCTAVE_SOURCE 1
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define SEPCHAR ':'
| #define SEPCHAR_STR ":"
| #define __NO_MATH_INLINES 1
| #define CXX_NEW_FRIEND_TEMPLATE_DECL 1
| #define CXX_ISO_COMPLIANT_LIBRARY 1
| #define HAVE_X_WINDOWS 1
| #define HAVE_FRAMEWORK_CARBON 1
| #define HAVE_LIBM 1
| #define HAVE_QHULL 1
| #define HAVE_PCRE_COMPILE 1
| #define HAVE_PCRE 1
| #define HAVE_REGEXEC 1
| #define HAVE_REGEX 1
| #define HAVE_ZLIB_H 1
| #define HAVE_ZLIB 1
| #define HAVE_HDF5_H 1
| #define HAVE_HDF5 1
| #define HAVE_H5GGET_NUM_OBJS 1
| #define HAVE_GLPK_H 1
| #define HAVE_GLPK 1
| #define HAVE_CURL_CURL_H 1
| #define HAVE_CURL 1
| #define HAVE_MAGICK 1
| #define HAVE_OPENGL_GL_H 1
| #define HAVE_OPENGL_GLU_H 1
| #define HAVE_OPENGL 1
| #define HAVE_FTGL_FTGL_H 1
| /* end confdefs.h.  */
|
| #ifdef HAVE_FTGL_FTGL_H
| #ifdef HAVE_FTGL_UPPERCASE
| #include <FTGL/FTGL.h>
| #include <FTGL/FTGLTextureFont.h>
| #else
| #include <FTGL/ftgl.h>
| #endif
| #elif HAVE_FTGL_H
| #ifdef HAVE_FTGL_UPPERCASE
| #include <FTGL.h>
| #include <FTGLTextureFont.h>
| #else
| #include <ftgl.h>
| #endif
| #endif
| int
| main ()
| {
|
| FTGLTextureFont font("");
|   ;
|   return 0;
| }
configure:12731: result: no


> | Octave development sources are also not detecting my installed fftw and 
> | arpack libraries, but I will leave that for later.
>
> Simply posting this vague information does not help much.  It works
> for me.  How did you install them?  Can your compiler find them
> without special flags?  If special flags are needed, are you passing
> them to configure in some way?  How?

Yes, I know this report was not helpful for solving the fftw and arpack 
problems.  But as I said, I am not interested in solving this part now. 
 I only reported it in case there exists a trivial fix that someone is 
aware of.

Jonathan