Re: [Boost-bugs] [Boost C++ Libraries] #4667: boost-build: configuration of toolset gcc does not enforce requested versions and accepts non-existing commands

Subject: Re: [Boost-bugs] [Boost C++ Libraries] #4667: boost-build: configuration of toolset gcc does not enforce requested versions and accepts non-existing commands
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2010-09-27 17:27:53


#4667: boost-build: configuration of toolset gcc does not enforce requested
versions and accepts non-existing commands
--------------------------------------+-------------------------------------
  Reporter: mhassert@… | Owner: vladimir_prus
      Type: Patches | Status: closed
 Milestone: To Be Determined | Component: build
   Version: Boost Development Trunk | Severity: Problem
Resolution: fixed | Keywords: bjam boost build boost-build gcc toolset version compiler
--------------------------------------+-------------------------------------

Comment (by mhassert@…):

 Hi Volodya,

 thanks for accepting the patch and fixing the version comparison. It was
 indeed too strict.

 Now that I looked at the code again, I see another problem:

 At the moment, specifying a command without a path and without ".exe"
 suffix does not work on Windows, because check-tool-aux() in common.jam
 auto-appends ".exe" only when the given command features a path.
 Omitting only one of path or .exe should to work. (I can't test right
 now.)

 This behavior of check-tool-aux() seems kind of strange to me.

 Passing the user specified command as the second argument in line 73 would
 work in case of omitted path but won't work for commands with a path. At
 least as far as I understand the rule find-tool().

 Moritz

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/4667#comment:6>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.

This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:04 UTC