Bug 70267 - TVT3.0: In japanese locale, automated discovery of include paths doesn't seem to work
Summary: TVT3.0: In japanese locale, automated discovery of include paths doesn't see...
Status: CLOSED FIXED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux
: P1 critical (vote)
Target Milestone: 2.0.1   Edit
Assignee: Victor Lenet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-07-16 15:59 EDT by Jonathan Simpson CLA
Modified: 2004-07-30 16:30 EDT (History)
3 users (show)

See Also:


Attachments
screen capture (53.99 KB, image/gif)
2004-07-16 16:00 EDT, Jonathan Simpson CLA
no flags Details
jpn created project (1.19 KB, application/zip)
2004-07-22 11:15 EDT, Jonathan Simpson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Simpson CLA 2004-07-16 15:59:59 EDT
When creating a Standard Make C++ project, the automated discovery of include 
paths doesn't seem to work when running in a japanese locale.  When I create 
the project in English it has an "Includes" section, but it doesn't when I 
create the same project in Japanese.  This is using the same workspace, so the 
settings should be identical.


This is the TVT tester's report on this problem:

OS : RHEL 3.0 
Build date:0714 
Language: JPN 

Problem Description: 

1. Create a SB project 
2. Select the SB project in the C/C++ Projects view. 
3. Right click and select Properties. 
4. Click "C/C++ Include Path and Symbols in the left panel. 

In the "Include path and Preprocessor Symbols" field, there is no "shown path" 
displayed. 
It seems that it couldn't find anything for "Includes" and "Preprocessor 
Sybmols". This function worked for English, but not for Japanese. 

Please investigate.
Comment 1 Jonathan Simpson CLA 2004-07-16 16:00:41 EDT
Created attachment 13385 [details]
screen capture
Comment 2 Jonathan Simpson CLA 2004-07-19 16:29:21 EDT
The French TVT tester is having the same problem.
Comment 3 Mathieu Lapensée CLA 2004-07-20 14:05:44 EDT
to be assigned to Vlad.
Comment 4 Victor Lenet CLA 2004-07-20 15:35:35 EDT
Please make sure that Preferences -> Workbench -> Build automatically is 
unchecked.

Then, when creating a new Standard Make project there should not be Includes 
item in C/C++ Projects view. It will appear only after the project has been 
built for the first time.

This behaviour has been verified on SLES 9, for both English and Japanese 
locales.
Comment 5 Jonathan Simpson CLA 2004-07-21 14:15:02 EDT
Following your instructions above, I still don't have an includes directory.  
Nor do I see any include paths under the Project Preferences page for automated 
discovery.  Does this mean that the automated discovery function is failing?

This is on RedHat Enterprised Linux 3.0, by the way.

Comment 6 Victor Lenet CLA 2004-07-21 14:36:43 EDT
Can you please verify if after a successful build of the project there are any 
include paths in Project -> Properties -> C/C++ Include Paths & Symbols 
property page, ->E <project name> ->E Discovered Paths ->E Includes.
(->E meens expand item)
Comment 7 Jonathan Simpson CLA 2004-07-21 15:01:28 EDT
Yep, thats what I'm saying.  There is nothing to expand under Discovered Paths.
Comment 8 Victor Lenet CLA 2004-07-21 17:33:21 EDT
Please try to rebuild the project from C/C++ Projects view -> Properties -> 
Rebuild Project.
Comment 9 Jonathan Simpson CLA 2004-07-21 18:28:35 EDT
I don't see a way to rebuild from Project View->Properties, but I did rebuild 
it by right-clicking on the project and selecting Rebuild Project.  
Unforunately I don't see any changes.
Comment 10 Victor Lenet CLA 2004-07-22 10:07:16 EDT
Can you please provide screen shots of Console view and Problems view after 
the rebuild.
Comment 11 Jonathan Simpson CLA 2004-07-22 11:15:11 EDT
Problems view is empty(no messages)

console view just shows make's output:

make -k all 
g++ -c -g -o main.o main.cpp 
g++ -c -g -o SB.o SB.cpp 
g++ -o SB.exe main.o SB.o


I'm also attaching a zip of an empty project created in a japanese locale with
build automatically turned on.  The .project and .cdtproject files are identical
to those created in an english locale.
Comment 12 Jonathan Simpson CLA 2004-07-22 11:15:50 EDT
Created attachment 13518 [details]
jpn created project
Comment 13 Jonathan Simpson CLA 2004-07-27 14:34:55 EDT
We need some resolution on this other than WORKSFORME.  Several TVT testers 
have experienced this problem and I'm unable to make it work in the problematic 
locales.  I can provide vnc access to one of our machines if you are not able 
to reproduce this problem.

Thanks.
Comment 14 Victor Lenet CLA 2004-07-27 14:48:57 EDT
That is a good idea. I would like to try it.
What are the problematic locales?
Comment 15 Jonathan Simpson CLA 2004-07-27 16:57:59 EDT
I will send you an email with the vnc and password info.  The problematic 
locales are Japan, France, Italy.
Comment 16 Victor Lenet CLA 2004-07-28 14:53:23 EDT
I have vreified that problem exists in French locale but not in the Italian. 
The reason is the GNU compiler's inconsistent locale support. 

There is an easy fix for the problem and it will be submitted soon.
Comment 17 Victor Lenet CLA 2004-07-29 14:00:53 EDT
Problem has been fixed by setting LANG variable to en_US.UTF-8 before running 
generate scanner info command. This will make gcc/g++ generate output in 
English, preserving any locale UTF-8 characters in include paths.

For the record, I tested original problem and it existed in French and Spanish 
locales, but not in Italian, German and Japanese locales. As said previously 
it is due to GNU's inconsistent internationalization support.
Comment 18 Cam-Thu Le CLA 2004-07-29 14:11:20 EDT
Did this make today's build?
Comment 19 Victor Lenet CLA 2004-07-29 14:21:21 EDT
Yes it is in build CDT 2.0.1 I200407291223.
Comment 20 Jonathan Simpson CLA 2004-07-30 16:30:37 EDT
closing