<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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></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-AU" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi Yannick,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yes, we patched the latest (as of around a month ago) versions to work on CentOS 5. Sorry, I neglected to mention that this is for UST only, not kernel tracing,
hence my not saying anything about the modules!<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If the changes aren’t going to go upstream into the git repositories, I imagine there is more chance of the CentOS 5 support becoming broken – something could
be committed upstream that requires further patching, or conflicts with the patches. In this case, then, I don’t think EPEL packages would help us much, and quite possibly nobody else is interested in CentOS 5 :) Also, we needed to backport some lttng-ust
commits from master to get support for dynamic trace providers to work, so we’re more interested in seeing future releases include the changes than seeing a patched version of the current release, and therefore I don’t think there would be any value in us
moving to an EPEL package for the same version of LTTng that we’re already using.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">I can certainly provide the patches to you anyway, but I’m not so keen to spend time improving them if they’re not going upstream, e.g. one thing I think needs
to be investigated is whether the kernel versions provided by CentOS 5 include the system calls that we had to add wrappers for; I haven’t paid any attention to what kernel version I’m using, I’m not sure if it is a standard CentOS 5 one.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Thanks!<br>
David<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt">
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span lang="EN-US" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Brosseau, Yannick [mailto:yannick.brosseau@gmail.com]
<br>
<b>Sent:</b> Friday, 17 May 2013 12:44 AM<br>
<b>To:</b> David OShea<br>
<b>Cc:</b> lttng-dev@lists.lttng.org<br>
<b>Subject:</b> Re: [lttng-dev] Patches to enable building on CentOS 5.x (glibc 2.5)<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">Hi,<br>
<br>
So you made it work with CentOS 5?<o:p></o:p></p>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt">I don't know if we want it upstream, but I could maybe use them to build a package for EPEL5.<o:p></o:p></p>
</div>
<p class="MsoNormal">Yannick<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Wed, May 15, 2013 at 7:38 AM, David OShea <<a href="mailto:David.OShea@quantum.com" target="_blank">David.OShea@quantum.com</a>> wrote:<o:p></o:p></p>
<p class="MsoNormal">Hi,<br>
<br>
Would contributions of patches to enable lttng-tools and lttng-ust to build with glibc 2.5 (as is shipped with CentOS 5.x) and to enable lttng-gen-tp to run with Python 2.4 (as shipped on CentOS 5.x) be accepted?<br>
<br>
What is missing from glibc 2.5 is:<br>
<br>
- a system call wrapper for sched_getcpu()<br>
- a system call wrapper for sync_file_range()<br>
- htobe32() and other similar endian conversion functions<br>
<br>
babeltrace and userspace-rcu did not require patching.<br>
<br>
Thanks in advance,<br>
David<br>
<br>
P.S. If you see this, thanks for all your recent replies, Mathieu, I will try to get back to you soon!<br>
<br>
----------------------------------------------------------------------<br>
The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to
have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is
not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.<br>
<br>
_______________________________________________<br>
lttng-dev mailing list<br>
<a href="mailto:lttng-dev@lists.lttng.org">lttng-dev@lists.lttng.org</a><br>
<a href="http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev" target="_blank">http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev</a><o:p></o:p></p>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<br>
-- <br>
Yannick Brosseau<br>
<a href="http://yannickbrosseau.com" target="_blank">yannickbrosseau.com</a> <o:p>
</o:p></p>
</div>
</div>
</div>
</body>
</html>