stdcxx-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Black (JIRA)" <j...@apache.org>
Subject [jira] Updated: (STDCXX-258) run_locale_utils.sh doesn't consider path to locale and localedef
Date Mon, 10 Jul 2006 21:31:30 GMT
     [ http://issues.apache.org/jira/browse/STDCXX-258?page=all ]

Andrew Black updated STDCXX-258:
--------------------------------

    Attachment: run_utils1.diff

A possible patch for run_locale_utils.sh

A problem with this patch is that if the run_locale_utils.sh script is invoked from a location
other than the the bin subdirectory of the build directory, the script will fail to call the
locale and localedef utilities, as it expects them in the current working directory.

This will likely be a problem when manually calling any locale generation wrapper script from
the command line, but the behavior of make/run_all is that the wrapper scripts will be called
with a current working directory being the correct location.

Changelog: 
* run_locale_utils.sh: Alter calls to 'locale' and 'localedef' to call './locale' and './localedef'
respectively 
Change required to avoid using $PATH in calling locale utilities

> run_locale_utils.sh doesn't consider path to locale and localedef
> -----------------------------------------------------------------
>
>          Key: STDCXX-258
>          URL: http://issues.apache.org/jira/browse/STDCXX-258
>      Project: C++ Standard Library
>         Type: Bug

>   Components: Build
>     Reporter: Andrew Black
>  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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message