You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues-all@impala.apache.org by "Laszlo Gaal (Jira)" <ji...@apache.org> on 2022/06/28 19:16:00 UTC

[jira] [Commented] (IMPALA-11403) CMake warning triggered by a sed regexp in common/thrift

|  ![](cid:jira-generated-image-avatar-41501069-fda3-49ca-b740-2e4585a39c1e) |
[Laszlo
Gaal](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=laszlog)
**commented** on [![Bug](cid:jira-generated-image-
avatar-494c6100-3dcb-419d-9db4-38d8363eaccb)
IMPALA-11403](https://issues.apache.org/jira/browse/IMPALA-11403)  
---|---  
|  
---  
|  [Re: CMake warning triggered by a sed regexp in
common/thrift](https://issues.apache.org/jira/browse/IMPALA-11403)  
---  
|

`sed`, `bash` and `CMake` all use the backslash as an escape character. In
this case a `sed` command line is written into a CMake recipe, to be emitted
into the generated Makefile by CMake, so CMake already attempts to process the
escape sequences.  
Observing the generated output shows that while CMake detects this syntax as
suspicious,it still does "the right thing" and passes on the `sed` command
line unchanged, preserving the `sed` syntax.  
Doubling the backslashes should allow the backslash characters to pass through
to `sed` unharmed while satisfying CMake's syntax rules as well.  
  
---  
|  |  [ ![Add Comment](cid:jira-generated-image-static-comment-
icon-d79a90e6-1db8-40af-aeb4-8af1ccc352d7)
](https://issues.apache.org/jira/browse/IMPALA-11403#add-comment "Add
Comment") |  [Add
Comment](https://issues.apache.org/jira/browse/IMPALA-11403#add-comment "Add
Comment")  
---|---  
  
|  This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9) |  |
![Atlassian logo](https://issues.apache.org/jira/images/mail/atlassian-email-
logo.png)  
---