public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* CMake: parse error in file FindTclsh.cmake
@ 2019-08-21 11:55 Sébastien Helleu
  2019-08-21 17:23 ` Marco Atzeri
  0 siblings, 1 reply; 2+ messages in thread
From: Sébastien Helleu @ 2019-08-21 11:55 UTC (permalink / raw)
  To: cygwin

Hi,

In the version 3.14.5 of CMake, I have issues to detect Tcl (I'm author of
WeeChat, which uses TCL language as one of the supported language scripts).

The file seems to have a comment (as rst) on top, but it is not properly
closed.

I have the following error:

=====
CMake Error at /usr/share/cmake-3.14.5/Modules/FindTclsh.cmake:93:
  Parse error.  Expected a command name, got unterminated bracket with text
  ".rst:

  FindTclsh

  ---------



  Find tclsh

(...)
  ".
Call Stack (most recent call first):
  cmake/FindTCL.cmake:59 (include)
  src/plugins/CMakeLists.txt:121 (find_package)


-- Configuring incomplete, errors occurred!
=====

The content of /usr/share/cmake-3.14.5/Modules/FindTclsh.cmake starts with:

=====
# Distributed under the OSI-approved BSD 3-Clause License.  See accompanying
# file Copyright.txt or https://cmake.org/licensing for details.

#[=======================================================================[.rst:
FindTclsh
---------

Find tclsh

This module finds if TCL is installed and determines where the include
files and libraries are.  It also determines what the name of the
library is.  This code sets the following variables:

::

  TCLSH_FOUND = TRUE if tclsh has been found
  TCL_TCLSH = the path to the tclsh executable


get_filename_component(TK_WISH_PATH "${TK_WISH}" PATH)
get_filename_component(TK_WISH_PATH_PARENT "${TK_WISH_PATH}" PATH)
string(REGEX REPLACE
  "^.*wish([0-9]\\.*[0-9]).*$" "\\1" TK_WISH_VERSION "${TK_WISH}")
(...)
=====

So for me this line is missing before the first CMake command:

#]=======================================================================]

Please let me know if I have report this bug on a tracker or send a patch.

Thanks.

-- 
Sébastien Helleu

web: weechat.org / flashtux.org
irc: FlashCode @ irc.freenode.net

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: CMake: parse error in file FindTclsh.cmake
  2019-08-21 11:55 CMake: parse error in file FindTclsh.cmake Sébastien Helleu
@ 2019-08-21 17:23 ` Marco Atzeri
  0 siblings, 0 replies; 2+ messages in thread
From: Marco Atzeri @ 2019-08-21 17:23 UTC (permalink / raw)
  To: cygwin

Am 21.08.2019 um 09:12 schrieb Sébastien Helleu:
> Hi,
> 
> In the version 3.14.5 of CMake, I have issues to detect Tcl (I'm author of
> WeeChat, which uses TCL language as one of the supported language scripts).
> 
> The file seems to have a comment (as rst) on top, but it is not properly
> closed.
> 


> So for me this line is missing before the first CMake command:
> 
> #]=======================================================================]
> 
> Please let me know if I have report this bug on a tracker or send a patch.
> 
> Thanks.
> 

it was already mentioned
https://cygwin.com/ml/cygwin/2019-07/msg00057.html

I had not yet time to implement the patch


Thanks
Marco


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-08-21 11:55 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-21 11:55 CMake: parse error in file FindTclsh.cmake Sébastien Helleu
2019-08-21 17:23 ` Marco Atzeri

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).