mesa3d-dev

[Mesa3d-dev] autoconfmake bugs fixed

[Sven M. H. <pe...@gm...>]

So here it is finally, someone should close the following bugs:


Bug #126494: Fixed.

Bug #114967: Fixed.

Bug #122196: Can be closed, existing Makefile is already correct.

Bug #122198: Regenerated the file lists by simply putting in *.[ch] found in
             the corresponding source directory. Library and checks build,
             All demos I tried ran fine. -> Can be closed.

Bug #122644: Appears fixed already. Checks for cpuid, MMX, and 3Dnow all
             return "yes" on my system. -> Can be closed.


I've already checked the changes into CVS, so everyone please try the
autoconfmake build mechanism on your systems and report any issues remaining
(submit them to the bug database at sourceforge and drop a note on the list).


Regards,
Sven

PS: I've used the very latest versions of autoconf, automake, and libtool from
their respective CVS repositories. This is reflected in some changes. So be
sure to get those before you try to run the bootstrap script!

-- 
"Would the All-Seeing Eye please look in my direction?"
 [ KeyID........: 0xC297FEAB ]
 [ Fingerprint..: FEA5 0F93 7320 3F39 66A5  AED3 073F 2D5F C297 FEAB ]

Re: [Mesa3d-dev] autoconfmake bugs fixed

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

"Sven M. Hallberg" wrote:
> 
> So here it is finally, someone should close the following bugs:
> 
> Bug #126494: Fixed.
> 
> Bug #114967: Fixed.
> 
> Bug #122196: Can be closed, existing Makefile is already correct.
> 
> Bug #122198: Regenerated the file lists by simply putting in *.[ch] found in
>              the corresponding source directory. Library and checks build,
>              All demos I tried ran fine. -> Can be closed.
> 
> Bug #122644: Appears fixed already. Checks for cpuid, MMX, and 3Dnow all
>              return "yes" on my system. -> Can be closed.
> 
> I've already checked the changes into CVS, so everyone please try the
> autoconfmake build mechanism on your systems and report any issues remaining
> (submit them to the bug database at sourceforge and drop a note on the list).

Thanks.  I've closed these bugs.


> Regards,
> Sven
> 
> PS: I've used the very latest versions of autoconf, automake, and libtool from
> their respective CVS repositories. This is reflected in some changes. So be
> sure to get those before you try to run the bootstrap script!

Could you tell us which versions you're using?

-Brian

Re: [Mesa3d-dev] autoconfmake bugs fixed

[Sven M. H. <pe...@gm...>]

On Fri, Jan 05, 2001 at 09:10:11AM -0700, Brian Paul wrote:
> > Regards,
> > Sven
> > 
> > PS: I've used the very latest versions of autoconf, automake, and libtool from
> > their respective CVS repositories. This is reflected in some changes. So be
> > sure to get those before you try to run the bootstrap script!
> 
> Could you tell us which versions you're using?

I follow the development of autoconf, automake, and libtool pretty closely,
because they're adding nifty features all the time. I've used some of these 
features in the process of updating Mesa's configure.in and Makefile.am's.

-- FYI --
Here are the versions the programs themselves report:

Autoconf: autoconf (GNU autoconf) 2.49c
Automake: automake (GNU automake) 1.4c
Libtool: ltmain.sh (GNU libtool) 1.3c (1.851 2001/01/05 09:33:38)

And these are the commands I used to retrieve the package sources from the
appropriate CVS repositories, quoted directly from the respective web pages:

