Em 18-08-2013 11:06, Bruce Dubbs escreveu: > BLFS Trac wrote: >> #3982: Firefox-23.0.1/Xulrunner-23.0.1 > >> * resolution: => fixed >> Comment: >> >> Fixed at revision 11650. >> >> Xulrunner, the first I built, needed over 3.3GB of memory, and ld died. >> Had to increase memory. > > Memory or disk space? I wouldn't think anything needs 3.3G RAM to compile. > > -- Bruce >
Perhaps disk space, but not partition space, I believe. If it was not this problem, I would have commited much earlier, still on the 17th, same day of release. First, build died repeatedly at the same point (attached, all five VMs are at this stuck point, now, it was lucky, hope I copied/pasted it correctly). Then, I follow disk/memory usage, and very rapidly, RAM and swap were 100% full, and the command taking more meory, called probably by that python script - or is it called python program? I cannot open the machine where it occurred to see, other three VMs are building xulrunner, now. A message of ld dead, Error 9, sent me in the internet to errors related to not enough swap. It was a VM, so, it was easier to increase the RAM than increase the 1.5GB swap. I increased RAM to 4GB, followed with htop through ssh in a tablet, and at sometime, it was using 3.3GB of RAM, swap not used anymore. Left it there, and later, it had finally completed. With these observations, I called "memory", instead of talking about RAM or swap. Other reason to increase the RAM, not swap, is that, obviously, a process taking place in RAM should be faster than in disk. It could be something wrong with that machine (only lfs x86_64 I have). Sometime ago (perhaps a couple of years), I followed these mozilla applications (SeaMonkey included), because one day, what was a reasonably fast compile/link, suddenly became increasingly very slow, from one version to the next, and discovered that was at this same point of the attached command. I think it is were libxul is linked. Some of the machines started to become unresponsive during that command, so I increased the 1GB RAM to 1.5GB, long ago, and things got better. One thing I am sure, each new version of these programs, more memory and time are needed. In my old days of FORTRAN, when compile and link were clearly separated, I would be sure, but these days, I am still struggling to understand these things. The VMS running now have 1.5GB of RAM, in this host, and two others, in another host, only have 1.0GB, running now, too. Since these problems started, I keep the VMs at the login, no X, and use ssh, to increase available RAM. -- []s, Fernando
libxul.so rm -f libxul.so /media/dados/home/fernando/tmp/paco-build-2013.08.18-10h58m52s/xulrunner-build-dir/_virtualenv/bin/python /media/dados/home/fernando/tmp/paco-build-2013.08.18-10h58m52s/mozilla-release/config/expandlibs_exec.py --depend .deps/libxul.so.pp --target libxul.so --uselist -- c++ -Wall -Wpointer-arith -Woverloaded-virtual -Werror=return-type -Wtype-limits -Wempty-body -Wsign-compare -Wno-invalid-offsetof -Wcast-align -fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections -fdata-sections -fno-exceptions -std=gnu++0x -fno-tree-vrp -pthread -pipe -DNDEBUG -DTRIMMED -g -Os -freorder-blocks -fomit-frame-pointer -fPIC -shared -Wl,-z,defs -Wl,-h,libxul.so -o libxul.so nsStaticXULComponents.o nsUnicharUtils.o nsBidiUtils.o nsSpecialCasingData.o nsUnicodeProperties.o nsRDFResource.o -lpthread -Wl,-z,noexecstack -Wl,--build-id -Wl,-rpath-link,/media/dados/home/fernando/tmp/paco-build-2013.08.18-10h58m52s/xulrunner-build-dir/dist/bin -Wl,-rpath-link,/usr/lib ../../media/kiss_fft/libkiss_fft.a ../../toolkit/components/osfile/libosfile_s.a ../../toolkit/xre/libxulapp_s.a ../../staticlib/components/libnecko.a ../../staticlib/components/libuconv.a ../../staticlib/components/libi18n.a ../../staticlib/components/libchardet.a ../../staticlib/components/libjar50.a ../../staticlib/components/libstartupcache.a ../../staticlib/components/libpref.a ../../staticlib/components/libhtmlpars.a ../../staticlib/components/libidentity.a ../../staticlib/components/libimglib2.a ../../staticlib/components/libmediasniffer.a ../../staticlib/components/libgkgfx.a ../../staticlib/components/libgklayout.a ../../staticlib/components/libdocshell.a ../../staticlib/components/libembedcomponents.a ../../staticlib/components/libwebbrwsr.a ../../staticlib/components/libnsappshell.a ../../staticlib/components/libtxmgr.a ../../staticlib/components/libcommandlines.a ../../staticlib/components/libtoolkitcomps.a ../../staticlib/components/libpipboot.a ../../staticlib/components/libpipnss.a ../../staticlib/components/libappcomps.a ../../staticlib/components/libjsreflect.a ../../staticlib/components/libcomposer.a ../../staticlib/components/libtelemetry.a ../../staticlib/components/libjsinspector.a ../../staticlib/components/libjsdebugger.a ../../staticlib/components/libstoragecomps.a ../../staticlib/components/librdf.a ../../staticlib/components/libwindowds.a ../../staticlib/components/libdiskspacewatcher.a ../../staticlib/components/libjsctypes.a ../../staticlib/components/libjsperf.a ../../staticlib/components/libgkplugin.a ../../staticlib/components/libunixproxy.a ../../staticlib/components/libjsd.a ../../staticlib/components/libautoconfig.a ../../staticlib/components/libauth.a ../../staticlib/components/libcookie.a ../../staticlib/components/libpermissions.a ../../staticlib/components/libuniversalchardet.a ../../staticlib/components/libfileview.a ../../staticlib/components/libplaces.a ../../staticlib/components/libtkautocomplete.a ../../staticlib/components/libsatchel.a ../../staticlib/components/libpippki.a ../../staticlib/components/libwidget_gtk2.a ../../staticlib/components/libimgicon.a ../../staticlib/components/libprofiler.a ../../staticlib/components/libaccessibility.a ../../staticlib/components/libremoteservice.a ../../staticlib/components/libspellchecker.a ../../staticlib/components/libzipwriter.a ../../staticlib/components/libservices-crypto.a ../../staticlib/components/libnkgio.a ../../staticlib
-- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
