Ticket #306 (closed defect: invalid)

Opened 6 years ago

Last modified 3 years ago

Sobby make: memory exhausted

Reported by: nh2 Owned by: armin
Priority: normal Milestone: Sobby 0.4.4
Component: Sobby Version: 0.4.4
Severity: normal Keywords: sobby; make; virtual; memory; exhausted
Cc: Launchpad Bug:

Description

After a successful ./configure on SuSE Linux 9.3, I get problems on makeing Sobby:

# make
g++ -DHAVE_CONFIG_H -I. -I./inc  -I/usr/local/include -I/opt/gnome/include/sigc++-2.0 -I/opt/gnome/lib/sigc++-2.0/include -I/usr/local/include/glibmm-2.4 -I/usr/local/lib/glibmm-2.4/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/libxml++-2.6 -I/usr/local/lib/libxml++-2.6/include -I/usr/local/include/libxml2   -I../inc/    -g -O2 -MT sobby-server.o -MD -MP -MF .deps/sobby-server.Tpo -c -o sobby-server.o `test -f 'src/server.cpp' || echo './'`src/server.cpp
virtual memory exhausted: Nicht genügend Hauptspeicher verfügbar
make: *** [sobby-server.o] Fehler 1

I ran free along the make, and its true: The memory decreases until 0 and the error message is shown.

How can I find out what the problem is?

Change History

Changed 6 years ago by phil

  • status changed from new to closed
  • resolution set to invalid

You don't even include the amount of RAM you have on your machine. Use a distributor-provided package or increase the amount of RAM for g++ (the C++ compiler) to run properly.

It may also be caused by using an old version of gcc, I don't know, and I won't guess on this one.

Changed 6 years ago by nh2

  • status changed from closed to reopened
  • resolution invalid deleted

Make uses 250 of 250 MByte (this is the amount of memory I can use on my v-server). GCC seems to be up to date :-(

Changed 6 years ago by phil

  • status changed from reopened to closed
  • resolution set to invalid

I don't see a case here. You did not read my comment completely. Your old version of SuSE Linux probably uses gcc 3.3, and gcc 4.2 is current, and 4.1 is common.

I doubt that g++ is able to use up the whole 250M, because there are probably other programs running, but it's common for C++ compilations to take up much RAM. Increase your amount of RAM or use another box to do the compilation on. We cannot support you on this one.

Changed 6 years ago by phil

And as a sidenote: I needed to increase the amount of memory assigned to our dev machine to be able to compile Sobby. 300M were sufficient on Debian Etch. It could be possible with some amount of swap to compile it, but you may observe heavy thrashing, so the build might take hours to compile and the server will be barely usable during that time.

Changed 6 years ago by nh2

  • status changed from closed to reopened
  • resolution invalid deleted

I've found the solution now. I stopped all services on my machine, but the make still did not work and told me:

# make
g++ -DHAVE_CONFIG_H -I. -I./inc  -I/usr/local/include -I/opt/gnome/include/sigc++-2.0 -I/opt/gnome/lib/sigc++-2.0/include -I/usr/local/include/glibmm-2.4 -I/usr/local/lib/glibmm-2.4/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/libxml++-2.6 -I/usr/local/lib/libxml++-2.6/include -I/usr/local/include/libxml2   -I../inc/    -g -O2 -MT sobby-server.o -MD -MP -MF .deps/sobby-server.Tpo -c -o sobby-server.o `test -f 'src/server.cpp' || echo './'`src/server.cpp
virtual memory exhausted: Nicht genügend Hauptspeicher verfügbar
make: *** [sobby-server.o] Fehler 1

So I did it manually:

# g++ -DHAVE_CONFIG_H -I. -I./inc  -I/usr/local/include -I/opt/gnome/include/sigc++-2.0 -I/opt/gnome/lib/sigc++-2.0/include -I/usr/local/include/glibmm-2.4 -I/usr/local/lib/glibmm-2.4/include -I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include -I/usr/local/include/libxml++-2.6 -I/usr/local/lib/libxml++-2.6/include -I/usr/local/include/libxml2   -I../inc/    -g -O2 -MT sobby-server.o -MD -MP -MF .deps/sobby-server.Tpo -c -o sobby-server.o `test -f 'src/server.cpp' || echo './'`src/server.cpp

Ad it worked. After another "make", it finished the other files and "make install" did the rest. (I used gcc 3.3.5 on a Suse Linux 9.3 v-Server.)

Changed 6 years ago by armin

Why did you reopen the ticket? Do you think there is anything we could do about this issue?

Changed 6 years ago by nh2

Sorry, I just thought it was necessary to set it to fixed or something like that, but then I saw I cannot change the status of my problem

Changed 6 years ago by armin

  • status changed from reopened to closed
  • resolution set to invalid
Note: See TracTickets for help on using tickets.