2.95.1 and .2 configure bug on solaris
Nils Lohner
lohner@hew.ecf.teradyne.com
Wed Jan 5 02:17:00 GMT 2000
In message < 200001042145.WAA00837@loewis.home.cs.tu-berlin.de >, "Martin v.
Loew
is" writes:
>> I've seen this problem in these two releases, and some before that as well.
>
>I haven't seen this before, even though I've installed gcc on Solaris
>a number of times. Is there something modified in your build environment?
>
What could be modified? Can you give me some examples on where to look?
Most things shoudl be GNU tools, shells are the only thing I can think of.
I have a /sup tree where all my hand build binaries (including compilers,
etc.) go, all compiled with --prefix=/sup and that should be first in all
paths and seems to be propeorly detected by config scripts as well.
>> If there's anything I can do to narrow it down, let me know.
>
>You can put a 'set -x' in the configure script(s), to see the shell
>commands as they are executed in order.
>
Which configure scripts in particular? I just tried recompiling binutils
2.9.1 (to go after the libgcc problem) and also saw the same thing, funnily
enough...
Nils.
More information about the Gcc-bugs
mailing list