This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 186565 - Misleading error message
Summary: Misleading error message
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Toolchain (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Alexander Simon
URL:
Keywords: USABILITY
: 186566 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-05-23 16:42 UTC by Egor Ushakov
Modified: 2012-05-16 08:10 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
proposed patch (24.12 KB, patch)
2011-09-22 15:27 UTC, Alexander Simon 		Details | Diff
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Egor Ushakov 2010-05-23 16:42:23 UTC 
I tried to change C comiler for the existing toolchain:
- selected addr2line.exe from another directory - fine
- selected gmake.exe from another directory - got "Only compilers within base dir allowed"
It looks like I can select a binary from the different folder but it should be somehow special, it is unclear how...
Also I can specify any existing file if I edit compiler field in the toochain. It means that this check is done only for filechooser result. This is inconsistent.
Comment 1 Egor Ushakov 2010-05-24 09:35:26 UTC 
*** Bug 186566 has been marked as a duplicate of this bug. ***
Comment 2 Egor Ushakov 2010-05-24 09:37:57 UTC 
Having tools from folders other than toolchain bin does not make sense for managed projects. Anyway tool from bin will be used, not the tool user specified.
In this case it is strange to have the ability to edit tools paths!
That does not affect anything (for managed projects).
Comment 3 Egor Ushakov 2010-05-24 10:22:01 UTC 
more of that if tool name is somehow special build will fail as soon as this tool is not in path or toolchain bin folder, e.g.:
Gnu toolchain from /usr/bin
c++ compiler: /opt/csw/gcc4/bin/i386-pc-solaris2.10-g++
Any build will fail because i386-pc-solaris2.10-g++ is not in path or /usr/bin
Comment 4 Egor Ushakov 2010-05-24 11:24:46 UTC 
workaround is to change project properties/C++ comiler/tool by hand.
User can enter full path there.
Comment 5 Alexander Pepin 2010-05-24 12:08:26 UTC 
Not a showstopper for 6.9.
Should be definitely fixed in the next release.
Comment 6 Thomas Preisler 2010-05-24 20:55:10 UTC 
Build is supposed to add compiler base to a users paths. If it doesn't, then this is the problem (and a regression). Compilers (cc, CC, gcc, g++, asm, ...) will be takes from base and that is why the toolchain GUI correctly disallow you to mix compilers from different bases. Make is not part of the toolchain (in this sense) so you can specify any make you like and it should use that make even it is not in the same base. It doesn't matter for make. It all has to do with certain standards of how makefiles are written and how compilers (not make it self) is choosen from these makefiles.
Comment 7 Alexander Simon 2011-09-22 15:27:30 UTC 
Created attachment 111054 [details]
proposed patch
Comment 8 Alexander Simon 2012-05-16 08:10:16 UTC 
fixed, change set:
http://hg.netbeans.org/cnd-main/rev/056b5756175e
- message was removed.