kopia lustrzana https://gitlab.com/sane-project/website
69 wiersze
3.3 KiB
HTML
69 wiersze
3.3 KiB
HTML
|
<!-- received="Tue Apr 21 10:37:24 1998 PDT" -->
|
|||
|
|
<!-- sent="Tue, 21 Apr 1998 18:36:55 +0100" -->
|
|||
|
|
<!-- name="Jim Ford" -->
|
|||
|
|
<!-- email="jf001@watford.net" -->
|
|||
|
|
<!-- subject="Sane compilation ate my ram!" -->
|
|||
|
|
<!-- id="" -->
|
|||
|
|
<!-- inreplyto="" -->
|
|||
|
|
<title>sane-devel: Sane compilation ate my ram!</title>
|
|||
|
|
<h1>Sane compilation ate my ram!</h1>
|
|||
|
|
<b>Jim Ford</b> (<a href="mailto:jf001@watford.net"><i>jf001@watford.net</i></a>)<br>
|
|||
|
|
<i>Tue, 21 Apr 1998 18:36:55 +0100</i>
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<li> <b>Messages sorted by:</b> <a href="date.html#229">[ date ]</a><a href="index.html#229">[ thread ]</a><a href="subject.html#229">[ subject ]</a><a href="author.html#229">[ author ]</a>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0230.html">Slana: "Re: 0.69 - 0.72 upgrade"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0228.html">Andreas Graevinghoff: "Re: sane 0.72 compilation under Solaris x86"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0194.html">Peter JD Hall: "Re: Sane compilation ate my ram!"</a>
|
|||
|
|
<li> <b>Maybe reply:</b> <a href="0194.html">Peter JD Hall: "Re: Sane compilation ate my ram!"</a>
|
|||
|
|
<li> <b>Reply:</b> <a href="0247.html">Peter JD Hall: "Re: Sane compilation ate my ram!"</a>
|
|||
|
|
<li> <b>Reply:</b> <a href="0255.html">Jim Ford: "Re: Sane compilation ate my ram!"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|
|||
|
|
<!-- body="start" -->
|
|||
|
|
I've tried the following message in comp.os.linux.hardware with no luck.<br>
|
|||
|
|
so I'll try it here. I don't think I'm asking for the moon - I've got a<br>
|
|||
|
|
perfectly standard<br>
|
|||
|
|
Slakware distribution on non-exotic hardware and have never encountered<br>
|
|||
|
|
compilation problems before. I _really_ don't want to have to use the<br>
|
|||
|
|
scanner under Win95!<br>
|
|||
|
|
<p>
|
|||
|
|
I've just ordered a scanner and decided in the meantime to install the<br>
|
|||
|
|
software. I grabbed the latest Sane package (0.72) and have tried<br>
|
|||
|
|
compiling it. It first ate my 64 meg of ram and then when that ran out,<br>
|
|||
|
|
<p>
|
|||
|
|
started snacking on my swap partition. When _that_ ran out, it burped<br>
|
|||
|
|
and announced "virtual memory exhausted" (in line 3686 of compiling<br>
|
|||
|
|
umax.c)!<br>
|
|||
|
|
<p>
|
|||
|
|
Now I guess that there is something wrong here and I don't have to<br>
|
|||
|
|
install more memory - I suspect that whatever I toss at it will also<br>
|
|||
|
|
get gobbled up! I also guess that I'm not alone with this problem and<br>
|
|||
|
|
I won't need to trawl through a lot of source code to find the problem<br>
|
|||
|
|
for myself.<br>
|
|||
|
|
<p>
|
|||
|
|
Any ideas, anyone?<br>
|
|||
|
|
<p>
|
|||
|
|
Regards: Jim Ford<br>
|
|||
|
|
<p>
|
|||
|
|
<pre>
|
|||
|
|
--
|
|||
|
|
Source code, list archive, and docs: <a href="http://www.mostang.com/sane/">http://www.mostang.com/sane/</a>
|
|||
|
|
To unsubscribe: echo unsubscribe sane-devel | mail <a href="mailto:majordomo@mostang.com">majordomo@mostang.com</a>
|
|||
|
|
</pre>
|
|||
|
|
<!-- body="end" -->
|
|||
|
|
<p>
|
|||
|
|
<ul>
|
|||
|
|
<!-- next="start" -->
|
|||
|
|
<li> <b>Next message:</b> <a href="0230.html">Slana: "Re: 0.69 - 0.72 upgrade"</a>
|
|||
|
|
<li> <b>Previous message:</b> <a href="0228.html">Andreas Graevinghoff: "Re: sane 0.72 compilation under Solaris x86"</a>
|
|||
|
|
<!-- nextthread="start" -->
|
|||
|
|
<li> <b>Next in thread:</b> <a href="0194.html">Peter JD Hall: "Re: Sane compilation ate my ram!"</a>
|
|||
|
|
<li> <b>Maybe reply:</b> <a href="0194.html">Peter JD Hall: "Re: Sane compilation ate my ram!"</a>
|
|||
|
|
<li> <b>Reply:</b> <a href="0247.html">Peter JD Hall: "Re: Sane compilation ate my ram!"</a>
|
|||
|
|
<li> <b>Reply:</b> <a href="0255.html">Jim Ford: "Re: Sane compilation ate my ram!"</a>
|
|||
|
|
<!-- reply="end" -->
|
|||
|
|
</ul>
|