[jira] Closed: (STDCXX-258) run_locale_utils.sh doesn't consider path to locale and localedef

["Andrew Black (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/STDCXX-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Black closed STDCXX-258.
-------------------------------


Confirmed fixed in a manual test.

How I tested was by creating a 'fake' locale and localedef script, which echoed an error message indicating that it wasn't the desired utility, then exited with a non-zero status.  These scripts were placed in a directory which I prepended to $PATH, then used this PATH to run the sanity_test.sh and en_US.UTF-8.sh scripts.  Both tests ran to completion.

I could see a benefit in altering the test infrastructure so that it used this strategy as part of the tests, but that would be an enhancement for 4.2.1 or later.

> run_locale_utils.sh doesn't consider path to locale and localedef
> -----------------------------------------------------------------
>
>                 Key: STDCXX-258
>                 URL: https://issues.apache.org/jira/browse/STDCXX-258
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 4.1.2, 4.1.3
>            Reporter: Andrew Black
>            Assignee: Martin Sebor
>            Priority: Minor
>             Fix For: 4.2
>
>         Attachments: run_utils1.diff
>
>
> At this time, the run_locale_utils.sh script invoks the locale and localedef utilities using the PATH environment variable to determine the location of the utilities.  This creates a problem if the bin subdirectory of the buildspace isn't in the PATH variable (likely), or if a system copy of locale or localedef is present in the PATH variable prior to the buildspace bin subdirectory.
> One possible solution is to alter the PATH variable when calling the run_locale_utils.sh script, either manually or in the stub locale and sanity_check scripts.  The trade off of this method is that other programs may be invoked incorrectly, if the altered PATH masks another utility used in the script.
> A second possibility is to alter the run_locale_utils.sh script to use relative or absolute paths to the locale and localedef utilities.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.