This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Anyone got irix5? I have questions about your ctype implementation
- From: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- To: aoliva at redhat dot com, mark at codesourcedy dot com
- Cc: cgf at redhat dot com, gcc-patches at gcc dot gnu dot org, gcc at gcc dot gnu dot org, java-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org, ro at TechFak dot Uni-Bielefeld dot DE
- Date: Tue, 7 May 2002 19:56:23 -0400 (EDT)
- Subject: Re: Anyone got irix5? I have questions about your ctype implementation
- References: <200205020414.AAA15565@caip.rutgers.edu> <20020503013353.GA2985@redhat.com> <200205031423.KAA13608@caip.rutgers.edu> <yddg019w2mf.fsf@xayide.TechFak.Uni-Bielefeld.DE> <200205032010.QAA10493@caip.rutgers.edu> <or8z6zrxh2.fsf@livre.redhat.lsd.ic.unicamp.br> <200205060400.AAA21303@caip.rutgers.edu> <ory9explnm.fsf@free.redhat.lsd.ic.unicamp.br> <200205061211.IAA02448@caip.rutgers.edu> <orbsbr50h0.fsf@free.redhat.lsd.ic.unicamp.br> <or8z6v3ebk.fsf@free.redhat.lsd.ic.unicamp.br> <orit5z1rcw.fsf@free.redhat.lsd.ic.unicamp.br>
> From: Alexandre Oliva <aoliva@redhat.com>
>
> On May 7, 2002, Alexandre Oliva <aoliva@redhat.com> wrote:
>
> > Never mind. I've just duplicated it with a full bootstrap. Something
> > is polluting mabi=64/config.cache with an incorrect setting of LD.
> > Either libf2c or libstdc++-v3. I'm looking into it.
>
> Ok, any libtool library would do it, due to an ill effect of (some)
> shells.
>
> My understanding is that, if an exported variable is modified in a
> shell script, the modified value is not supposed to be automatically
> re-exported. It should be kept private to the script.
>
> It appears that IRIX's /bin/sh doesn't agree with my understanding, so
> this work around was necessary. Ideally, libtool shouldn't mess up
> with LD, but I'd rather not touch this at this point.
Huh? Never heard of that rule. I routinely bootstrap with
CONFIG_SHELL of /bin/ksh or /bin/bash anyway so unless they all share
the bug, I think you may be mistaken. Consider this:
---file foo---------------------
#!/bin/bash
export VAR=xxx
VAR=yyy
./bar
---file bar---------------------
#!/bin/bash
echo $VAR
--------------------------------
what should running "foo" output? Under bash-2.03, I get "yyy".
--Kaveh
--
Kaveh R. Ghazi Director of Systems Architecture
ghazi@caip.rutgers.edu Qwest Global Services