This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libstdc++-v3 configuration and check problems under hpux 10.20
- To: John David Anglin <dave at hiauly1 dot hia dot nrc dot ca>
- Subject: Re: libstdc++-v3 configuration and check problems under hpux 10.20
- From: Phil Edwards <pedwards at disaster dot jaj dot com>
- Date: Mon, 5 Mar 2001 15:14:23 -0500
- Cc: Alexandre Oliva <aoliva at redhat dot com>, gcc-bugs at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org
- References: <or8zn1anm3.fsf@guarana.lsd.ic.unicamp.br> <200103051923.OAA14016@hiauly1.hia.nrc.ca>
On Mon, Mar 05, 2001 at 02:23:11PM -0500, John David Anglin wrote:
> > AFAIK, mkcheck is a bash-only shell-script. In any case, this patch
> > might help. Please let me know if it fixes the problem.
>
> No. It didn't work. The problem is the `-n' from the echo command near
> the end of tests_flags. This ends up in argument 1. Here is one possible
> method to fix the problem. Since mkcheck is a bash script, we can use
> bash for tests_flags as well.
I don't know what "this patch" in the previous message referred to, but this
latest patch is the wrong approach. We want to move /away/ from requiring
Bash to be installed. The current mkcheck.in was just a temporary measure.
In any case, this has already been fixed in the mainline, a few weeks ago.
It hasn't been picked up in the truck/branch merges since then because it
didn't seem to fit the 3.0 criteria.
Phil
--
pedwards at disaster dot jaj dot com | pme at sources dot redhat dot com
devphil at several other less interesting addresses in various dot domains
The gods do not protect fools. Fools are protected by more capable fools.