Autoconf (quoting from http://sources.redhat.com/autoconf/):
 cvs -z9 -d :pserver:an...@su...:/cvs login
 {empty password}
 cvs -z9 -d :pserver:an...@su...:/cvs checkout autoconf

Automake (quoting from http://sources.redhat.com/automake/):
 cvs -z 9 -d :pserver:an...@an...:/cvs/automake login
     (password is ``anoncvs'')
 cvs -z 9 -d :pserver:an...@an...:/cvs/automake co automake

Libtool (quoting from http://www.gnu.org/software/libtool/):
 $ cvs -z3 -d :pserver:an...@su...:/home/cvs login
 Password:
 $ cvs -z3 -d :pserver:an...@su...:/home/cvs co libtool

I pulled the packages out of CVS just a few minutes ago (my current time is
2001-01-07 16:22 CET), and everything worked. A bug in automake I mentioned
in an earlier mail is fixed by now.


Best regards,
Sven

PS: Unfortunately my Christmas vacation ends tomorrow and I will have to return
    to serve my country for another four months, so expect to hear from me
    again next weekend.

-- 
"Would the All-Seeing Eye please look in my direction?"
 [ KeyID........: 0xC297FEAB ]
 [ Fingerprint..: FEA5 0F93 7320 3F39 66A5  AED3 073F 2D5F C297 FEAB ]

Re: [Mesa3d-dev] autoconfmake bugs fixed

[Marcelo E. M. <mar...@bi...>]

>> "Sven M. Hallberg" <pe...@gm...> writes:

 > I follow the development of autoconf, automake, and libtool pretty closely,
 > because they're adding nifty features all the time. I've used some of these 
 > features in the process of updating Mesa's configure.in and Makefile.am's.

 I'm sure everyone appreciates your work (I do), but using unreleased
 tools kinda makes it difficult for people to actually *test* stuff.  I
 was trying to build Mesa 3.4 with some of the bells and whistles (GGI,
 glide2, glide3) and found out it won't build.  Among the problems, I
 found some of the Makefile.am are wrong.  I pulled new Makefile.am's
 and configure.in from CVS to see if the problems had been dealt with
 already, just to find out that that I needed to hunt for some special
 version of automake and libtool.

 Since one of the new features you have used is something I have wished
 for myself, I can understand why using it is desirable, but...

 (I'll send a patch for Mesa 3.4 sometime this week, I still need to
 figure out the glide2 problems first)

--
Marcelo

Re: [Mesa3d-dev] autoconfmake bugs fixed

[Lee B. <le...@i-...>]

On Sun, 07 Jan 2001, Sven M. Hallberg wrote:

> -- FYI --
> Here are the versions the programs themselves report:
> 
> Autoconf: autoconf (GNU autoconf) 2.49c
> Automake: automake (GNU automake) 1.4c
> Libtool: ltmain.sh (GNU libtool) 1.3c (1.851 2001/01/05 09:33:38)

Sven,

I tried the latest from these cvs repositories and I failed to build libtool.

ltmain.sh (GNU libtool) 1.3c (1.852 2001/01/08 01:52:10)   

I managed to get the above versions of autoconf and automake to build however.  

Can download (or anybody) download the latest libtool and get it to work?

I get the following errors.
 
lee@darkstar:~/cvs/libtool$ ./bootstrap
configure:5820: error: undefined macro: AR_FLAGS
autoheader: config.h.in is unchanged
configure.in: 33: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
configure:6074: error: undefined macro: AR_FLAGS
configure.in: 10: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
Makefile.am:126: variable `libdir' not defined
Makefile.am:130: variable `libdir' not defined
configure:5650: error: undefined macro: AR_FLAGS
configure.in: 8: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
configure:5478: error: undefined macro: AR_FLAGS
configure.in: 16: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
configure:5971: error: undefined macro: AR_FLAGS
configure.in: 8: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
configure:5478: error: undefined macro: AR_FLAGS      

<gripe>
I understand that it might be useful to have the latest
autoconf/automake/libtool set,  but why not use the latest stable releases
rather than the latest bleeding edge tools? It seems to me this would take out
one more source of bugs in the code.  I also have to do four cvs updates just
to get mesa to work rather than one.  Perhaps mesa is such a special library
that it requires the latest and greatest,  but I really doubt it. I may add
this is coming from somebody who considers himself pretty good at automake.
</gripe>

Thanks ahead for any assistance.
Lee

-- 
Lee Brown Jr.
le...@i-...

Re: [Mesa3d-dev] autoconfmake bugs fixed

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

Lee Brown wrote:
> 
> On Sun, 07 Jan 2001, Sven M. Hallberg wrote:
> 
> > -- FYI --
> > Here are the versions the programs themselves report:
> >
> > Autoconf: autoconf (GNU autoconf) 2.49c
> > Automake: automake (GNU automake) 1.4c
> > Libtool: ltmain.sh (GNU libtool) 1.3c (1.851 2001/01/05 09:33:38)
> 
> Sven,
> 
> I tried the latest from these cvs repositories and I failed to build libtool.
> 
> ltmain.sh (GNU libtool) 1.3c (1.852 2001/01/08 01:52:10)
> 
> I managed to get the above versions of autoconf and automake to build however.
> 
> Can download (or anybody) download the latest libtool and get it to work?
> 
> I get the following errors.
> 
> lee@darkstar:~/cvs/libtool$ ./bootstrap
> configure:5820: error: undefined macro: AR_FLAGS
> autoheader: config.h.in is unchanged
> configure.in: 33: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
> configure:6074: error: undefined macro: AR_FLAGS
> configure.in: 10: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
> Makefile.am:126: variable `libdir' not defined
> Makefile.am:130: variable `libdir' not defined
> configure:5650: error: undefined macro: AR_FLAGS
> configure.in: 8: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
> configure:5478: error: undefined macro: AR_FLAGS
> configure.in: 16: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
> configure:5971: error: undefined macro: AR_FLAGS
> configure.in: 8: `AM_PROG_LIBTOOL' is obsolete, use `AC_PROG_LIBTOOL' instead
> configure:5478: error: undefined macro: AR_FLAGS
> 
> <gripe>
> I understand that it might be useful to have the latest
> autoconf/automake/libtool set,  but why not use the latest stable releases
> rather than the latest bleeding edge tools? It seems to me this would take out
> one more source of bugs in the code.  I also have to do four cvs updates just
> to get mesa to work rather than one.  Perhaps mesa is such a special library
> that it requires the latest and greatest,  but I really doubt it. I may add
> this is coming from somebody who considers himself pretty good at automake.
> </gripe>

I haven't had time to try the new tools and ./bootstrap but I'm
concerned about needing bleeding-edge tools.  Why are these
development versions of libtool, etc needed?

-Brian