From: Fay J. F C. AAC/W. <joh...@eg...> - 2002-11-05 18:24:16
|
Umm ... don't everybody speak at once. I went over to my customer this morning and tried to compile "freeglut" on an SGI workstation over there. We read the "INSTALL" file and got started. - When we ran "./configure", we got an error message: no "ltmain.sh" file. We looked all over for one and couldn't find one. - When we tried simply to "make" in the "freeglut" directory, we got an error message: missing "aclocal" in the command cd . && /c/projects/freeglut/freeglut The system has no "/c" directory to the best of my knowledge. - When we tried to "make" in the "freeglut-1.3" directory (the one with all the source code files), we got an error message: freeglut_internal.h:88:42 X11/extensions/xf86vmode.h -- no such file or directory My customer was not very impressed. Any ideas? John F. Fay joh...@eg... -----Original Message----- From: Fay John F Contr AAC/WMG [mailto:joh...@eg...] Sent: Thursday, October 31, 2002 10:46 AM To: fre...@li... Subject: [Freeglut-developer] Recent Changes to freeglut <snip> I need to pause here and let somebody else pick up the ball. I do not have a Linux machine, so I am unable to test any of my changes on a Linux system. On the other hand, I have a fairly large GLUT-based application which I am trying to port to "freeglut", and my customer wants it to run on Windows, Linux, and SGI. And anything else that may come his way as well. So here is my need: I need somebody with a Linux box to run the GLUT demos with "freeglut" and make sure they behave the same (or at least similarly) with both windowing systems. Any help would be appreciated. <snip> |
From: Don H. <dh...@ho...> - 2002-11-05 21:13:23
|
I noticed the problem with autoconf when I made the mingw makefile for freeglut. Some of the files required by autoconf were missing from the distribution. I think they're in the CVS archives though. The missing files and the immaturity (at that time) of the msys part of mingw convinced me to make my own cheesy makefile. It's pretty generic and might just work with a few modifications on an SGI. It should be in the zip file I gave John, but here it is just in case. I think the -ggdb thing might be mingw specific. CC=gcc CFLAGS=-ggdb -I../include AR = ar RANLIB = ranlib SRCS = freeglut_display.c freeglut_overlay.c freeglut_cursor.c freeglut_videoresize.c freeglut_teapot.c freeglut_font.c freeglut_misc.c freeglut_font_data.c freeglut_joystick.c freeglut_geometry.c freeglut_menu.c freeglut_state.c freeglut_gamemode.c freeglut_init.c freeglut_structure.c freeglut_callbacks.c freeglut_main.c freeglut_window.c freeglut_stroke_roman.c freeglut_stroke_mono_roman.c OBJS = $(SRCS:.c=.o) all : libfreeglut.a libfreeglut.a: $(OBJS) -rm -f libfreeglut.a $(AR) cru libfreeglut.a $(OBJS) $(RANLIB) libfreeglut.a --Don-- _________________________________________________________________ Internet access plans that fit your lifestyle -- join MSN. http://resourcecenter.msn.com/access/plans/default.asp |
From: Stephen J B. <sj...@li...> - 2002-11-05 19:16:15
|
On Tue, 5 Nov 2002, Fay John F Contr AAC/WMG wrote: > Umm ... don't everybody speak at once. Sorry - I'm just *way* too busy to try it right now. I worked 78 hours last week! > I went over to my customer this morning and tried to compile "freeglut" on > an SGI workstation over there. We read the "INSTALL" file and got started. > > - When we ran "./configure", we got an error message: no "ltmain.sh" > file. We looked all over for one and couldn't find one. I don't have convenient access to SGI hardware anymore. ltmain.sh is run by ltconfig which is something to do with libtool IIRC. It should be in the same directory as all the other configure stuff. When I delete it, it seems to be recreated by automake --add-missing as a symlink that points at /usr/share/libtool/ltmain.sh I guess that if your SGI machine doesn't have libtool installed then this isn't going to work terribly well. > - When we tried simply to "make" in the "freeglut" directory, we got an > error message: missing "aclocal" in the command > cd . && /c/projects/freeglut/freeglut > The system has no "/c" directory to the best of my knowledge. Similarly - aclocal appears to be recreated by automake --add-missing if it doesn't exist. Normally, these files are included in the 'tarball' that 'make dist' creates - but they are not normally checked into CVS because they can be recreated on a developer's machine by running automake --add-missing. I suggest that you do one of two things. Either: A) Install the auto* tools on the SGI box and run automake/autoconf like this: aclocal automake --add-missing autoconf ./configure gmake ...or... B) Do those commands on a Linux box and then build a distro using 'make dist'. That should bundle all the needed '.sh' and '.m4' files into the tarball which you should then be able to build on your SGI machine using just: ./configure make install ...I havn't tried either of those things for freeglut on an SGI machine though. > - When we tried to "make" in the "freeglut-1.3" directory (the one with > all the source code files), we got an error message: > freeglut_internal.h:88:42 X11/extensions/xf86vmode.h -- no such > file or directory Hmmm - freeglut shouldn't be using that. This is an XFree86-specific extensions for switching Video modes that SGI's IRIX doesn't have. I wonder what features of XFree86 freeglut is depending on here? Probably something in the 'GameGLUT' stuff. > My customer was not very impressed. Alas - The well-known customer-proximity effect. ---- Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation & Training (817)619-2466 (Fax) Work: sj...@li... http://www.link.com Home: sjb...@ai... http://www.sjbaker.org |
From: James J. <jcp...@co...> - 2002-11-05 19:02:18
|
On Tue, 2002-11-05 at 13:12, Fay John F Contr AAC/WMG wrote: > Umm ... don't everybody speak at once. > =20 > I went over to my customer this morning and tried to compile "freeglut" o= n > an SGI workstation over there. We read the "INSTALL" file and got starte= d. N.b. I've never been able to play with Irix before. So take what I say with a grain of salt...=20 =20 > - When we ran "./configure", we got an error message: no "ltmain.sh" > file. We looked all over for one and couldn't find one. 'ltmain.sh' is part of the libtool package, which is basically a shared library generation package. The Libtool homepage is: http://www.gnu.org/software/libtool/libtool.html It may be installed on that machine already, though (I wouldn't see why not...); try executing=20 find / -name "ltmain.sh" -print and seeing if it's already installed in some unexpected place. > - When we tried simply to "make" in the "freeglut" directory, we got = an > error message: missing "aclocal" in the command > cd . && /c/projects/freeglut/freeglut > The system has no "/c" directory to the best of my knowledge. 'aclocal' is part of the automake package, and is definitely needed... It turns a 'configure.in' into a 'aclocal.m4' Automake's homepage is at: http://www.gnu.org/software/automake/ Automake requires Autoconf, which can be located here: http://www.gnu.org/software/autoconf/ > - When we tried to "make" in the "freeglut-1.3" directory (the one wi= th > all the source code files), we got an error message: > freeglut_internal.h:88:42 X11/extensions/xf86vmode.h -- no suc= h > file or directory According to the Freeglut news (http://freeglut.sourceforge.net/freeglut.html): "Argh. Don't be surprised if the code doesn't compile under X-11 other than XFree86. It could fail when trying to include the X11/extensions/xf86vmode.h include header, in that case just comment out that inclusion line (found in freeglut_internal.h). Is there any intelligent way to detect the existence of an include header, and if it's autoconf to be the answer, how to use it?" So just comment it out, I guess. > My customer was not very impressed. Sorry about that... I expect not... It *does* work, though! --=20 James 'Pug' Jones "I give (this watch) to you not that you may remember time,=20 but that you might forget it now and then for a moment and=20 not spend all your breath trying to conquer it." - Mr. Compson to Quentin, "The Sound and the Fury" by William Faulkner |
From: Stephen J B. <sj...@li...> - 2002-11-06 14:51:53
|
On 5 Nov 2002, James Jones wrote: > > - When we ran "./configure", we got an error message: no "ltmain.sh" > > file. We looked all over for one and couldn't find one. > > 'ltmain.sh' is part of the libtool package, which is basically a shared > library generation package. <snip> The point here is that (as with any 'auto-*' configured package) you have two choices: 1) Install from CVS. Make sure that you have a recent set of the 'auto*' tools (automake, autoconf, libtool, etc) and run something like: aclocal automake --add-missing autoconf ./configure make The three commands before './configure' construct all of the wierd and wonderful '.m4' and '.sh' files that the mechanism requires. ...OR... 2) Install from a 'distro' - which is made on a developers system using the commands in (1) above. That distro is supposed to contain everything the end user needs - except for the minimal shell toolset that all 'sane' Unix systems have. It specifically DOESN'T need to have the 'auto*' tools installed. So, if you take a distro tarball (*NOT* a CVS download) then you should be able to build without any auto* tools just by saying: ./configure make If mechanism (1) isn't working then you probably have a broken set of auto* tools. If mechanism (2) isn't working then there is probably an error in freeglut's Makefile.am or configure.in that is somehow not including a needed file into the distro. You can make a 'distro' tarball from the CVS version (providing you have the auto* tools) using: make dist ...the tarball will magically appear ready-to-install in the top level freeglut directory. Any attempt at doing some weird hybrid of (1) and (2) is DOOMED to failure (or at least horrible anguish). eg Downloading the CVS on one machine, running aclocal/automake/autoconf on that system and then taking the resulting files over to another machine without doing the 'make dist' and installing the resulting tarball...that kind of thing is **BAD** and results in exactly this kind of problem. Also (as I explained before) - you need to be sure that ALL of the auto* tools are updated at the same time with compatible releases. Don't grab a new libtool without ALSO grabbing new automake, autoconf, aclocal, etc. Probably someone who was a deep guru wrt the auto* tools could juggle things without following these practices - but I've never met anyone with that kind of competance! ---- Steve Baker (817)619-2657 (Vox/Vox-Mail) L3Com/Link Simulation & Training (817)619-2466 (Fax) Work: sj...@li... http://www.link.com Home: sjb...@ai... http://www.sjbaker.org |