On Thu, 7 Sep 1995, dk smith wrote:
> Here are notes I took during the last couple of hours...
>
> bison variable not set though bin var was set to '/opt/gnu/bin'
Yes. bison is not used, but Configure searches for a generic long list
of programs that might be used. I suppose I could trim them out of
Configure, but it never seemed worth the effort.
> I get the same results (final config.sh file and std output) when I invoke
> the script with any of the following:
>
> ./Configure -de
>
> ./Configure -des -Dcc=gcc -Dlibpth="/usr/lib /usr/ccs/lib /opt/sww/lib
> /opt/gnu/lib /opt/gnu/lib/gcc-lib/sparc-sun-solaris2.4/2.7.0"
> -Dlibc=/usr/lib/libc.so
>
> ./Configure -Dcc=gcc -Dlibpth="/usr/lib /usr/ccs/lib /opt/sww/lib
> /opt/gnu/lib /opt/gnu/lib/gcc-lib/sparc-sun-solaris2.4/2.7.0"
> -Dlibc=/usr/lib/libc.so -Dprefix=/opt/sww -des
Huh?
./Configure -de
and
./Configure -de -Dcc=gcc
will use different compilers. The first will use cc. The second will
use gcc. You must be re-using a config.sh. Don't do that. Quoting
from README:
If you change compilers or make other significant changes, you should
probably _not_ re-use your old config.sh. Simply remove it or
rename it, e.g. mv config.sh config.sh.old. Then rerun Configure
with the options you want to use.
Note that autoconf packages that use config.cache have *exactly* the
same problem.
> Why does this have to be so difficult?
Why does what have to be so difficult? I'm unclear what you're trying
to do that you find difficult.
rm config.sh
sh Configure -de -Dcc=gcc -Dprefix=/opt/sw
works just fine, and is documented in README.
I don't mean to be dense or unhelpful, and I do understand that
Configure asks a lot of questions, but I just don't understand what
specific problems you're having and how we can help you solve them.
If you have specific suggestions for README or patches for Configure,
I'll be happy to try to include them.
Andy Dougherty doughera@lafcol.lafayette.edu
> Here are notes I took during the last couple of hours...
>
> bison variable not set though bin var was set to '/opt/gnu/bin'
Yes. bison is not used, but Configure searches for a generic long list
of programs that might be used. I suppose I could trim them out of
Configure, but it never seemed worth the effort.
> I get the same results (final config.sh file and std output) when I invoke
> the script with any of the following:
>
> ./Configure -de
>
> ./Configure -des -Dcc=gcc -Dlibpth="/usr/lib /usr/ccs/lib /opt/sww/lib
> /opt/gnu/lib /opt/gnu/lib/gcc-lib/sparc-sun-solaris2.4/2.7.0"
> -Dlibc=/usr/lib/libc.so
>
> ./Configure -Dcc=gcc -Dlibpth="/usr/lib /usr/ccs/lib /opt/sww/lib
> /opt/gnu/lib /opt/gnu/lib/gcc-lib/sparc-sun-solaris2.4/2.7.0"
> -Dlibc=/usr/lib/libc.so -Dprefix=/opt/sww -des
Huh?
./Configure -de
and
./Configure -de -Dcc=gcc
will use different compilers. The first will use cc. The second will
use gcc. You must be re-using a config.sh. Don't do that. Quoting
from README:
If you change compilers or make other significant changes, you should
probably _not_ re-use your old config.sh. Simply remove it or
rename it, e.g. mv config.sh config.sh.old. Then rerun Configure
with the options you want to use.
Note that autoconf packages that use config.cache have *exactly* the
same problem.
> Why does this have to be so difficult?
Why does what have to be so difficult? I'm unclear what you're trying
to do that you find difficult.
rm config.sh
sh Configure -de -Dcc=gcc -Dprefix=/opt/sw
works just fine, and is documented in README.
I don't mean to be dense or unhelpful, and I do understand that
Configure asks a lot of questions, but I just don't understand what
specific problems you're having and how we can help you solve them.
If you have specific suggestions for README or patches for Configure,
I'll be happy to try to include them.
Andy Dougherty doughera@lafcol.lafayette.edu