public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* "Virtual Memory exhausted" message during compilation
@  Victor Tsaran
   ` Jacob Schmude
  0 siblings, 1 reply; 7+ messages in thread
From: Victor Tsaran @  UTC (permalink / raw)
  To: Speakup List

Hello, listers!
I was wondering if some of you know the remeedy or have any clues asto what
this message means in this context.
Earlier today I wrote that I am trying to compile Napster client on a
Bigslack7.1-powered machine. In order for PERL to run the Napster client, it
needs to support multiple threads. So, I started to recompile my PERL5.60.
Everything goes fine through configuration stage, I can start Make. However,
as soon as Make gets to queering Posix libraries, it always exits with the
following message:

"Posix.o: Virtual memory exhausted".

I thought initially that it has to do with the size of a swapfile. So, I
increased it to 128MB, my system RAM is only 32 MB. However, the message
persists.
I tried to compile PERL for both dynamic and static loading. Both cases
fail.
Jacob, do you have any suggestions?
Anyone?

Thanks in advance,
Vic

******* ******* *******
have you thought of visiting Cybertsar's Internet Kingdom? It is still
alive!
Here is the URL:
http://nimbus.ocis.temple.edu/~vtsaran/
******* ******* *******



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: "Virtual Memory exhausted" message during compilation
   "Virtual Memory exhausted" message during compilation Victor Tsaran
@  ` Jacob Schmude
     ` Victor Tsaran
  0 siblings, 1 reply; 7+ messages in thread
From: Jacob Schmude @  UTC (permalink / raw)
  To: speakup

Hi
	I've had this before. It seems to mean exactly what it says,
virtual memory is full. How much ram and how much swap do you have? Since
bigslack uses UMSDOS for its fs, you're more likely to get this
error. Make sure you have lots and lots of swap. If you can't create a
swap partition, you'll need to use a swap file, but you need some sort of
swap space. Make it about 128MB to be safe.

On Sun, 1 Oct 2000, Victor Tsaran wrote:

> Hello, listers!
> I was wondering if some of you know the remeedy or have any clues asto what
> this message means in this context.
> Earlier today I wrote that I am trying to compile Napster client on a
> Bigslack7.1-powered machine. In order for PERL to run the Napster client, it
> needs to support multiple threads. So, I started to recompile my PERL5.60.
> Everything goes fine through configuration stage, I can start Make. However,
> as soon as Make gets to queering Posix libraries, it always exits with the
> following message:
> 
> "Posix.o: Virtual memory exhausted".
> 
> I thought initially that it has to do with the size of a swapfile. So, I
> increased it to 128MB, my system RAM is only 32 MB. However, the message
> persists.
> I tried to compile PERL for both dynamic and static loading. Both cases
> fail.
> Jacob, do you have any suggestions?
> Anyone?
> 
> Thanks in advance,
> Vic
> 
> ******* ******* *******
> have you thought of visiting Cybertsar's Internet Kingdom? It is still
> alive!
> Here is the URL:
> http://nimbus.ocis.temple.edu/~vtsaran/
> ******* ******* *******
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: "Virtual Memory exhausted" message during compilation
     ` Victor Tsaran
