[I'm moving this thread back to mesa-dev]
On 11-Jul-99 Brian Paul wrote:
> I removed the dead lock just now.
Thanks. Does my patch fix your problem?
>> > Another question: exactly which configure-related files are supposed to
>> > be included in the Mesa tar file?
>> configure, acinclude.m4,
Thomas Tanner wrote:
>
> On 08-Jul-99 Brian Paul wrote:
> > OK, I think I've finally got all the GNU utilities going on IRIX.
> > But compiling Mesa doesn't work. Here's the output:
> >
> > % ./configure
> [...]
>
> looks good so far
>
> > updating cache ./config.cache
> > loading cache ./con
On 08-Jul-99 Brian Paul wrote:
> OK, I think I've finally got all the GNU utilities going on IRIX.
> But compiling Mesa doesn't work. Here's the output:
>
> % ./configure
[...]
looks good so far
> updating cache ./config.cache
> loading cache ./config.cache
> checking for a BSD compatible in
Thomas Tanner wrote:
>
> On 08-Jul-99 Brian Paul wrote:
> > Thomas Tanner wrote:
> >> To generate the files just run the "bootstrap" script in the
> >> toplevel directory.
> > What is 'aclocal' and where can I get it?
> > I'm trying to setup autoconfig, etc on IRIX 6.5 (with out luck so far).
>
On 08-Jul-99 Brian Paul wrote:
> Thomas Tanner wrote:
>> To generate the files just run the "bootstrap" script in the
>> toplevel directory.
> What is 'aclocal' and where can I get it?
> I'm trying to setup autoconfig, etc on IRIX 6.5 (with out luck so far).
aclocal is part of automake (see f
Thomas Tanner wrote:
> To generate the files just run the "bootstrap" script in the
> toplevel directory.
What is 'aclocal' and where can I get it?
I'm trying to setup autoconfig, etc on IRIX 6.5 (with out luck so far).
-Brian
On 07-Jul-99 Brian Paul wrote:
> Questions:
> 1. Shouldn't there be a "configure" file? Or, how do I make it?
It's generally a bad idea to include the generated files (configure,
Makefile.in etc.) in the CVS tree because every time you modify one
of the source files (configure.in, Makefile.a
Thomas Tanner wrote:
>
> On 03-Jul-99 Brian Paul wrote:
> >Those of you working on autoconfig scripts on the experimental
> >branch can bring them to the main branch whenever you want.
>
> Done.
Questions:
1. Shouldn't there be a "configure" file? Or, how do I make it?
2. I'd like
On 03-Jul-99 Brian Paul wrote:
>Those of you working on autoconfig scripts on the experimental
>branch can bring them to the main branch whenever you want.
Done.
Thomas Tanner -
email: tanner@(ffii.org|gnu.org|ggi-project.org|gmx.de)
web: http
I've just checked in a number of significant changes:
1. Most "Makefile"'s are now obsolete/gone. They've been replaced
with new makefiles named Makefile.X11
This will allow autoconfig to generate new makefiles without
overwriting the originals.
One special case is the top-level M
10 matches
Mail list logo
