Re: Slackware Linux compilation problems

Chip Atkinson (chip@pupman.com)
Fri, 7 Aug 1998 16:48:03 -0600 (MDT)

It sounds like you either have no swap or not enough. Look at the man
page for swapon. You can use the command "free" to show the amount of
swap space and memory being used. The top command is useful to run while
doing the compilation. You can then watch as the memory is used up.

Chip

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Chip Atkinson
http://www.pupman.com
--- If I can't fix it, I can fix it so it can't be fixed --
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

On Fri, 7 Aug 1998, Matt Kuznicki wrote:

> Greetings,
>
> I apologize right away if this is the wrong address to send this to;
> if it is, please refer me to the correct one.
>
> In the PROBLEMS file of SANE-0.74 the first entry is a problem
> compiling under slackware, the compiler dying with a "virtual memory
> exhausted." It does actually eat up all the memory compiling the umax
> backend.
> I was able to produce this error with a nearly stock Slackware 3.4
> installation. Upon upgrading to GCC 2.80 and version 2.8.1.1 of
> libstdc++ (the std. libraries), SANE compiles without a hitch. I had
> also updated my binutils to 2.9.1.0.6, but am not sure if that has
> anything to do with this. Please also note that version 2.8.0 of the
> stdc++ libraries seems to take muck pleasure in making X servers
> segfault on my Slackware setup. I don't know if this is a reported bug
> or not.
>
> I hope this helps.
>
> Matt Kuznicki
>
> --
> Matt Kuznicki -- kuznick@bgnet.bgsu.edu
>
> "All life is future to past."
>
>
> --
> Source code, list archive, and docs: http://www.mostang.com/sane/
> To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com
>

--
Source code, list archive, and docs: http://www.mostang.com/sane/
To unsubscribe: echo unsubscribe sane-devel | mail majordomo@mostang.com