@      ` Jacob Schmude
         ` Kirk Wood
       ` Kerry Hoath
  1 sibling, 1 reply; 7+ messages in thread
From: Jacob Schmude @  UTC (permalink / raw)
  To: speakup

Hi
	You may want to make it larger. I've got 128mb swap and 64mb
of physical memory, and had no trouble compiling perl but, then again, I'm
not using UMSDOS either. It could also be the fact that it is a swap file,
as the fs needs to be accessed for this file, slowing that system down and
using even more memory and CPU power. Do happen to have some other
partition you could put it on? This way, you'd avoid accessing the UMSDOS
fs too much. Better yet, if you can create a swap partition, do it!


On Sun, 1 Oct 2000, Victor Tsaran wrote:

> See, Jacob, that's the thing. I did mkswap the /root/swapfile to be as big
> as 128MB, but the error still persists. Perhaps it needs to be even larger?
> I have 32MB of physical RAM.



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: "Virtual Memory exhausted" message during compilation
     ` Victor Tsaran
       ` Jacob Schmude
@      ` Kerry Hoath
         ` Victor Tsaran
  1 sibling, 1 reply; 7+ messages in thread
From: Kerry Hoath @  UTC (permalink / raw)
  To: speakup

What kernel is this? The kernels have been experiencing vm strangeness lately
and aparently upgrading the kernel to 2.2.17 fixes many many of these out of
memory problems. The system isn't exactly out of memory; it just over
commits pages or gets into a tis.

Regards, Kerry.
On Sun, Oct 01, 2000 at 10:52:25PM -0700, Victor Tsaran wrote:
> See, Jacob, that's the thing. I did mkswap the /root/swapfile to be as big
> as 128MB, but the error still persists. Perhaps it needs to be even larger?
> I have 32MB of physical RAM.
> Best,
> Vic
> 
> ******* ******* *******
> have you thought of visiting Cybertsar's Internet Kingdom? It is still
> alive!
> Here is the URL:
> http://nimbus.ocis.temple.edu/~vtsaran/
> ******* ******* *******
> ----- Original Message -----
> From: "Jacob Schmude" <jacobs@ncinter.net>
> To: <speakup@braille.uwo.ca>
> Sent: Sunday, October 01, 2000 12:16 PM
> Subject: Re: "Virtual Memory exhausted" message during compilation
> 
> 
> > Hi
> > I've had this before. It seems to mean exactly what it says,
> > virtual memory is full. How much ram and how much swap do you have? Since
> > bigslack uses UMSDOS for its fs, you're more likely to get this
> > error. Make sure you have lots and lots of swap. If you can't create a
> > swap partition, you'll need to use a swap file, but you need some sort of
> > swap space. Make it about 128MB to be safe.
> >
> > On Sun, 1 Oct 2000, Victor Tsaran wrote:
> >
> > > Hello, listers!
> > > I was wondering if some of you know the remeedy or have any clues asto
> what
> > > this message means in this context.
> > > Earlier today I wrote that I am trying to compile Napster client on a
> > > Bigslack7.1-powered machine. In order for PERL to run the Napster
> client, it
> > > needs to support multiple threads. So, I started to recompile my
> PERL5.60.
> > > Everything goes fine through configuration stage, I can start Make.
> However,
> > > as soon as Make gets to queering Posix libraries, it always exits with
> the
> > > following message:
> > >
> > > "Posix.o: Virtual memory exhausted".
> > >
> > > I thought initially that it has to do with the size of a swapfile. So, I
> > > increased it to 128MB, my system RAM is only 32 MB. However, the message
> > > persists.
> > > I tried to compile PERL for both dynamic and static loading. Both cases
> > > fail.
> > > Jacob, do you have any suggestions?
> > > Anyone?
> > >
> > > Thanks in advance,
> > > Vic
> > >
> > > ******* ******* *******
> > > have you thought of visiting Cybertsar's Internet Kingdom? It is still
> > > alive!
> > > Here is the URL:
> > > http://nimbus.ocis.temple.edu/~vtsaran/
> > > ******* ******* *******
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
--
Kerry Hoath: kerry@gotss.eu.org
Alternates: kerry@emusys.com.au kerry@gotss.spice.net.au or khoath@lis.net.au
ICQ UIN: 62823451



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: "Virtual Memory exhausted" message during compilation
   ` Jacob Schmude
@    ` Victor Tsaran
       ` Jacob Schmude
       ` Kerry Hoath
  0 siblings, 2 replies; 7+ messages in thread
From: Victor Tsaran @  UTC (permalink / raw)
  To: speakup

See, Jacob, that's the thing. I did mkswap the /root/swapfile to be as big
as 128MB, but the error still persists. Perhaps it needs to be even larger?
I have 32MB of physical RAM.
Best,
Vic

******* ******* *******
have you thought of visiting Cybertsar's Internet Kingdom? It is still
alive!
Here is the URL:
http://nimbus.ocis.temple.edu/~vtsaran/
******* ******* *******
----- Original Message -----
From: "Jacob Schmude" <jacobs@ncinter.net>
To: <speakup@braille.uwo.ca>
Sent: Sunday, October 01, 2000 12:16 PM
Subject: Re: "Virtual Memory exhausted" message during compilation


> Hi
> I've had this before. It seems to mean exactly what it says,
> virtual memory is full. How much ram and how much swap do you have? Since
> bigslack uses UMSDOS for its fs, you're more likely to get this
> error. Make sure you have lots and lots of swap. If you can't create a
> swap partition, you'll need to use a swap file, but you need some sort of
> swap space. Make it about 128MB to be safe.
>
> On Sun, 1 Oct 2000, Victor Tsaran wrote:
>
> > Hello, listers!
> > I was wondering if some of you know the remeedy or have any clues asto
what
> > this message means in this context.
> > Earlier today I wrote that I am trying to compile Napster client on a
> > Bigslack7.1-powered machine. In order for PERL to run the Napster
client, it
> > needs to support multiple threads. So, I started to recompile my
PERL5.60.
> > Everything goes fine through configuration stage, I can start Make.
However,
> > as soon as Make gets to queering Posix libraries, it always exits with
the
> > following message:
> >
> > "Posix.o: Virtual memory exhausted".
> >
> > I thought initially that it has to do with the size of a swapfile. So, I
> > increased it to 128MB, my system RAM is only 32 MB. However, the message
> > persists.
> > I tried to compile PERL for both dynamic and static loading. Both cases
> > fail.
> > Jacob, do you have any suggestions?
> > Anyone?
> >
> > Thanks in advance,
> > Vic
> >
> > ******* ******* *******
> > have you thought of visiting Cybertsar's Internet Kingdom? It is still
> > alive!
> > Here is the URL:
> > http://nimbus.ocis.temple.edu/~vtsaran/
> > ******* ******* *******
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: "Virtual Memory exhausted" message during compilation
       ` Kerry Hoath
