[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]



I have pretty much decided that the problem is hardware induced.  I just 
pulled the HD with the Slack 10.2 distro in it, put it in another 
machine, and I can compile to my heart's content.  The old motherboard 
had no problems with Slack 7.1 - it peacefully ran for four years.  But, 
it will not peacefully coexist with Slack 10.2.  Its time has come and gone.

Thanks all who wrote back.

V/r

Bob

James P. Kinney III wrote:

>On Sun, 2005-10-23 at 15:32 -0400, Bob Kruger wrote:
>  
>
>>Christopher;
>>
>>Fair enough.  The three shown here are "segmentation faults"  Here are
>>some snippets.  Firstly, compiling samba  3.0.22b:
>>    
>>
>
>I'm not running slack 10.2. Nor have I had compilation issues with the
>slack machines I do have.
>
>However, I have seen seg faults during compiles. 2 were memory faults
>(RAM was bad in ways that only a compiler would find or memtest86) and 2
>were bad applications configures. On one of the bad app configs, I had
>to do a lot more than just ./configure; make; make install. There were a
>bunch of settings I had to tweak.
>
>Samba, MySQL and PHP are monster applications that usually need much
>more than the vanilla ./configure to make correctly.
>
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Ale mailing list
>Ale at ale.org
&gt;<a  rel="nofollow" href="http://www.ale.org/mailman/listinfo/ale";>http://www.ale.org/mailman/listinfo/ale</a>
&gt;

-------------- next part --------------
An HTML attachment was scrubbed...



</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="00453" href="msg00453.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00446" href="msg00446.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> bkruger at mindspring.com (Bob Kruger)</li></ul></li>
<li><strong><a name="00447" href="msg00447.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> n4zm at mindspring.com (zeb)</li></ul></li>
<li><strong><a name="00448" href="msg00448.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> bkruger at mindspring.com (Bob Kruger)</li></ul></li>
<li><strong><a name="00449" href="msg00449.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> ale at accipiter.org (Christopher R. Curzio)</li></ul></li>
<li><strong><a name="00450" href="msg00450.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> bkruger at mindspring.com (Bob Kruger)</li></ul></li>
<li><strong><a name="00451" href="msg00451.html">[ale] Slackware v10.2 compile woes</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00451.html">[ale] Slackware v10.2 compile woes</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00453.html">[ale] Slackware v10.2 compile woes</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00451.html">[ale] Slackware v10.2 compile woes</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00453.html">[ale] Slackware v10.2 compile woes</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00452"><strong>Date</strong></a></li>
<li><a href="threads.html#00452"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>