<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Menlo;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
code
{mso-style-priority:99;
font-family:"Courier New";}
samp
{mso-style-priority:99;
font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Verdana",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
/* List Definitions */
@list l0
{mso-list-id:426001062;
mso-list-template-ids:998396386;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:72.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l0:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:108.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level4
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:144.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level5
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:180.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:216.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level7
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:252.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level8
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:288.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l0:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:324.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Wingdings;}
@list l1
{mso-list-id:2106606294;
mso-list-type:hybrid;
mso-list-template-ids:2013660112 134807553 134807555 134807557 134807553 134807555 134807557 134807553 134807555 134807557;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level3
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level4
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level5
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level6
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
@list l1:level7
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Symbol;}
@list l1:level8
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:"Courier New";}
@list l1:level9
{mso-level-number-format:bullet;
mso-level-text:\F0A7;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-18.0pt;
font-family:Wingdings;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I had my fingers crossed the problem would only be with the specific variable in the previous error you reported, but actually I was
afraid of this. <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">The underlying issue is that there are (at least) two ways to define global variables in C:<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<ul style="margin-top:0cm" type="disc">
<li class="MsoListParagraph" style="color:#1F497D;margin-left:0cm;mso-list:l1 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;mso-fareast-language:EN-US">In a source file, with “extern” declarations in other source/header files<o:p></o:p></span></li><li class="MsoListParagraph" style="color:#1F497D;margin-left:0cm;mso-list:l1 level1 lfo1">
<span style="font-size:10.0pt;font-family:"Verdana",sans-serif;mso-fareast-language:EN-US">In a header file, which creates a copy of the definition in each source file the header is included in; the multiple copies of identical variables in global scope are
later merged by the linker.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">The former is the newer and recommended way, and the latter is older and AFAIK Unix-only.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">CWB uses both, but mostly the latter. In GCC, which one works depends on whether it is in “common” mode (both work) or “no-common”
mode (only the former method words). <o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">In older GCCs – including v 8 which is in use on Debian buster - “common” is the default. In GCC 10, “no-common” is default. Changelog
(</span><a href="https://gcc.gnu.org/gcc-10/changes.html">https://gcc.gnu.org/gcc-10/changes.html</a><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">) says<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<ul type="disc">
<li class="MsoNormal" style="color:black;mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-list:l0 level1 lfo2">
<span style="font-size:13.5pt;font-family:"Times New Roman",serif">GCC now defaults to </span><span style="font-size:10.0pt;font-family:"Courier New"">-fno-common</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif">. As a result, global
variable accesses are more efficient on various targets. In C, global variables with multiple tentative definitions now result in linker errors. With </span><span style="font-size:10.0pt;font-family:"Courier New"">-fcommon</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif"> such
definitions are silently merged during linking.<o:p></o:p></span></li></ul>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Fedora favours cutting-edge GCC whereas Debian is conservative. Thus why we have hit this problem first in Fedora.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">I strongly suspect, Maarten, that your Fedora distro uses gcc 10 or gcc 11.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">The wording of the gcc manuals over the ages is quite amusing, by the way, as it goes from assuming that
<i>of course</i> you want “common” to an equally strong assumption that only smelly legacy code would want “common”.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">=============================================================================<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">v2:<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Courier New";color:black">-fno-common</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt;background:white"><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">Allocate even uninitialized global variables in the bss section of the object file, rather than generating them as
common blocks. This has the effect that if the same variable is declared (without </span><span style="font-size:10.0pt;font-family:"Courier New";color:black">extern</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">) in two
different compilations, you will get an error when you link them. The only reason this might be useful is if you wish to verify that the program will work on other systems which always work this way.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">v8:<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Courier New";color:black">-fno-common</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt;background:white">
<a name="index-fno-common"></a><a name="index-tentative-definitions"></a><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">In C code, this option controls the placement of global variables defined without an initializer, known as <i>tentative
definitions</i> in the C standard. Tentative definitions are distinct from declarations of a variable with the </span><span style="font-size:10.0pt;font-family:"Courier New";color:black">extern</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black"> keyword,
which do not allocate storage.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt;background:white">
<span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">Unix C compilers have traditionally allocated storage for uninitialized global variables in a common block. This allows the linker to resolve all tentative definitions of the same
variable in different compilation units to the same object, or to a non-tentative definition. This is the behavior specified by </span><span style="font-size:13.5pt;font-family:"Courier New";color:black">-fcommon</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">,
and is the default for GCC on most targets. On the other hand, this behavior is not required by ISO C, and on some targets may carry a speed or code size penalty on variable references.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt;background:white">
<span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">The </span><span style="font-size:13.5pt;font-family:"Courier New";color:black">-fno-common</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black"> option
specifies that the compiler should instead place uninitialized global variables in the data section of the object file. This inhibits the merging of tentative definitions by the linker so you get a multiple-definition error if the same variable is defined
in more than one compilation unit. Compiling with </span><span style="font-size:13.5pt;font-family:"Courier New";color:black">-fno-common</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black"> is useful on targets for which it
provides better performance, or if you wish to verify that the program will work on other systems that always treat uninitialized variable definitions this way.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">v11:<o:p></o:p></span></p>
<p class="MsoNormal" style="background:white"><span style="font-size:10.0pt;font-family:"Courier New";color:black">-fcommon</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black"><o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt;background:white">
<a name="index-fcommon"></a><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">In C code, this option controls the placement of global variables defined without an initializer, known as <i>tentative definitions</i> in the C standard.
Tentative definitions are distinct from declarations of a variable with the </span><span style="font-size:10.0pt;font-family:"Courier New";color:black">extern</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black"> keyword, which
do not allocate storage.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt;background:white">
<span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">The default is </span><span style="font-size:13.5pt;font-family:"Courier New";color:black">-fno-common</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">,
which specifies that the compiler places uninitialized global variables in the BSS section of the object file. This inhibits the merging of tentative definitions by the linker so you get a multiple-definition error if the same variable is accidentally defined
in more than one compilation unit.<o:p></o:p></span></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;margin-left:36.0pt;background:white">
<span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black">The </span><span style="font-size:13.5pt;font-family:"Courier New";color:black">-fcommon</span><span style="font-size:13.5pt;font-family:"Times New Roman",serif;color:black"> places
uninitialized global variables in a common block. This allows the linker to resolve all tentative definitions of the same variable in different compilation units to the same object, or to a non-tentative definition. This behavior is inconsistent with C++,
and on many targets implies a speed and code size penalty on global variable references. It is mainly useful to enable legacy code to link without errors.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">====================================================================<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Ah well.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">The question is what to do. Solution 1. Add
<b>-fcommon </b>to all GCC calls in the makefile. Solution 2. Bite the bullet and make each global variable be defined in one place only with an extern declaration in a header file.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">STEFAN – any thoughts? My instinct is the latter – it will be easy enough for me to switch to
<b>-fno-common</b> on Debian and allow the resulting build errors to find all the variables in question!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">best<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Andrew.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Verdana",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US">From:</span></b><span lang="EN-US"> cwb-bounces@sslmit.unibo.it <cwb-bounces@sslmit.unibo.it>
<b>On Behalf Of </b>Maarten Janssen<br>
<b>Sent:</b> 05 May 2020 09:19<br>
<b>To:</b> CWBdev Mailing List <cwb@sslmit.unibo.it><br>
<b>Subject:</b> Re: [CWB] Segmentation fault<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">The fedora issue changed - but now actually throws a lot more error messages, I guess because the libraries that are being loaded are partially overlapping, this should be the crucial bit, but it then goes on for various pages with duplications:<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><span style="font-family:Menlo">gcc -O2 -Wall -fPIC -m64 -DUSE_TERMCAP -DUSE_READLINE -DCWB_REGISTRY_DEFAULT_PATH=\""/usr/local/cwb-3.4.22/share/cwb/registry"\" -DCOMPILE_DATE=\""Tue 05 May 2020 04:16:03 AM EDT"\" -DCWB_VERSION=\"3.4.22\"
-I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -o cqp llquery.o cqp.o symtab.o eval.o tree.o options.o corpmanag.o regex2dfa.o output.o ranges.o builtins.o groups.o targets.o matchlist.o concordance.o parse_actions.o attlist.o context_descriptor.o
print-modes.o ascii-print.o sgml-print.o html-print.o latex-print.o variables.o print_align.o macro.o hash.o table.o parser.tab.o lex.yy.o dummy_auth.o /home/mjanssen/cwb/cqp/../cl/libcl.a -lm -lpcre -lglib-2.0 -lreadline -lhistory -lncurses -ltinfo <o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Menlo">/usr/bin/ld: cqp.o:(.bss+0x2acaa8): multiple definition of `signal_handler_is_installed'; llquery.o:(.bss+0x2ac268): first defined here<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Menlo">/usr/bin/ld: cqp.o:(.bss+0x2acaac): multiple definition of `EvaluationIsRunning'; llquery.o:(.bss+0x2ac26c): first defined here<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Menlo">/usr/bin/ld: cqp.o:(.bss+0x2ac938): multiple definition of `silent'; llquery.o:(.bss+0x2ac0f8): first defined here<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Menlo">/usr/bin/ld: cqp.o:(.bss+0x2acab0): multiple definition of `exit_cqp'; llquery.o:(.bss+0x2ac270): first defined here<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Menlo">/usr/bin/ld: cqp.o:(.bss+0x2ac8f8): multiple definition of `child_process'; llquery.o:(.bss+0x2ac0b8): first defined here<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span style="font-family:Menlo">/usr/bin/ld: cqp.o:(.bss+0x2acaa0): multiple definition of `current_corpus'; llquery.o:(.bss+0x2ac260): first defined here<o:p></o:p></span></p>
</div>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>