<?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 for The Intraweb Home of Andy White</title>
	<atom:link href="http://acdub.com/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://acdub.com/blog</link>
	<description>Your personal guide to the wide, wide world of webs</description>
	<pubDate>Thu, 11 Mar 2010 03:16:20 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on The quest for MacOSX 10.5, Apache, Python, Django, and mod_wsgi by Andy</title>
		<link>http://acdub.com/blog/2009/10/02/the-quest-for-macosx-105-apache-python-django-and-mod_wsgi/comment-page-1/#comment-5586</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Fri, 02 Oct 2009 22:57:52 +0000</pubDate>
		<guid isPermaLink="false">http://acdub.com/blog/?p=170#comment-5586</guid>
		<description>Hey Graham, thanks for your comment!  I'm fairly new to Apache, modules, and dealing with 64-bit on Mac, among other things, so this was a good learning experience.  I did read through that wiki for wsgi on MacOSX, and the problem was not with mod_wsgi.so.  I verified that the Makefile was building mod_wsgi with the full "fat" set of architectures.  I believe the problem I was seeing was that the Python library was only built in 32-bit mode.  I figured the solution to this problem would be to either try to build the Python library with all archs, or thin Apache down to 32-bits.  I was hoping to not have to thin Apache down, but that seems to be the easiest solution.  What are your thoughts?</description>
		<content:encoded><![CDATA[<p>Hey Graham, thanks for your comment!  I&#8217;m fairly new to Apache, modules, and dealing with 64-bit on Mac, among other things, so this was a good learning experience.  I did read through that wiki for wsgi on MacOSX, and the problem was not with mod_wsgi.so.  I verified that the Makefile was building mod_wsgi with the full &#8220;fat&#8221; set of architectures.  I believe the problem I was seeing was that the Python library was only built in 32-bit mode.  I figured the solution to this problem would be to either try to build the Python library with all archs, or thin Apache down to 32-bits.  I was hoping to not have to thin Apache down, but that seems to be the easiest solution.  What are your thoughts?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The quest for MacOSX 10.5, Apache, Python, Django, and mod_wsgi by Graham Dumpleton</title>
		<link>http://acdub.com/blog/2009/10/02/the-quest-for-macosx-105-apache-python-django-and-mod_wsgi/comment-page-1/#comment-5585</link>
		<dc:creator>Graham Dumpleton</dc:creator>
		<pubDate>Fri, 02 Oct 2009 09:58:34 +0000</pubDate>
		<guid isPermaLink="false">http://acdub.com/blog/?p=170#comment-5585</guid>
		<description>Rather than search through all those blogs, you could have just read:

http://code.google.com/p/modwsgi/wiki/InstallationOnMacOSX

It mentions how to build fully fat framework from source code as well as mention tricks for thinning Apache etc if absolutely needed.

The particular error you are getting also possibly not entirely related to that anyway and may be because wrong version of Python framework being picked up at run time. You need to check with 'otool' what mod_wsgi.so thinks it will find. If it isn't right, you need to change how mod_wsgi is linked against Python framework.

Easiest thing to do is make sure using mod_wsgi 2.6 and if standard configure doesn't work, use the '--disable-framework' option to configure to force linking via old style library reference. Don't know why but different Python installations and operating system versions appear not to be consistent as to what works.

Also read:

http://code.google.com/p/modwsgi/wiki/ChangesInVersion0206

as it mentions the linking issues that may be causing this and that configure option.

BTW, asking for help on the mod_wsgi list on Google Groups is always a good idea.</description>
		<content:encoded><![CDATA[<p>Rather than search through all those blogs, you could have just read:</p>
<p><a href="http://code.google.com/p/modwsgi/wiki/InstallationOnMacOSX" rel="nofollow">http://code.google.com/p/modwsgi/wiki/InstallationOnMacOSX</a></p>
<p>It mentions how to build fully fat framework from source code as well as mention tricks for thinning Apache etc if absolutely needed.</p>
<p>The particular error you are getting also possibly not entirely related to that anyway and may be because wrong version of Python framework being picked up at run time. You need to check with &#8216;otool&#8217; what mod_wsgi.so thinks it will find. If it isn&#8217;t right, you need to change how mod_wsgi is linked against Python framework.</p>
<p>Easiest thing to do is make sure using mod_wsgi 2.6 and if standard configure doesn&#8217;t work, use the &#8216;&#8211;disable-framework&#8217; option to configure to force linking via old style library reference. Don&#8217;t know why but different Python installations and operating system versions appear not to be consistent as to what works.</p>
<p>Also read:</p>
<p><a href="http://code.google.com/p/modwsgi/wiki/ChangesInVersion0206" rel="nofollow">http://code.google.com/p/modwsgi/wiki/ChangesInVersion0206</a></p>
<p>as it mentions the linking issues that may be causing this and that configure option.</p>
<p>BTW, asking for help on the mod_wsgi list on Google Groups is always a good idea.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on EMG Pickup Installation in a Gibson Explorer (part 5) by Scott hall</title>
		<link>http://acdub.com/blog/2007/11/20/emg-pickup-installation-in-a-gibson-explorer-part-5/comment-page-1/#comment-5338</link>
		<dc:creator>Scott hall</dc:creator>
		<pubDate>Thu, 24 Sep 2009 14:22:27 +0000</pubDate>
		<guid isPermaLink="false">http://acdub.com/blog/?p=10#comment-5338</guid>
		<description>Hey you've had the closest answer i've been looking for... I have some EMG bass pickups, i don't use em because of the battery, so, i was thinking about how to power them using an external power source. I'm ok with electronics but not just great but i have a friend that really good and could help me but i ran across your blog. Did you ever find a for sure way to run power to the pickups without noise. Any info would be GREATLY appreciated.</description>
		<content:encoded><![CDATA[<p>Hey you&#8217;ve had the closest answer i&#8217;ve been looking for&#8230; I have some EMG bass pickups, i don&#8217;t use em because of the battery, so, i was thinking about how to power them using an external power source. I&#8217;m ok with electronics but not just great but i have a friend that really good and could help me but i ran across your blog. Did you ever find a for sure way to run power to the pickups without noise. Any info would be GREATLY appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on iPhone 3GS not receiving incoming calls by LnddMiles</title>
		<link>http://acdub.com/blog/2009/06/28/iphone-3gs-not-receiving-incoming-calls/comment-page-1/#comment-3395</link>
		<dc:creator>LnddMiles</dc:creator>
		<pubDate>Wed, 22 Jul 2009 00:58:33 +0000</pubDate>
		<guid isPermaLink="false">http://acdub.com/blog/?p=159#comment-3395</guid>
		<description>The best information i have found exactly here. Keep going Thank you</description>
		<content:encoded><![CDATA[<p>The best information i have found exactly here. Keep going Thank you</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Kayak log:  Golden 2009-06-23 by Mary</title>
		<link>http://acdub.com/blog/2009/06/23/kayak-log-golden-2009-06-23/comment-page-1/#comment-3294</link>
		<dc:creator>Mary</dc:creator>
		<pubDate>Wed, 24 Jun 2009 06:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://acdub.com/blog/?p=146#comment-3294</guid>
		<description>Pretty good post. I just came by your site and wanted to say 
that I've really enjoyed browsing your blog posts. Anyway 
I'll be subscribing to your blog and I hope you write again soon!</description>
		<content:encoded><![CDATA[<p>Pretty good post. I just came by your site and wanted to say<br />
that I&#8217;ve really enjoyed browsing your blog posts. Anyway<br />
I&#8217;ll be subscribing to your blog and I hope you write again soon!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
