<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: MySQL in Gales 2: bundles of joy</title>
	<atom:link href="http://jfxpt.com/2021/mysql-in-gales-2-bundles-of-joy/feed/" rel="self" type="application/rss+xml" />
	<link>http://jfxpt.com/2021/mysql-in-gales-2-bundles-of-joy/</link>
	<description>The search for invariants</description>
	<pubDate>Sun, 19 Apr 2026 02:10:42 +0000</pubDate>
	<generator>http://polimedia.us</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: #jwrd Logs for Nov 2021 &#171; Fixpoint</title>
		<link>http://jfxpt.com/2021/mysql-in-gales-2-bundles-of-joy/#comment-1396</link>
		<dc:creator>#jwrd Logs for Nov 2021 &#171; Fixpoint</dc:creator>
		<pubDate>Wed, 10 Nov 2021 00:07:49 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=157#comment-1396</guid>
		<description>[...]  [...]</description>
		<content:encoded><![CDATA[<p>[...]  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2021/mysql-in-gales-2-bundles-of-joy/#comment-1394</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Tue, 09 Nov 2021 20:28:01 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=157#comment-1394</guid>
		<description>&lt;blockquote&gt;pdksh quirk perhaps: "set - x y z" leaves the "-" as $1 (and there's no reason to have it here).&lt;/blockquote&gt;

Ftr, there is at least a theoretical reason and the better fix would have been replacing the single with a double dash.</description>
		<content:encoded><![CDATA[<blockquote><p>pdksh quirk perhaps: "set - x y z" leaves the "-" as $1 (and there's no reason to have it here).</p></blockquote>
<p>Ftr, there is at least a theoretical reason and the better fix would have been replacing the single with a double dash.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jacob Welsh</title>
		<link>http://jfxpt.com/2021/mysql-in-gales-2-bundles-of-joy/#comment-1393</link>
		<dc:creator>Jacob Welsh</dc:creator>
		<pubDate>Tue, 09 Nov 2021 20:17:13 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=157#comment-1393</guid>
		<description>&lt;blockquote&gt;That "heh" has me hanging off a cliff.&lt;/blockquote&gt;

Keep holding on!

Actually, there was already some libedit drama at this stage of the tale, just getting it to build, that I missed. First it had some shell script generated code thing that misfired; here was my patch from the time in full:

&lt;blockquote&gt;&lt;pre style="white-space:pre-wrap"&gt;
pdksh quirk perhaps: "set - x y z" leaves the "-" as $1 (and there's no reason to have it here).

Caused headers to be generated with broken, colliding ifdef guards.

 -jfw

--- a/cmd-line-utils/libedit/makelist.sh
+++ b/cmd-line-utils/libedit/makelist.sh
@@ -62,7 +62,7 @@
     ;;
     
 -h)
-    set - `echo $FILES &#124; sed -e 's/\\./_/g'`
+    set `echo $FILES &#124; sed -e 's/\\./_/g'`
     hdr="_h_`basename $1`"
     cat $FILES &#124; $AWK '
 	BEGIN {
&lt;/pre&gt;&lt;/blockquote&gt;

Then in libedit/chartype.h there was some ifdef madness for unicode detection that deliberately bombed because it didn't know about musl, the fix being to delete it on the assumption that indeed musl uses unicode for its "wide characters" rather than "some other funky encoding"; the offending part:

&lt;blockquote&gt;&lt;pre style="white-space:pre-wrap"&gt;
/* Ideally we should also test the value of the define to see if it
 * supports non-BMP code points without requiring UTF-16, but nothing
 * seems to actually advertise this properly, despite Unicode 3.1 having
 * been around since 2001... */

/* XXXMYSQL : Added FreeBSD &#38; AIX to bypass this check.
  TODO : Verify if FreeBSD &#38; AIX stores ISO 10646 in wchar_t. */
#if !defined(__NetBSD__) &#38;&#38; !defined(__sun) \
  &#38;&#38; !(defined(__APPLE__) &#38;&#38; defined(__MACH__)) \
  &#38;&#38; !defined(__FreeBSD__) &#38;&#38; !defined(_AIX)
#ifndef __STDC_ISO_10646__
/* In many places it is assumed that the first 127 code points are ASCII
 * compatible, so ensure wchar_t indeed does ISO 10646 and not some other
 * funky encoding that could break us in weird and wonderful ways. */
	#error wchar_t must store ISO 10646 characters
#endif
#endif
&lt;/pre&gt;&lt;/blockquote&gt;</description>
		<content:encoded><![CDATA[<blockquote><p>That "heh" has me hanging off a cliff.</p></blockquote>
<p>Keep holding on!</p>
<p>Actually, there was already some libedit drama at this stage of the tale, just getting it to build, that I missed. First it had some shell script generated code thing that misfired; here was my patch from the time in full:</p>
<blockquote><pre style="white-space:pre-wrap">
pdksh quirk perhaps: "set - x y z" leaves the "-" as $1 (and there's no reason to have it here).

Caused headers to be generated with broken, colliding ifdef guards.

 -jfw

--- a/cmd-line-utils/libedit/makelist.sh
+++ b/cmd-line-utils/libedit/makelist.sh
@@ -62,7 +62,7 @@
     ;;

 -h)
-    set - `echo $FILES | sed -e 's/\\./_/g'`
+    set `echo $FILES | sed -e 's/\\./_/g'`
     hdr="_h_`basename $1`"
     cat $FILES | $AWK '
 	BEGIN {
</pre>
</blockquote>
<p>Then in libedit/chartype.h there was some ifdef madness for unicode detection that deliberately bombed because it didn't know about musl, the fix being to delete it on the assumption that indeed musl uses unicode for its "wide characters" rather than "some other funky encoding"; the offending part:</p>
<blockquote><pre style="white-space:pre-wrap">
/* Ideally we should also test the value of the define to see if it
 * supports non-BMP code points without requiring UTF-16, but nothing
 * seems to actually advertise this properly, despite Unicode 3.1 having
 * been around since 2001... */

/* XXXMYSQL : Added FreeBSD &amp; AIX to bypass this check.
  TODO : Verify if FreeBSD &amp; AIX stores ISO 10646 in wchar_t. */
#if !defined(__NetBSD__) &amp;&amp; !defined(__sun) \
  &amp;&amp; !(defined(__APPLE__) &amp;&amp; defined(__MACH__)) \
  &amp;&amp; !defined(__FreeBSD__) &amp;&amp; !defined(_AIX)
#ifndef __STDC_ISO_10646__
/* In many places it is assumed that the first 127 code points are ASCII
 * compatible, so ensure wchar_t indeed does ISO 10646 and not some other
 * funky encoding that could break us in weird and wonderful ways. */
	#error wchar_t must store ISO 10646 characters
#endif
#endif
</pre>
</blockquote>
]]></content:encoded>
	</item>
	<item>
		<title>By: Robinson Dorion</title>
		<link>http://jfxpt.com/2021/mysql-in-gales-2-bundles-of-joy/#comment-1391</link>
		<dc:creator>Robinson Dorion</dc:creator>
		<pubDate>Tue, 09 Nov 2021 17:35:16 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=157#comment-1391</guid>
		<description>&lt;blockquote&gt;
The sarcasm will be contained to the title for this one.
&lt;/blockquote&gt;

Cooler read, but just as informative.

&lt;blockquote&gt;
Having bigger fish to fry, I took a note and let it proceed with the bundled one, figuring that would at least be the one most tested and likely to work (heh).
&lt;/blockquote&gt;

Alright. That "heh" has me hanging off a cliff.

&lt;blockquote&gt;
Memcached being a whole separate thing that we're not currently interested in - nor do I anticipate that we'd likely ever be - I happily struck it from the CMakeLists and scripted the full removal of its code just to be sure. This has turned out fine so far.
&lt;/blockquote&gt;

Alright, sounds fine.

&lt;blockquote&gt;
Thus all that was needed was to change the offending line to check for 2 instead of 1. I suppose deleting the check altogether would have worked just as well, but taken things out of "sed one-liner" territory and I wasn't inclined to do some more thorough patch at such an early stage.
&lt;/blockquote&gt;

&lt;blockquote&gt;
So at the moment I can't use my system zlib; I may end up updating it to the latest once I can take a proper look at it. Since bumping the MySQL version to 5.6.45 at least I won't have the known-bad bundled compressBound() in play.
&lt;/blockquote&gt;

Alright for now, like you said, bigger fish to fry.</description>
		<content:encoded><![CDATA[<blockquote><p>
The sarcasm will be contained to the title for this one.
</p></blockquote>
<p>Cooler read, but just as informative.</p>
<blockquote><p>
Having bigger fish to fry, I took a note and let it proceed with the bundled one, figuring that would at least be the one most tested and likely to work (heh).
</p></blockquote>
<p>Alright. That "heh" has me hanging off a cliff.</p>
<blockquote><p>
Memcached being a whole separate thing that we're not currently interested in - nor do I anticipate that we'd likely ever be - I happily struck it from the CMakeLists and scripted the full removal of its code just to be sure. This has turned out fine so far.
</p></blockquote>
<p>Alright, sounds fine.</p>
<blockquote><p>
Thus all that was needed was to change the offending line to check for 2 instead of 1. I suppose deleting the check altogether would have worked just as well, but taken things out of "sed one-liner" territory and I wasn't inclined to do some more thorough patch at such an early stage.
</p></blockquote>
<blockquote><p>
So at the moment I can't use my system zlib; I may end up updating it to the latest once I can take a proper look at it. Since bumping the MySQL version to 5.6.45 at least I won't have the known-bad bundled compressBound() in play.
</p></blockquote>
<p>Alright for now, like you said, bigger fish to fry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MySQL in Gales 3: debug, rebug &#171; Fixpoint</title>
		<link>http://jfxpt.com/2021/mysql-in-gales-2-bundles-of-joy/#comment-1366</link>
		<dc:creator>MySQL in Gales 3: debug, rebug &#171; Fixpoint</dc:creator>
		<pubDate>Sun, 07 Nov 2021 08:38:14 +0000</pubDate>
		<guid isPermaLink="false">http://fixpoint.welshcomputing.com/?p=157#comment-1366</guid>
		<description>[...] Continuing from where the advanced quality assurance process of "start it and see if it blows up" had returned in the affirmative, it was clearly time to pay an old debt and get a proper debugger working on Gales. [...]</description>
		<content:encoded><![CDATA[<p>[...] Continuing from where the advanced quality assurance process of "start it and see if it blows up" had returned in the affirmative, it was clearly time to pay an old debt and get a proper debugger working on Gales. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