@        ` Victor Tsaran
  0 siblings, 0 replies; 7+ messages in thread
From: Victor Tsaran @  UTC (permalink / raw)
  To: speakup

Hi, Kerry!
This is version 2.2.16. Will try to upgrade tomorrow.
Best,
Vic

******* ******* *******
have you thought of visiting Cybertsar's Internet Kingdom? It is still
alive!
Here is the URL:
http://nimbus.ocis.temple.edu/~vtsaran/
******* ******* *******
----- Original Message -----
From: "Kerry Hoath" <kerry@gotss.eu.org>
To: <speakup@braille.uwo.ca>
Sent: Sunday, October 01, 2000 8:54 PM
Subject: Re: "Virtual Memory exhausted" message during compilation


> What kernel is this? The kernels have been experiencing vm strangeness
lately
> and aparently upgrading the kernel to 2.2.17 fixes many many of these out
of
> memory problems. The system isn't exactly out of memory; it just over
> commits pages or gets into a tis.
>
> Regards, Kerry.
> On Sun, Oct 01, 2000 at 10:52:25PM -0700, Victor Tsaran wrote:
> > See, Jacob, that's the thing. I did mkswap the /root/swapfile to be as
big
> > as 128MB, but the error still persists. Perhaps it needs to be even
larger?
> > I have 32MB of physical RAM.
> > Best,
> > Vic
> >
> > ******* ******* *******
> > have you thought of visiting Cybertsar's Internet Kingdom? It is still
> > alive!
> > Here is the URL:
> > http://nimbus.ocis.temple.edu/~vtsaran/
> > ******* ******* *******
> > ----- Original Message -----
> > From: "Jacob Schmude" <jacobs@ncinter.net>
> > To: <speakup@braille.uwo.ca>
> > Sent: Sunday, October 01, 2000 12:16 PM
> > Subject: Re: "Virtual Memory exhausted" message during compilation
> >
> >
> > > Hi
> > > I've had this before. It seems to mean exactly what it says,
> > > virtual memory is full. How much ram and how much swap do you have?
Since
> > > bigslack uses UMSDOS for its fs, you're more likely to get this
> > > error. Make sure you have lots and lots of swap. If you can't create a
> > > swap partition, you'll need to use a swap file, but you need some sort
of
> > > swap space. Make it about 128MB to be safe.
> > >
> > > On Sun, 1 Oct 2000, Victor Tsaran wrote:
> > >
> > > > Hello, listers!
> > > > I was wondering if some of you know the remeedy or have any clues
asto
> > what
> > > > this message means in this context.
> > > > Earlier today I wrote that I am trying to compile Napster client on
a
> > > > Bigslack7.1-powered machine. In order for PERL to run the Napster
> > client, it
> > > > needs to support multiple threads. So, I started to recompile my
> > PERL5.60.
> > > > Everything goes fine through configuration stage, I can start Make.
> > However,
> > > > as soon as Make gets to queering Posix libraries, it always exits
with
> > the
> > > > following message:
> > > >
> > > > "Posix.o: Virtual memory exhausted".
> > > >
> > > > I thought initially that it has to do with the size of a swapfile.
So, I
> > > > increased it to 128MB, my system RAM is only 32 MB. However, the
message
> > > > persists.
> > > > I tried to compile PERL for both dynamic and static loading. Both
cases
> > > > fail.
> > > > Jacob, do you have any suggestions?
> > > > Anyone?
> > > >
> > > > Thanks in advance,
> > > > Vic
> > > >
> > > > ******* ******* *******
> > > > have you thought of visiting Cybertsar's Internet Kingdom? It is
still
> > > > alive!
> > > > Here is the URL:
> > > > http://nimbus.ocis.temple.edu/~vtsaran/
> > > > ******* ******* *******
> > > >
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
> --
> --
> Kerry Hoath: kerry@gotss.eu.org
> Alternates: kerry@emusys.com.au kerry@gotss.spice.net.au or
khoath@lis.net.au
> ICQ UIN: 62823451
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: "Virtual Memory exhausted" message during compilation
       ` Jacob Schmude
@        ` Kirk Wood
  0 siblings, 0 replies; 7+ messages in thread
From: Kirk Wood @  UTC (permalink / raw)
  To: speakup

I have another idea. Why not have Jacob send you the bianary. I know it
isn't as sexy as compiling for yourself, but chances are it would run just
fine.

-- 
Kirk Wood
Cpt.Kirk@1tree.net
------------------

Seek simplicity -- and distrust it.
		Alfred North Whitehead




^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~ UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 "Virtual Memory exhausted" message during compilation Victor Tsaran
 ` Jacob Schmude
   ` Victor Tsaran
     ` Jacob Schmude
       ` Kirk Wood
     ` Kerry Hoath
       ` Victor Tsaran

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).