[Mesa3d-dev] [ mesa3d-Bugs-438348 ] Clean CVS checkout fails to build.

[<no...@so...>]

Bugs item #438348, was opened at 2001-07-03 14:06
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100003&aid=438348&group_id=3

Category: mesa-core
Group: Compile/Install
Status: Open
Resolution: None
Priority: 5
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Clean CVS checkout fails to build.

Initial Comment:
1) the bootstrap script fails because most automakes
want an argument "Makefile"

===================================================================
RCS file: /cvsroot/mesa3d/Mesa/bootstrap,v
retrieving revision 1.12
diff -u -r1.12 bootstrap
--- bootstrap   2001/06/26 14:11:45     1.12
+++ bootstrap   2001/07/03 20:43:45
@@ -20,7 +20,7 @@
 run_cmd libtoolize --automake --copy --force
 run_cmd aclocal
 run_cmd autoheader
-run_cmd automake -a -c
+run_cmd automake -a -c Makefile
 run_cmd autoconf
 
 exit 0


2) It is not entirely clear to a novice (me) that
automake-2.5 is actually  automake-2.50 and that the
automake-2.13 currently being distributed does not
support AC_CONFIG_FILES. (The 2.50 test in configure.in
catches this, but is it a bit of a struggle, the
tempation was to interpret the "0" as a typo, and
conclude that you meant 2.5 ..... an obsolete
automake!)


3) There are no instructions to build the Makfile.in's
in the sub directories so that AC_CONFIG_FILES can do
its stuff. One has to conclude that

foreach file ( `find . -name 'Makefile.am'` )
  automake -a -c `basname $file .am`
end

is the thing to do. Maybe the sh version of this
belongs in bootstrap.

4) Probably an autoconf bug, but the current autoconf
generated configure does not copy info like

 
# ### BEGIN LIBTOOL CONFIG
# Libtool was configured on host pcrod:
#
# CC="gcc" CFLAGS="-O2 -march=i386 -mcpu=i686"
CPPFLAGS="" \
# LD="/usr/bin/ld" LDFLAGS="" LIBS="" \
# NM="/usr/bin/nm -B" RANLIB="ranlib" LN_S="ln -s" \
# DLLTOOL="" OBJDUMP="" AS="" \
#   ./ltconfig --with-gcc --with-gnu-ld --enable-dlopen
--srcdir=. --output=libtool ./ltmain.sh
#
# Compiler and other test output produced by ltconfig,
useful for
# debugging ltconfig, is in ./config.log if it exists.
 
# The version of ltconfig that generated this script.
LTCONFIG_VERSION="1.3.5"

to the spot before SHELL=/bin/sh in libtool. Hence
libtool fails with a version mismatch.

5) Doco to the effect that

./configure --disable-osmesa --prefix=/usr
--infodir=/usr/share/info --mandir=/usr/share/man

is probably the right thing for linux. The
--disable-osmesa is needed on the first build because
the osmesa make tries to link to a library that is not
built yet.


Hope this helps, I know how easy it is to miss stuff
like this when you have a working CVS sandpit.

Cheers.

----------------------------------------------------------------------

You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=100003&aid=438348&group_id=3