This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: compile and install bugs on irix
- To: law at cygnus dot com
- Subject: Re: compile and install bugs on irix
- From: Alexandre Oliva <oliva at dcc dot unicamp dot br>
- Date: 23 Jun 1999 06:31:21 -0300
- Cc: Stephane Conversy <Stephane dot Conversy at lri dot fr>, egcs-bugs at egcs dot cygnus dot com, egcs-patches at egcs dot cygnus dot com
- References: <32321.930129360@upchuck.cygnus.com>
On Jun 23, 1999, Jeffrey A Law <law@cygnus.com> wrote:
> In message <orzp1r1h8o.fsf@saci.lsd.dcc.unicamp.br>you write:
>> Moreover, we could stop building install-info, since we don't (appear
>> to) use it, or start to use it instead of wasting CPU cycles on a
>> useless build.
> As you know, the plan is to totally zap the whole texinfo tree after
> gcc-2.95. Until then I want to make the absolute minimal changes
> necessary to this stuff.
I didn't know it, but that's really good to know :-)
> What I do not understand (I did not follow the whole thread) is why other
> folks are not having this problem. What is different about the particular
> system that's choking on libz right now?
IRIX 6's libz.so (AKA libiflPNG) depends on libCsup, but libCsup won't
be linked in at run-time, so `makeinfo' just crashes. I've met this
problem myself, and since then I renamed /usr/lib32/libz.so to
/usr/lib32/libz-disabled.so. I had thought it was just something
broken in my local installation, but now I see I'm not alone.
And then, since we don't need that feature at all, why should we
bother to test it and try to use it, potentially running into a known
problem?
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
{oliva,Alexandre.Oliva}@dcc.unicamp.br aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
*** E-mail about software projects will be forwarded to mailing lists