[translate] [Fwd: web/xml/faq faq.en.xml,1.51,1.52]

-------- Original Message --------

Update of /cvsroot/fink/web/xml/faq
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv19065

Modified Files:
	faq.en.xml
Log Message:
updates:

gettext-dev vs libgettext3-dev

rebuild python after OS upgrade


Index: faq.en.xml
===================================================================
RCS file: /cvsroot/fink/web/xml/faq/faq.en.xml,v
retrieving revision 1.51
retrieving revision 1.52
diff -u -d -r1.51 -r1.52
--- faq.en.xml	22 Jun 2005 13:36:11 -0000	1.51
+++ faq.en.xml	8 Jul 2005 00:50:06 -0000	1.52
@@ -1394,6 +1394,35 @@
            <em>Note:  </em>Fink is deliberately set up such that all 
official binaries are identical regardless of what machine they are 
built on, so things like G5 optimization won't happen with an official 
package.  If you want them, you'll have to do it yourself.</p>
        </answer>
      </faqentry>
+    <faqentry name="gettext">
+      <question>
+        <p>Whenever I try to build from source, Fink keeps waffling 
between <code>gettext-dev</code> and <code>libgettext3-dev</code>.</p>
+      </question>
+      <answer>
+        <p>Some packages that need <code>gettext</code> headers to 
build have been updated to use <code>libgettext3-dev</code> and some 
still use <code>gettext-dev</code>.  Consequently, Fink may try to 
switch to whichever one isn't currently installed in order to satisfy a 
build dependency for some package that you're trying to update.  In 
addition, the <code>fink </code>tool treats <code>gettext-dev</code> as 
essential, and will install it any time you selfupdate.</p>
+        <p>Similar behavior can happen for other pairs of packages, 
too. </p>
+        <p>Unfortunately, due to limitations in the build-dependency 
engine, you may find that your build bombs because you've swapped in one 
of these but some later package in your build chain wants the other one. 
  You can proceed by repeating your update command again.</p>
+        <p>A permanent fix should hopefully be available in 
<code>fink-0.2.5</code>.</p>
+      </answer>
+    </faqentry>
+    <faqentry name="python-mods">
+      <question>
+        <p>I get errors involving <code>MACOSX_DEPLOYMENT_TARGET 
</code>when I try to build a Python module.</p>
+      </question>
+      <answer>
+        <p>For errors that look like the following:</p>
+        <codeblock>running build
+running build_ext
+Traceback (most recent call last):
+  File "setup_socket_ssl.py", line 21, in ?
+    depends = ['socketmodule.h'] )
+  File 
"/sw/src/root-python24-2.4.1-1/sw/lib/python2.4/distutils/core.py", line 
166, in setup
+SystemExit: error: $MACOSX_DEPLOYMENT_TARGET mismatch: now "10.4" but 
"10.3" during configure
+### execution of /sw/bin/python2.4 failed, exit code 1</codeblock>
+        <p>the problem occurs because the <code>python2*</code> 
packages write the current <code>MACOSX_DEPLOYMENT_TARGET</code> to a 
configuration file when they're built and the python build utilities use 
this value when compiling modules. This means that if you have, for 
example, a <code>python24</code> package on 10.4 that was built on 10.3, 
either by upgrading 10.3 =&gt; 10.4, or via the 
<em>10.4-transitional</em> binary distribution, in which 
<code>python24</code> wasn't rebuilt, there will be a mismatch between 
what python thinks <code>MACOSX_DEPLOYMENT_TARGET</code> should be 
(10.3) and what it actually is (10.4).</p>
+        <p>The fix is to rebuild the offending <code>python</code> 
package, e.g. <code>fink rebuild python24</code> for the case above.</p>
+      </answer>
+    </faqentry>
    </chapter>
    <chapter filename="comp-packages">
      <title>Compile Problems - Specific Packages</title>



-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP, 
AMD, and NVIDIA.  To register visit http://www.hp.com/go/dualwebinar