Re: [Mesa3d-dev] Re: [Mesa3d-users] configure problem (was Missing GLX extensions)

[Brian P. <br...@va...>]

Dirk Reiners wrote:
> 
> OK, next iteration. :)
> 
> On Mar 20,  6:31pm, Sven M. Hallberg wrote:
> > Subject: Re: [Mesa3d-users] configure problem (was Missing GLX
> extensions)
> >
> > Oh, that's ugly. As far as a quick grep indicated the identifier 'quad'
> is
> > used in a number of places. It would probably be pretty painful to wade
> > through all the source files to eliminate every occurance.
> >
> > Do you have any way of preventing bsd_types.h from being included or
> quad from
> > being defined in it?
> 
> It's not really that bad. It's not actually DEFINEd, it's just a typedef.
> I just changed it in ss_tritmp.h and could compile everything. As for
> avoiding it: it's unconditionally included from sys/types.h, and I guess
> that one's is definitely needed.
> 
> > Well, if the compiler doesn't support the feature the only way would be
> to use
> > some sort of preprocessor kludge or hard-code the function names. Both
> options
> > seem kind of hard to accept. I'd say we check for the feature and in
> case it's
> > not available #define __FUNCTION__ to something sensable expressing the
> lack.
> 
> It does support __FILE__ and __LINE__, maybe using these would be better
> than not having any indications of the problem happened.
> 
> > Hm, seems something messed up here. Fixed two minor mistakes, but I
> don't see
> > how these could have caused glut not being built at all:
> >         * Makefile.am: Added src-glut to DIST_SUBDIRS.
> >         * src-glut/Makefile.am: Removed NEED_GLUT check for good.
> >
> > I assume you don't have another GLUT already installed, do you? In that
> case
> > the configure script will use that library instead of the one supplied
> with
> > Mesa. Look for a warning message from configure. You can tell configure
> not to
> > look for an external GLUT using --without-glut.
> 
> OK, looks like that was the problem. I do have another GLUT somewhere,
> --without-glut worked.
> 
> >-- End of excerpt from Sven M. Hallberg
> 
> Nearly.
> 
> The new common_rules.make has a bug in that it uses spaces instead of tabs
> for the new rules, make doesn't like that.
> 
> Some Makefiles use the linker option -no-install, Irix doesn't know that
> one. I don't know what the purpose of that option is, maybe it can just be
> removed.
> 
> Now everything makes. Woohoo! ;)
> 
> I tried making and running a demo from all the different demo directories.
> Compiling works, but they didn't run. Apparently somewhere in si-glu C++
> streams are used. I couldn't actually find it, but the library contains
> undefined references to symbols that are used in that context (__dl__GPv,
> __iob, __vtbl__9type_info, __pure_virtual_called). Adding -lCio to the
> link line fixes that.
> 
> The last thing I found is tests/. The Makefile there doesn't use automake
> yet, and wants to use gcc hardcoded. Don't know how important that is.

The programs under tests/ aren't included in the Mesa distro.  They're
only intended for us developers.  The makefiles aren't too important.

-Brian